JSON, Quick Facts
- •JSON stands for JavaScript Object Notation, the standard data format for APIs, config files, and NoSQL databases.
- •Valid JSON requires double quotes around keys and strings, no trailing commas, and no comments.
- •The only types allowed are object
{}, array[], string, number, boolean, andnull. - •A single missing comma or bracket is the most common cause of "Unexpected token" errors.
- •This tool runs 100% in your browser — nothing you paste is ever uploaded, so API responses with tokens or customer data stay on your machine.
The Real Problem This Solves
APIs and log files return JSON crammed onto one line, hundreds of characters wide, with no indentation. Reading it, or spotting the one syntax error breaking your integration, is nearly impossible by eye.
This tool beautifies it instantly for reading, minifies it back down for production, validates it against the JSON specification, and tells you the exact line and column where a syntax error is hiding instead of a vague browser console message.
One more thing that matters for real work: the JSON you paste here never leaves your browser. Many online formatters send your input to their server to process it — a real problem when the payload contains bearer tokens, session IDs, or customer records. Here, parsing happens locally with JavaScript's built-in engine; you can load this page, disconnect from the internet, and it still works.
Beautify, Minify, Validate — What Each One Does
Beautify (also called a JSON beautifier or pretty printer) parses your JSON into a data structure and rewrites it with consistent indentation — 2, 4, or 8 spaces — one key per line, with optional alphabetical key sorting. Sorted keys make two payloads diff cleanly, which is the fastest way to spot what changed between two API responses.
Minify reverses it: every non-essential space and line break is stripped to produce the smallest payload for the wire. A typical formatted config shrinks by 30–40%, which matters when the JSON ships inside every API response or gets embedded in an HTML page.
Validate happens in the same parse step: the input is checked against strict JSON syntax (RFC 8259). If it fails, you get the reason and the precise location. That last part is the point — the browser's own error ("Unexpected token } in JSON at position 4183") makes you count characters; this tool converts the position into a line and column you can jump to.
Example: A minified API response like {"id":7,"name":"Rahul","active":true} expands into a clean, indented block with one key per line, making nested objects and arrays immediately readable — especially useful for deeply nested config files or GraphQL responses.
Most invalid JSON fails for one of six reasons. If your file won't parse, check this list against the error location before anything else:
| Error You See | Usual Cause | The Fix |
|---|---|---|
Unexpected token ' | Single quotes around keys or strings | JSON only allows double quotes: {"name": "value"} |
Unexpected token } or ] | Trailing comma after the last item | Delete the comma before the closing bracket |
Unexpected token a/N/u | Unquoted key, or NaN/undefined as a value | Quote every key; use null instead of NaN or undefined |
Unexpected end of JSON input | Truncated response or an unclosed bracket | Check the response wasn't cut off; balance every { [ with } ] |
Unexpected token / | Comments in the JSON | Strict JSON has no comments — remove // and /* */ lines |
Bad control character in string | A raw line break inside a string value | Escape it as \n instead of pressing Enter |
Frequently Asked Questions
Why does my JSON say "Unexpected token"?
Usually a trailing comma, single quotes instead of double quotes, or an unquoted key. This tool shows the exact line and column of the failure so you can jump straight to it instead of scanning the whole file — the table above covers the six most common causes and their fixes.
How do I fix "Unexpected end of JSON input"?
The parser reached the end of your text while still expecting more — either the payload was truncated (common when copying from a terminal or a log that cut off) or a bracket was never closed. Paste the full response and check that every opening brace and bracket has a closing partner.
Is a JSON formatter the same as a JSON validator or beautifier?
They are the same parse under different names. A beautifier rewrites the JSON readably, a minifier compresses it, and a validator reports whether it parses at all. This tool does all three in one pass — if it can format your input, your input is valid.
Is my data sent to a server?
No. Formatting, minifying, and validation all happen entirely in your browser using JavaScript's built-in JSON parser. Nothing is uploaded anywhere — you can even use this page offline once it has loaded. That matters when your JSON contains API keys, tokens, or customer data.
Can this handle large JSON files?
Yes. The editors are full-width, sized to your screen, and drag-resizable, and the parsing uses the browser's native engine, which comfortably handles multi-megabyte payloads. For very large files, minified input formats faster than you can scroll it.
Can JSON have comments?
No. The JSON specification has no comment syntax. If you need notes, use a JSON5/JSONC-style variant your tooling supports, or add a dedicated field like "_comment".
What is the difference between JSON and a JavaScript object?
JSON is a text format with a stricter subset of rules: quoted keys, no functions, no trailing commas, no undefined values. A JavaScript object literal is code and can hold any value, including functions, that JSON simply cannot represent.
Does sorting keys change what the JSON means?
No. JSON objects are unordered by specification, so sorting keys alphabetically only affects readability and makes diffs cleaner, it does not change the data. Array order is always preserved.
Related Calculators
This config actually written in YAML?
Docker Compose, GitHub Actions, and Kubernetes all lean on YAML for the same kind of data. Convert between the two with our YAML to JSON Converter.
Open YAML to JSON Converter →