JSON (JavaScript Object Notation) is the format almost every modern API, config file, and web app uses to move data around. It’s simple by design, but that simplicity hides a few strict rules — and when one of those rules is broken, the whole file fails to parse. A missing comma or an extra bracket won’t just look wrong; it will crash whatever’s trying to read it.
Why Formatting Matters
Raw JSON from an API response or a minified config file is often a single unbroken line of text — technically valid, but unreadable to a human. Formatting (also called “pretty-printing”) adds indentation and line breaks so the structure is visible at a glance: which values belong to which keys, where one object ends and another begins, and how deeply nested something is. This matters most when you’re debugging — a formatting tool turns “somewhere in this wall of text there’s an error” into “line 47, missing closing brace.”
The Most Common JSON Errors
Almost every JSON error comes down to one of a handful of mistakes:
- Trailing commas. Unlike JavaScript objects, JSON does not allow a comma after the last item in an array or object.
["a", "b",]is invalid. - Single quotes. JSON strings must use double quotes.
{'key': 'value'}will fail — it must be{"key": "value"}. - Unquoted keys. Every key must be a quoted string:
{name: "Alex"}is invalid;{"name": "Alex"}is correct. - Unescaped special characters. A double quote or backslash inside a string value needs to be escaped with a backslash, or it will terminate the string early.
- Missing or mismatched brackets. Every
{needs a matching}, and every[needs a matching]— easy to lose track of in deeply nested data.
Formatting vs. Minifying
These are opposite operations, and you’ll want both at different times:
- Formatting (pretty-print) adds whitespace and indentation for readability — use this while developing, debugging, or documenting.
- Minifying strips all unnecessary whitespace to reduce file size — use this for production API responses and config files being shipped over the network, where every byte counts.
How to Validate JSON Before You Ship It
A validator checks that your JSON follows the spec exactly and points to the precise location of any error, rather than leaving you to scan a huge file by eye. This is especially useful when:
- You’re hand-editing a config file and want to catch mistakes before deploying.
- You’re debugging why an API integration is failing silently.
- You’re reviewing JSON generated by another tool or a colleague’s code.
Try It Yourself
ToolNixy’s free JSON Formatter formats, validates, and minifies JSON directly in your browser — paste in a file, see it instantly pretty-printed, and get a clear error message if something’s invalid. Nothing is uploaded anywhere, so it’s safe to use with real data and API keys still in the payload (though it’s always good practice to strip secrets before sharing JSON with anyone else).
Related Guides
More on working with structured data formats: