JSON Parse
Format and validate JSON, locate errors by line and column, view as tree and copy JSONPath
JSON parsing and formatting explained
The JSON parser reformats compact or unevenly indented text into a consistent layout with space or tab indentation, and reports the original size, the result size and the compression rate right away. Everything runs in the browser, so configuration files, API responses and log fragments never leave your device.
Formatting starts with a syntax check. A trailing comma, a missing quote or an unbalanced bracket is reported with its line and column, and the editor marks the exact position so you can fix it instead of scanning the whole document.
Beyond the text view you can switch to a tree view, expand objects and arrays level by level, and copy the JSONPath of any node for later queries or scripts. For longer editing sessions, use the online editor page and keep its local draft.
Frequently asked questions
- What should I do about a trailing comma error?
- Standard JSON does not allow a comma after the last member of an object or array. Remove that comma to pass validation; if the text comes from JSON5 or a JavaScript object, convert it on the JSON5 page first.
- Why is the formatted result larger?
- Formatting inserts line breaks and indentation, so the output is usually larger than the compact input. A negative compression rate is expected; use the minify mode when you need a smaller payload.
- Where is the parsed result stored?
- The result only lives in the current page memory and disappears on refresh. The history page stores recent formats you trigger explicitly, and that data stays in the browser.