JSON Editor
A JSON editor goes beyond pretty-printing. You need to change values, navigate nested objects, repair broken payloads, compare two documents, or convert to YAML—without installing an IDE plugin. This page gives you dual panes (tree, text, and table views) that run locally after the page loads.
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.
Enjoying this tool?
Part of JSON tools
JSON editor: edit, repair, and compare JSON in your browser
A JSON editor goes beyond pretty-printing. You need to change values, navigate nested objects, repair broken payloads, compare two documents, or convert to YAML—without installing an IDE plugin. This page gives you dual panes (tree, text, and table views) that run locally after the page loads.
Use it when Postman is overkill, when a support ticket includes a mangled config, or when you want a side-by-side diff of two API responses. Pair it with the JSON Formatter when you only need whitespace cleanup, and with JSON Escape when you are embedding a string inside another document.
How to use this converter
- Paste JSON into either pane, or open a file / URL / CSV from the editor controls.
- Switch between tree, text, and table views to navigate nested data.
- Edit values, repair syntax issues, then copy JSON, minified JSON, or YAML.
- Use a second pane to compare or transform without leaving the page.
Before and after examples
Editors change structure; formatters only change whitespace.
| Original | Converted | Notes |
|---|---|---|
| {"user":{"id":1}} | { "user": { "id": 1, "active": true } } | Add a field in the tree |
| [{"sku":"A"},{"sku":"B"}] | Table rows for sku A / B | Array as table |
JSON editor vs JSON formatter
A formatter validates and re-indents. An editor lets you change structure: rename keys, delete nodes, import CSV rows, and keep two versions visible while you merge fields. If your only job is “make this readable,” open the JSON Formatter. If you are building or fixing a payload, stay on this editor.
Both tools parse with the same browser JSON rules—no comments, no trailing commas—so a file that fails here will also fail in production Node or browser fetch handlers.
Tree, text, and table views
Tree view is best for deep objects: expand only the branch you need. Text view is best for paste-from-logs workflows and quick find/replace in the raw string. Table view helps when an array of similar objects should read like a spreadsheet.
Large documents can slow older tabs. Filter or truncate huge log dumps before pasting, then edit the fragment that matters.
Secrets and privacy
Editing runs in this browser tab. That is safer than uploading tokens to a random SaaS formatter—but screenshots, shared machines, and browser extensions still see your clipboard. Redact production secrets before sharing a pane with a teammate.
Frequently asked questions
Is the JSON editor free?
Yes. Edit, compare, and convert in your browser with no account required.
Does it upload my JSON?
No. Parsing and editing run locally after the page loads.
When should I use the formatter instead?
Use the JSON Formatter when you only need to pretty-print or minify. Use this editor when you need to change values, compare panes, or work in tree/table views.
Can it validate against a JSON Schema?
Use the schema tools in the editor chrome when available. Syntax validity (JSON.parse) is always checked first.