JSON Editor
Two full JSON editors side by side. Switch each pane between tree, text, and table. Repair messy pastes, transform with JSONQuery or JMESPath, compare documents, or validate against a schema in the other pane. Work stays in this browser—no account and no cloud save.
Loading JSON editor…
Each pane is a full JSON editor (tree, text, table). Use Open when you want a file, URL, or CSV; Copy for JSON, minified, or YAML. Drag the ⋮ handle to resize—both panes stay visible.
Part of JSON tools
Two independent editors, three modes each
Left and right panes are separate documents. Each pane switches between tree (keys and values, context menu, drag to reorder), text (highlighted source with format and compact), and table (spreadsheet-style rows for arrays of objects). Copy or transform from one pane to the other without overwriting the source until you choose to.
Repair, transform, compare, and validate
Repair fixes comments, trailing commas, quotes, and similar issues. Transform filters, sorts, and reshapes JSON with JSONQuery, JMESPath, JSONPath, Lodash, or JavaScript. Compare highlights added, removed, and changed paths (left is old, right is new). Point the right pane at a JSON Schema to validate the left document.
Files, CSV, and what stays local
Open JSON or NDJSON from disk, drop a file on a pane, fetch an https URL that allows CORS, import CSV (header and dotted nested keys), and export CSV or YAML. Documents under 1 MB are remembered in this browser’s local storage. There is no account, share link, or cloud folder—copy or download when you need a file.
Frequently asked questions
How is this different from JSON Formatter?
The formatter pretty-prints or minifies a single box. This editor adds tree and table modes, undo/redo, search, repair, sort, transform, dual-pane compare, schema warnings, and CSV import/export.
Does it save my JSON to a server?
No. There is no login and no cloud folder. A copy can stay in local storage on this device. Use Save JSON or Copy when you need a file elsewhere.
Which transform language should I use?
JSONQuery is the default for filter/sort/pick on arrays. JMESPath and JSONPath are common for queries. Lodash and JavaScript are for people who already think in those APIs. Transform never leaves this tab.