LOCAL FILES. CLEAR RESULTS.

JSON workbench — editor, viewer & validator

Edit JSON on the left and inspect it live on the right: validate with exact line-and-column errors, format, explore a collapsible tree, run JSONPath queries and convert to CSV, XML or YAML.

About this tool

Most JSON tools make you choose between an editor and a converter. This workbench puts them side by side: your document lives in the left pane where you can type, paste or load a file, and the right pane keeps a formatted, validated view of it in sync — as collapsible text or as a tree you can fold open node by node, copying the JSONPath of anything you click.

Validation is the point of the page. When a document is broken, the workbench does not stop at "invalid JSON": it scans for the first place the grammar breaks and reports the exact line and column, marking the line in the editor gutter. Around that core sit the everyday operations — format with 2 or 4 spaces, minify, sort keys recursively, escape or unescape strings, JSONPath queries, and conversion to CSV, XML or YAML (and back from CSV or YAML) using the same local engine as the data converter. Everything runs in your browser; nothing is uploaded.

How to use JSON workbench — editor, viewer & validator

  1. Paste or type JSON in the left pane, or load a .json file or the sample. The right pane formats and validates as you type.
  2. If the JSON is broken, the status line names the exact line and column and the editor gutter marks the line — click the message to jump there.
  3. Format with 2 or 4 spaces, minify, sort keys, escape or unescape strings, switch the right pane to a collapsible tree, query with JSONPath, or convert to CSV, XML or YAML and download the result.

Keep the original files and inspect the exported result before publishing or sharing it.

Frequently asked questions

Is my JSON uploaded anywhere?

No. Parsing, validation, the tree view and every conversion run in your browser with JavaScript. Nothing is sent to a server, which is why the input limit is 5 MB — very large files would slow the tab down.

Why does the error line matter?

Most validators just say "unexpected token". This workbench scans the document and reports the first line and column where the grammar actually breaks, then marks that line in the editor so you can fix it in place.

Which JSONPath syntax is supported?

The everyday subset: $, .key, ['key'], [0], .* and [*] wildcards, and ..key recursive descent. Filter expressions such as [?(@.x>1)] are not supported and are reported as an error instead of silently returning wrong results.

How do conversions handle nested JSON?

CSV export needs a flat array of objects — the same rule as the data converter, whose engine this page reuses. XML repeats the element for each array item, and YAML is produced with a JSON-compatible schema. CSV or YAML pasted into the left pane can be converted back to JSON with the CSV → JSON and YAML → JSON operations.

Related tools