Reading JSON that was never meant to be read
JSON returned by an API is usually minified: every unnecessary space stripped out to save bandwidth. That is the right choice for a machine and the wrong one for a human. A single line running to several thousand characters is effectively unreadable, and finding the one field you care about means scrolling sideways and counting brackets.
This formatter takes that single line and expands it into an indented structure where nesting is visible at a glance. Paste, press Format, and the shape of the data becomes obvious.
Validation and error messages
The more common use is finding out why a payload is being rejected. JSON is strict in ways that trip people up constantly: keys must be wrapped in double quotes, single quotes are never valid, trailing commas after the last item in an array or object are forbidden, and comments are not part of the specification at all despite how often people try to add them.
When parsing fails, this tool reports the error along with the line number where the parser gave up. The reported position points to where the problem was detected, which is not always where it was introduced — a missing closing brace early in a document often surfaces as an error near the end. Working backwards from the reported line usually finds it quickly.
Minifying for production
The Minify button does the reverse, stripping all whitespace to produce the most compact valid representation. This is worth doing for configuration files shipped to browsers, for payloads sent over constrained connections, and anywhere you are paying for bandwidth. The tool reports how many characters you saved.
Indentation conventions
Two spaces is the most widely used indentation for JSON and is the default in most JavaScript tooling. Four spaces is common in Python-adjacent projects. Tabs are less usual in JSON specifically but are sometimes required by house style. Whichever you choose, consistency across a codebase matters far more than the choice itself.
Your data never leaves your browser
API responses routinely contain access tokens, customer records, email addresses and internal identifiers. Pasting that into an online formatter that uploads to a server is a real, if quiet, data leak. This tool parses everything locally in your browser using the native JSON parser — nothing is transmitted, nothing is logged, and nothing persists after you close the tab.
Frequently Asked Questions
Why does my JSON say invalid when it looks correct?
The three most common causes are single quotes instead of double quotes, a trailing comma after the last element, and comments, none of which are valid JSON even though they are valid JavaScript.
Does formatting change my data?
No. The tool parses your JSON into an object and re-serialises it, so values are preserved exactly. Only whitespace changes. Note that key order is preserved but duplicate keys will collapse to the last one.
Is my JSON uploaded to a server?
No. Parsing and formatting happen entirely in your browser, which matters because API responses often contain tokens and personal data.
Can it handle very large files?
Yes, though files of several megabytes may take a moment to render in the text area. The parsing itself is fast.
Why is the reported line number not where the problem is?
The parser reports where it detected the failure, not where it began. A missing bracket early on is often only noticed much later in the document, so work backwards from the reported line.