JSON Parser
Run your JSON through a real parser to confirm it is well-formed, and read the parsed result as clean output.
Your data stays on your device
Input — JSON
- characters
- 0
- lines
- 0
- size
- 0 B
Output — Parsed JSON
- characters
- 0
- lines
- 0
- size
- 0 B
Options
About this tool
Parsing is the step every program performs before it can use JSON: the text is scanned, its structure is checked against the grammar, and it becomes an in-memory value. This tool runs that same step and shows you the outcome.
When the input parses, you get a tidy, indented rendering of the value. When it does not, the parser stops at the first violation and explains what it expected — a comma, a closing brace, a quoted key — with the position highlighted.
Parsing is stricter than most people expect. JSON has no comments, no trailing commas, no single-quoted strings, no unquoted keys, no hexadecimal or leading-zero numbers, and no NaN or Infinity. Anything a JavaScript engine would happily accept in an object literal may still be rejected here, which is exactly why a document that "looks fine" can fail in a strict consumer.
A parse failure always reports the first problem it hits, not every problem in the file. Fix that one and parse again — later errors are often caused by the first, so a single missing brace can otherwise produce a misleading list of complaints further down.
How to use this tool
- Paste the JSON text you want to check, or upload a file.
- Press Parse to run it through the parser.
- Read the indented output, or jump to the reported error position if parsing failed.
- Copy or download the parsed result when you are happy with it.
Key features
- Strict, specification-compliant parsing
- Line, column and character offset for every error
- Indented rendering of the parsed value
- Duplicate-key awareness through the related Validator
- Runs entirely client-side
Example
Input — JSON
{"user":{"id":7,"name":"Mira"},"active":true}Output — JSON
{
"user": {
"id": 7,
"name": "Mira"
},
"active": true
}Good to know
- It parses a single top-level JSON value. For newline-delimited JSON, parse one record at a time.
- Very deeply nested documents can exhaust the browser call stack; split them before parsing.
Frequently asked questions
How is this different from the Validator?
The Validator focuses on a pass/fail report and duplicate-key detection. The Parser emphasises turning valid input into readable output, while still reporting errors precisely.
Can it parse JSON with comments?
Standard JSON has no comments, so they are reported as errors here. Use JSON Repair to strip comments and produce clean JSON.
Where does parsing happen?
In your browser. No request carries your document to a server.
Why does it reject a number like 007 or 0x1F?
JSON numbers may not have leading zeros and have no hexadecimal form. Quote the value if it is really an identifier such as "007", or write it in plain decimal.
It only shows one error — where are the rest?
Parsing stops at the first violation, because everything after it is unreliable. A single missing brace or comma usually explains the errors that would follow, so fix that one and parse again.
Your data stays on your device
Your data is processed locally in your browser and is not uploaded to our server. This page keeps working after you go offline, because there is nothing to send.