JSON formatter

Format re-indents valid JSON with two-space indentation so nested objects and arrays are visually tree-shaped. It is JSON.stringify(obj, null, 2) applied in your browser.

Minify removes all insignificant whitespace, producing the smallest valid JSON representation. That is useful for storage, transmission over constrained links, or comparing hashes with a server response.

Yes. Auto-detect recognizes key=value lines, key: value lines, comma- or tab-separated tables with a header, and JS object literals with unquoted keys, and converts each to valid JSON. Text without any recognizable structure becomes a JSON string. You can always pick an explicit input type to override the guess.

It parses the input and reports line and column for any error. For JSON input it echoes your text back unmodified; for text formats it shows the converted JSON so you can confirm it parsed successfully.

Error positions are taken from the engine's own parser message when available, else computed from the character offset. Either way, you get the line, the column, and the first line of the parser message.

No. JSON is processed entirely in your browser tab. No request is sent, no file is written to a server, and no analytics record your payload. This is especially relevant for schema snippets and private config.

Yes. Everything you paste is parsed, analyzed, and rendered in your browser with no network round-trips. Your payload is never transmitted, stored, or recorded, and disposing of the page erases it completely.

No. Formatting and minification only change whitespace - indentation for reading, or its removal for a compact output. The keys, values, and structure are preserved exactly, so the formatted JSON is semantically identical to the input.

The validator parses your input and reports the exact line, column, and parser message where a syntax error occurs. Unlike vague token errors, the position points straight at the problem - typically a missing comma, quote, or brace.

Yes, but encode it first with encodeURIComponent() and expect a length limit around a few KB in browsers and servers. For larger or sensitive payloads, your own client-side formatting and copying is safer, since you control where the data goes.

Use the JSON data format from ECMA-404 / RFC 8259, which is what browsers and this tool implement. There is no meaningful alternative for interoperable JSON, so a standards-compliant formatter is the right choice for every endpoint.

Yes. Once the page has been loaded once, all validation, formatting, and conversion logic lives in your browser. You can use it offline with no server dependency, and it never uploads your data.