JSON Tools

Fixing a JSON problem is rarely one operation. A payload fails to parse, so you validate it, repair it, format it to read it, then sort its keys to compare it against what you expected — and in most online tools that is four pages and four pastes. Here they share a single editor, a single input, and a history of what you have worked on. The language switcher at the top behaves identically for HTML, CSS, JavaScript, and JSON, so the whole set works as one editor rather than as separate utilities.

JSON is the format your sensitive data arrives in. An API response you are debugging can contain names, email addresses, access tokens, internal identifiers, and payment details, and pasting that into a server-side tool means handing all of it to a third party — which in many organisations is a policy violation regardless of intent. Every transform here runs as JavaScript on your machine, so there is no request to audit and no log to worry about. Disconnect from the network after the page loads and everything still works.

Ten things without leaving the editor. Format and minify handle the everyday need to make JSON readable or compact. Validate tells you the exact line and column where a payload fails to parse, and Repair fixes the usual causes — trailing commas, single quotes, unquoted keys — automatically. Sort keys makes two documents comparable. Flatten collapses nesting into paths for translations and configuration. Escape and Unescape move documents in and out of string literals. Paths lists every dotted key. JSON to YAML produces what infrastructure tooling expects.

Start with the validator, because it tells you where the parser gave up and what it expected. If the cause is one of the common JavaScript-style mistakes, the Repair tool fixes it in one step. If neither helps, the problem is usually that the content is not JSON at all — a truncated response or an HTML error page returned with the wrong content type — and the first line of what you pasted will show that immediately.

No. Every tool runs in your browser as JavaScript — your data is never uploaded, never logged, and never sent to a server. You can confirm it by watching the Network tab in devtools while you work, or by disconnecting from the internet after the page loads and seeing that everything still functions. That matters for JSON in particular, because API responses routinely contain personal data, tokens, and internal identifiers.

No. Whatever is in the editor follows you between JSON tools, so you can validate a payload, repair it, then format and sort it without pasting four times. Each language keeps its own draft and its own history, so switching to the HTML, CSS, or JavaScript tools leaves your JSON alone. History is stored in your browser only, and you can pin entries you want to keep.