JSON viewer — format, validate & explore

No. Parsing, formatting, tree rendering and conversion all run in your browser. The site uses Google Analytics for page-level visit counts only — the JSON you paste never leaves your device.

When JSON.parse fails, modern browsers include a character offset (Chrome / Edge) or line and column (Firefox / Safari) in the thrown message. The viewer parses that out and moves your textarea caret to the failing character.

JSONC is JSON with comments — // and /* */ — used by VS Code settings.json, tsconfig.json and others. Strip comments walks the text token by token, leaves anything inside string literals untouched, and removes only the comment runs.

Only when the root is an array of flat objects, like [{"id":1,"name":"A"}, ...]. The viewer takes the union of keys as headers, escapes commas, quotes and newlines, and writes one row per object. Nested values become empty cells — flatten first if you need them.

Every leaf in the tree view has a small copy path button. It builds a JSONPath-style string like $.users[0].name, escaping keys that aren't simple identifiers as bracketed quoted strings ($['weird-key']).

Escape wraps your current text in JSON.stringify so it becomes a single quoted string literal — handy for embedding JSON inside another JSON value or a code snippet. Unescape reverses the operation: if your textarea contains a quoted string, it parses it and replaces the textarea with the inner content.

It produces clean YAML for the common shape — nested objects and arrays, strings, numbers, booleans, null. Strings with YAML-significant characters (:, #, leading dashes / whitespace) are quoted. It does not emit anchors, aliases or custom tags.

The whole tree is rendered up-front, so multi-MB files can feel slow on weaker machines. For most config files and API responses the tree is instant. For giant payloads, work in the textarea and use the search to find what you need.

Yes — the textarea contents are saved to localStorage so they're there when you return. Click Clear or wipe browser site data to remove them.

Paste your JSON and watch the status row. Invalid JSON turns rose and shows the parser’s exact message (e.g. Unexpected token } in JSON at position 142); click Jump to error to move your caret there. Common culprits are trailing commas after the last ,, unquoted keys, single quotes, comments, or unescaped newlines inside strings — Strip trailing commas and Strip comments fix the JSONC-style ones in one click.

Beautify (also called pretty-print) adds indentation and line breaks so a human can read the structure — this tool offers 2-space, 4-space and tab variants. Minify strips every whitespace character outside string literals so the payload shrinks to its smallest legal form, ideal for API responses, embedded data or saving bandwidth. Both produce identical values when re-parsed.

Not as a first-class parser — the viewer uses the browser’s strict JSON.parse, which follows RFC 8259. The two most common JSON5 sins, however, are handled: click Strip comments to remove // and /* */, then Strip trailing commas. Unquoted keys and single-quoted strings are not auto-fixed; convert them in the text editor or paste valid JSON instead.