Skip to content
FmtTools

JSON tools

Parse, print and check JSON documents

Three pages over the same parser: one that re-indents a document, one that explains why it will not parse, and one that removes every byte RFC 8259 calls insignificant. All of them keep numbers as the exact literal you pasted — no JavaScript Number round trip — which is the difference between a formatter you can trust on an API payload and one that quietly rewrites 9007199254740993 to 9007199254740992.

3 tools in this column

Questions people ask before converting

Do these JSON tools send my data anywhere?

No. Parsing, formatting and validation run in JavaScript inside your browser tab, so a payload never leaves the machine and there is no server-side log of it. That is also why the pages work offline once loaded and why there is no size limit other than your own memory — a 20 MB response is handled locally instead of being uploaded to someone else's queue.

Why does my formatted JSON differ from the original file?

Only whitespace and, if you ask for it, key order change. RFC 8259 §2 defines object order as unspecified and §6 defines whitespace as insignificant, so a formatter is free to normalise both. These pages keep the order you pasted by default and escape forward slashes nowhere, because RFC 8259 §7 dropped the JSON:///../ escaping that the older ECMAScript JSON.parse (RFC 4627) inherited from JavaScript string literals.

Which page should I use for a file that will not parse?

Start with the validator: it names the offending token and the offset, and it flags the things a plain JSON.parse hides, such as a UTF-8 BOM, comments, single quotes, trailing commas and newline-delimited JSON. If the source is a log or a config export, repair mode on the formatter turns JavaScript-style syntax into valid JSON and lists every mechanical change it made.

Read next