JSON Formatting, Validating & Minifying: A Practical Guide
JSON (JavaScript Object Notation) is the lingua franca of modern APIs and config files. It’s simple, but a single misplaced comma can break an entire payload — and a minified blob of JSON is nearly impossible to read. This guide covers the everyday JSON tasks developers actually do: formatting, validating, minifying, fixing errors, and comparing two JSON documents.
What “formatting” (beautifying) means
Formatting takes compact or messy JSON and re-indents it with consistent spacing and line breaks so it’s easy to read. It doesn’t change the data — just the whitespace. Our JSON Formatter lets you beautify with 2-space, 4-space or tab indentation, and it works entirely in your browser, so nothing you paste is uploaded.
Validating JSON (and the rules that trip people up)
Valid JSON follows a few strict rules that are easy to forget:
- Keys and strings must use double quotes —
"name", not'name'. - No trailing commas — the last item in an object or array can’t be followed by a comma.
- No comments — standard JSON doesn’t allow
//or/* */. - No undefined or functions — only strings, numbers, booleans, null, arrays and objects.
When you beautify in our formatter, invalid JSON is caught with a clear error message telling you what went wrong and where. For convenience, the tool is also lenient: if you paste JavaScript-style input (single quotes, unquoted keys, trailing commas), it will auto-correct it into valid JSON for you.
Minifying JSON
Minifying does the opposite of beautifying: it strips every unnecessary space and line break to make the payload as small as possible. That’s useful for reducing bandwidth in production APIs and for embedding JSON in places where size matters. In the formatter, just click Minify to get a single-line version you can copy.
Common JSON errors and how to fix them
- “Unexpected token” — usually a missing or extra comma, or a value that isn’t quoted. Beautify the JSON to see exactly where it breaks.
- “Expected property name” — a key isn’t wrapped in double quotes, or there’s a trailing comma before a closing brace.
- Wrong quotes — smart/“curly” quotes copied from a document aren’t valid; replace them with straight double quotes.
Comparing two JSON files
When an API response changes or a config drifts between environments, you need to see exactly what’s different. Our JSON Diff Checker compares two JSON documents and shows a side-by-side, colour-coded diff — added, removed and changed keys with their full path (like user.address.city). You can step through each change and export the differences as JSON or a text report.
A quick workflow
- Paste raw JSON into the formatter and click Beautify to read it and confirm it’s valid.
- Fix any errors it flags, then Minify if you need a compact version.
- Comparing two versions? Drop them into the diff checker to see precisely what changed.
Frequently asked questions
Is my JSON uploaded anywhere? No — both tools run entirely in your browser, so your data stays local.
Does it handle large files? Yes, within the limits of your browser’s memory — it comfortably handles typical API payloads.
Can it fix invalid JSON? The formatter auto-corrects common JavaScript-style mistakes (single quotes, unquoted keys, trailing commas) into valid JSON.