Free Developer Tool
JSON Validator Online — Instant Syntax Check
Paste any JSON and instantly know if it's valid. Syntax errors are caught with exact position — no more guessing which bracket is missing.
Features
What the validator checks
JSON has strict syntax rules. One wrong character breaks everything — the validator finds the exact problem instantly.
Syntax Validation
Checks bracket balance, quote pairing, commas, colons and value types according to the JSON specification (RFC 8259).
Error Location
When JSON is invalid, the exact error message from the browser's JSON parser is shown — including the character position of the problem.
Size Analysis
On valid JSON, shows total byte size, number of keys, maximum nesting depth — useful for understanding API payload sizes.
100% Private
Validation runs entirely in your browser. Sensitive JSON — API tokens, user data, config files — never reaches any server.
Instant Results
Runs on every keystroke. You see validation status as you type — no need to click a Run button.
Then Format
Once valid, switch to Format mode with one click to see the full syntax-highlighted, indented output.
Common JSON errors
Errors the validator catches
These are the most frequent JSON syntax errors developers encounter when working with APIs and config files.
Trailing commas
{"a": 1,} — The trailing comma after the last element is not valid in JSON (unlike JavaScript).Unquoted keys
{name: "Alice"} — JSON requires all keys to be double-quoted strings.Single quotes
{'name': 'Alice'} — JSON only accepts double quotes, never single quotes.Comments
// this is a comment — JSON does not support comments. Use JSONC or strip comments before parsing.Undefined values
{"x": undefined} — JSON has no undefined. Only null, booleans, numbers, strings, objects, arrays.Mismatched brackets
{"a": [1, 2} — An array opened with [ must close with ], not }.FAQ
Common questions
What is JSON validation?
JSON validation checks whether a string conforms to the JSON specification (RFC 8259). Valid JSON must use double-quoted keys, have no trailing commas, use only the six valid value types (string, number, boolean, null, object, array), and have properly matched brackets and braces.
Why does my JSON fail validation?
The most common reasons are: trailing commas (e.g.
[1, 2, 3,]), unquoted property names, single quotes instead of double quotes, JavaScript comments (// or /* */), or the value undefined which doesn't exist in JSON. The validator shows the exact error message so you can locate the problem.Is there a difference between JSON and JSONC?
Yes. JSONC (JSON with Comments) is a superset of JSON that allows
// line comments and /* */ block comments. It is used by tools like VS Code settings files and TypeScript config files. Standard JSON parsers reject JSONC. This validator checks standard JSON — strip comments before pasting JSONC.Can I validate JSON from an API response?
Yes. Copy the raw response body from your browser's DevTools Network tab, Postman, or curl, and paste it here. Since all processing is browser-based, API tokens and sensitive data in the JSON are never sent to any server.
Related tools