JSON Validator

Check JSON syntax against RFC 8259 in milliseconds. Get the exact line and column for every error. Runs entirely in your browser — zero upload, zero latency.

INPUTUTF-8 / JSON

What validation actually catches

JSON has a strict grammar defined by RFC 8259. Despite its apparent simplicity, a single misplaced character — a trailing comma, a single-quoted string, an unquoted key — breaks the entire document and crashes any downstream parser.

This validator uses your browser's native JSON.parse, which is the same engine Node.js, Deno, Bun, Chrome, Firefox, and Safari use. If a document passes here, it will parse in any modern JavaScript runtime — no surprises in production.

Common JSON errors

  • Trailing comma — [1, 2,] is invalid
  • Single quotes — JSON requires double quotes
  • Unquoted keys — { name: "x" } is JS, not JSON
  • Missing comma between key/value pairs
  • Comments — // inline are not JSON
  • NaN / Infinity — use null instead

Privacy first

All validation happens locally in this browser tab. Your data never leaves your device, is never logged on any server, and disappears when you close the tab. Open the network panel — you will see zero requests when you click Validate.

Common questions

What is a JSON validator?
A JSON validator checks that a JSON document conforms to the JSON specification (RFC 8259). It catches syntax errors such as missing commas, unbalanced braces, trailing commas, unquoted keys, and invalid escape sequences before your application tries to parse the data.
Is this validator free and private?
Yes. JSONEditor.net runs entirely in your browser using the native JavaScript JSON parser. Your data is never uploaded, stored, or logged on any server. The validator works offline once the page is loaded.
Why does my JSON fail to validate?
The most common errors are: trailing commas after the last item in an array or object, single quotes instead of double quotes, unquoted object keys, missing commas between key/value pairs, unescaped control characters in strings, and unbalanced braces or brackets. This validator reports the exact line and column where parsing failed.
Does it support JSON5, JSONC, or comments?
No. This tool validates strict JSON (RFC 8259) only. Comments, trailing commas, and unquoted keys are not part of standard JSON and will be reported as errors. For JSON5 or JSONC you need a dedicated parser — those formats are intentionally lenient extensions.
How big a JSON file can I validate?
Validation runs in your browser, so the practical limit is your device memory. Files up to a few hundred megabytes generally work on modern desktops; very large payloads (multi-GB) should be streamed with a tool like jq, fx, or a server-side parser.
How is this different from the main JSON editor?
This page is a single-purpose validator with extra context and a dedicated FAQ. The main editor at the homepage offers the same validation plus tree, table, graph, and constellation views, multi-tab workspaces, undo/redo, and conversion to 18+ formats.

When to validate JSON

Validate before committing a configuration file to source control, before sending a request body to an API, after generating JSON from a template, after a copy-paste from another tool, and any time you see a "SyntaxError: Unexpected token" in your logs. Validating early surfaces the problem at the file you control, not three layers deep in a microservice you do not own.

Pair with the rest of JSONEditor.net

Once your JSON validates, you may want to convert it to CSV for a spreadsheet, to YAML for a Kubernetes manifest, generate TypeScript interfaces from its shape, or diff it against another version to see what changed. The same data, no re-upload — every tool runs in the same in-browser session.