JSON in 60 Seconds
JSON (JavaScript Object Notation) is the standard format for moving data between servers and browsers. Every REST API you've ever called returns JSON. Every package.json, tsconfig.json, and .eslintrc file on your machine is JSON.
The format is dead simple: objects use curly braces, arrays use square brackets, strings need double quotes. But the simplicity is deceptive. There's no comment syntax, trailing commas are illegal, and a single misplaced comma will break the entire document. That's where a formatter with validation comes in.
JSON is defined in RFC 8259 (December 2017). The spec is only 16 pages. The rule most people trip over: object keys MUST be strings in double quotes. {name: "John"} is valid JavaScript but invalid JSON. Another gotcha: despite the name, JSON isn't a strict subset of JavaScript. Characters U+2028 and U+2029 are valid in JSON strings but were illegal in JS string literals until ES2019.
How to Use
- 1Paste or type your JSON into the input area on the left.
- 2Pick your indentation: 2 spaces (JS/TS convention) or 4 spaces (Python convention).
- 3Hit "Format" to pretty-print, or "Minify" to strip all whitespace.
- 4Copy the result. If there are errors, the validator highlights the exact line and character.
When You'll Actually Use This
Debugging API responses
Your fetch() returns a 2000-character blob. Paste it here to see the nested structure. Way faster than console.log(JSON.stringify(data, null, 2)) when you're jumping between multiple endpoints.
Validating config files before deploy
Caught a trailing comma in your CloudFormation template? That's a 20-minute deploy failure you just avoided. Paste any JSON config here before pushing. The validator catches what your editor's syntax highlighting misses.
Cleaning up database exports
MongoDB dumps and Firestore exports come as massive single-line JSON. Format it to find that one document with the weird null field that's crashing your migration script.
Preparing JSON for documentation
Need to show a JSON example in your API docs or README? Format it with 2-space indent, copy, paste into your markdown code block. Done in 5 seconds.
Tips from Experience
Always validate before you parse
Wrap JSON.parse() in try-catch. Always. An unhandled JSON parse error in production will crash your Node process or show users a white screen of death.
Watch out for copy-paste encoding issues
Smart quotes from Slack/Word (“” instead of ""), invisible BOM characters from Windows Notepad, and non-breaking spaces from web pages. All of these break valid-looking JSON. If the validator says error at position 0, it's probably an invisible character.
Know when NOT to use an online tool
For files over 10MB, use jq on the command line. For automated formatting in CI, use prettier or python -m json.tool. This tool is for quick manual debugging at your desk, not pipeline automation.
2 spaces vs 4 spaces
JSON spec doesn't care. But JS/TS projects overwhelmingly use 2 spaces (check any popular open source repo). Python projects tend to use 4. Pick one and be consistent across your team.
Real-World Examples
Nested API response
A typical user profile response from a REST API, minified as it arrives over the wire.
Input
{"id":42,"name":"Jane","email":"jane@example.com","roles":["admin","editor"],"preferences":{"theme":"dark","locale":"en-US","notifications":{"email":true,"push":false}},"lastLogin":"2026-05-10T14:30:00Z"}Output
{
"id": 42,
"name": "Jane",
"email": "jane@example.com",
"roles": [
"admin",
"editor"
],
"preferences": {
"theme": "dark",
"locale": "en-US",
"notifications": {
"email": true,
"push": false
}
},
"lastLogin": "2026-05-10T14:30:00Z"
}Invalid JSON: spot the error
This looks right at first glance, but has a trailing comma that breaks strict JSON parsing.
Input
{"users": [{"name": "Alice", "age": 30,}, {"name": "Bob", "age": 25}]}Output
Error at position 38: Unexpected token '}'. Trailing comma after "30" is not allowed in JSON. Remove the comma to fix.Limitations
- Maximum input size is limited by browser memory (typically ~100MB for modern browsers, but performance degrades above 10MB).
- Does not support JSON5, JSONC (comments), or other JSON superset formats — strict RFC 8259 only.
- Cannot format streaming or partial JSON — the entire document must be valid before formatting.
- No file upload support — content must be pasted manually or via clipboard.
Features
- 2 or 4 space indentation, your choice
- Validates and pinpoints errors to the exact line and character
- One-click minification for production use
- Your data stays local. Zero network requests after page load.
- Handles files up to ~50MB (tested with production MongoDB dumps)
- No signup, no ads, no tracking
Frequently Asked Questions
My JSON looks valid but the parser says "unexpected token". What gives?
Nine times out of ten it's one of these: (1) trailing commas, like {"a": 1,} which is invalid, (2) single quotes, because JSON requires double quotes only, (3) unquoted keys like {name: "John"} which is JS but not JSON, (4) comments, since // and /* */ aren't allowed in standard JSON. If you need comments, look into JSONC or JSON5.
Is there a file size limit?
No hard limit on our end. It runs in your browser's memory. Chrome handles up to ~100MB before tabs start crashing. For anything over 10MB, you'll get better performance with jq or fx on the command line.
Does this tool phone home with my data?
No. Zero network requests after the page loads. Open DevTools, go to the Network tab, paste your JSON, click format. Nothing fires. The entire tool is client-side JavaScript.
What's the difference between JSON and JSONC?
JSONC (JSON with Comments) allows // and /* */ comments plus trailing commas. VS Code uses it for settings.json and tsconfig.json. Standard JSON parsers will reject JSONC, so you need a JSONC-aware parser like the jsonc-parser npm package.
Why does JSON not allow trailing commas?
It's a deliberate design choice from the spec to keep parsing simple and unambiguous. JavaScript allows them, Python allows them, but JSON doesn't. Most "invalid JSON" errors in the wild come from developers assuming JSON follows the same rules as their programming language.
Is it safe to paste production JSON data into this tool?
Yes. This formatter processes all data using your browser's native JSON.parse() and JSON.stringify() methods. 100% client-side JavaScript. No data is transmitted to our servers. You can verify by opening DevTools → Network tab while formatting: zero outbound requests fire. Safe for JWT payloads, API responses, config files, and any other sensitive JSON.
Last reviewed:
Your Privacy
All processing happens entirely in your browser. No data is uploaded to any server. Your JSON never leaves your device.
In-Depth Guide
Complete Guide to JSON: Syntax, Validation & Common Errors
Everything you need to know about JSON: from basic syntax to fixing the errors that trip up even experienced developers.
Read guideTips & Related Workflows
- Putting formatted JSON into a URL parameter? Encode it first with the URL Encoder/Decoder.
- Got a Base64-encoded JSON payload from an API? Decode it with the Base64 Encoder/Decoder.
- Building a JSON Schema with regex patterns? Test them in the Regex Tester.
- If your JSON objects need unique IDs, grab some from the UUID Generator.