Publisher notes · reviewed 10 September 2026
What this JSON formatter does with invalid input
The formatter pretty-prints JSON that already parses, and it reports the first syntax error when the text is not JSON. It is not a schema validator and it does not send the document to Toolioz when the page is labelled local processing.
Parse errors you will actually see
JSON requires double-quoted keys, no trailing commas, and no comments. A trailing comma after the last property is valid in JavaScript objects and invalid in JSON. Single quotes around strings fail. `undefined` is not a JSON value. The engine stops at the first violation and shows a position; fix that before looking for a second error.
Huge minified files can freeze a tab because parsing is synchronous on the main thread. Split the file or use a desktop tool if the browser complains. Formatting does not prove the payload matches an API contract. That check is JSON Schema, on a different page.
Privacy note
Tokens, passwords, and PII pasted here stay in the tab only if the page states local processing. The website still loads scripts and analytics. Do not paste production secrets into any website, including this one, if your policy forbids it.
Worked examples
Trailing comma
{"ok": true,} fails. {"ok": true} parses. Remove the comma after true.
Limits of this page
- Does not repair YAML, TOML, or JavaScript object literals automatically.
- Duplicate keys: JSON.parse keeps the last value; that may not be what the API author intended.