Does validation upload my file?
No. Parsing runs in a Web Worker in this tab.
Paste a payload to check that it parses as JSON. A valid document is confirmed in this tab; an invalid one shows the syntax problem next to the editor. Nothing is posted to a server.
JSON formatter
Run a tool to see a polished result here
This page asks โis this JSON?โ โ commas, quotes, brackets, and literal names. It does not evaluate JSON Schema, OpenAPI, or TypeScript types. A document can be valid JSON and still be the wrong shape for your API. Use Repair when the text is JavaScript-like (comments, trailing commas, single quotes) rather than strict JSON.
Trailing commas, comments, or single quotes? Repair JSON applies conservative fixes, then you can validate the strict JSON.
Once it parses, pretty-print with the JSON beautifier so you can read the structure.
Two documents both valid but disagreeing? JSON compare groups added, removed, and changed paths.
Valid and too nested to read as text? Open the JSON viewer and collapse the branches you do not need.
Missing commas between members. Extra commas after the last array item or object property. Single-quoted strings (`'name'`). Unquoted keys (`{name: 1}`). Bare `NaN`, `Infinity`, or `undefined`. JavaScript comments. Truncated files that close fewer braces than they open. Those are all syntax problems; the status line is the place to read them.
{ name: 'jfmt', tags: ['json',], } โ not JSON
{ "name": "jfmt", "tags": ["json"] } โ validStandard JSON.parse keeps the last duplicate key and ignores the earlier ones. JFmt still parses, then warns in the summary when a key appeared more than once so silent data loss is visible. Integers above Number.MAX_SAFE_INTEGER are preserved as digits in the formatted output rather than rounded.
The validator will accept `"null"`, `[]`, and `{"status": 500}` because they parse. It will not tell you that an order is missing `items` or that `price` should be a number. Pair this page with JSONPath or JSON Compare when you need shape or drift checks on top of syntax.
The sample is already valid: an envelope with ok, errors, and a nested payload. Break it on purpose (delete a comma, add a trailing comma, wrap a key in single quotes) to see how each class of error is reported.
{
"ok": true,
"errors": [],
"payload": { "id": 42, "name": "jfmt" }
}Use the validator when a parser elsewhere rejected a file and you need the syntax error locally. Skip this page if you already know the JSON is valid and you want a tree, a spreadsheet, or a compare report.
Also try JSON beautifier, JSON viewer, JSON compare, Repair JSON, or JSON to XML. The JSON formatter on the homepage is the general workspace.
No. Parsing runs in a Web Worker in this tab.
No. This URL starts in validate-only mode. Switch to Repair in the sidebar for automatic syntax fixes.
Yes, in the status summary when the parser sees them. JSON objects should have unique keys; the last value wins.
It is a syntax checker (jsonlint-style). It does not load a JSON Schema and does not check types beyond JSON literals.
JSON has null, not undefined. Replace undefined with null or omit the key.