Three views (tree / table / graph) for JSON: search, diff, schema inference — large files parsed off-thread.

Switch tool

Input0 chars · 0 lines

Nothing to show.

How to use

Purpose

Online JSON viewer and formatter that beautifies, minifies, validates and converts JSON to XML. Three view modes (split, tree, raw) handle nested objects with deep hierarchies. Large files (100MB+) are parsed in a Web Worker so the UI never freezes. Errors are pinpointed to line:column with highlighting; lenient mode parses non-standard JSON with comments or trailing commas. Common use cases: debug REST API responses, inspect JSON fields in logs, diff schemas across versions. A daily tool for backend, frontend, and QA engineers.

Steps

Paste JSON into the left editor or drop a .json file; files above 1MB auto-route to Worker parsing
Pick a view mode: split (editor + tree side by side), tree (deep nested objects), raw (preserve indentation)
Click Format for 2-space indented standard JSON, or Minify to strip all whitespace for transport
Errors are pinpointed to line:column with red highlighting; fix and the view updates instantly
Click Schema to infer a JSON Schema draft from the current data
JSON → XML and XML → JSON conversions are one click away
Use the Diff view to compare two JSONs side by side with added/removed/changed lines highlighted
Search keys or values in the top bar; matched paths auto-expand in tree view
Export options: download JSON file, copy minified string, or generate a share link (data never leaves the browser)

FAQ

How do I fix "Unexpected token" errors in JSON?: The error message includes line:column, and the editor highlights the exact position. Common causes: trailing commas like {"a":1,}, single-quoted strings, unquoted keys, or leftover comments. These violate standard JSON, but lenient mode can parse them; toggle it in the toolbar.
A 10MB JSON file freezes the browser, what can I do?: The tool auto-detects large files and parses them in a Web Worker so the UI thread stays responsive. If tree rendering is still slow, switch to lazy expansion (only first level by default) and expand nodes on demand. Or click Minify to reduce DOM nodes.
How do I convert JSON to TypeScript interfaces or Java POJOs?: This tool infers JSON Schema; for code generation use the dedicated json-to-types or sql-to-entity tools. Hit Send-To-Tool in the toolbar to ship the current JSON via postMessage (data stays in browser).
Chinese characters in JSON show up as \u4e2d\u6587 escapes?: Output preserves UTF-8 by default. The escapes come from upstream serializers like Python json.dumps with ensure_ascii=True. Format here always emits readable UTF-8; use unicode-converter if you need ASCII escapes.
Is my data uploaded to a server?: No. All parsing, formatting, validating, and converting happen entirely in your browser. You can verify in DevTools Network: after the page loads, no fetch/XHR fires during operations.

Use cases

Debug REST APIs: paste responses from Postman or DevTools Network, format and search for specific fields
Triage production logs: log lines often include single-line JSON; expand them to see nested structure
Review config files: large application.json or package.json read better in tree view than IDE folding
Verify API contracts: infer Schema from backend responses; frontend writes types from Schema
Compare environments: diff dev vs prod responses to find missing fields or drifted values

Use cases

Debug REST APIs, triage production JSON in logs, diff schemas across versions, review configs, infer frontend types. Worker parsing for large files, precise error pinpointing, and lenient parsing are the differentiators.