Format strict JSON into readable indentation, validate its syntax, or minify it for a compact representation. Switch between raw text and a collapsible tree to inspect nested API responses or configuration data. Keep a copy of the source when exact numeric precision matters.
lightbulb When to use this tool
- check_circle Read a compact API response by adding indentation and expanding its object tree.
- check_circle Check whether a configuration snippet is valid strict JSON before passing it to another application.
- check_circle Remove insignificant whitespace from valid JSON without manually editing string contents.
Inputs and results
Input: Strict JSON text or a selected JSON file.
Output: Formatted or minified JSON, syntax feedback, a tree view, copy and download controls.
Why use our tool?
Inspect raw text or a tree
Raw and tree views provide two ways to inspect nested data.
Choose readable or compact output
Separate Format and Minify actions make the output purpose explicit.
Check syntax before exporting
Syntax feedback helps identify malformed input before copying or downloading.
How it works
Paste strict JSON, upload a file or use the sample.
Choose indentation and click Format to make the structure readable.
Switch to Tree to expand nested objects and arrays, or return to Raw to edit the source.
Use Minify to remove formatting whitespace, then copy or download the result.
If parsing fails, check quotes, commas and bracket pairs. Preserve large identifiers as quoted strings in the original data when exact digits matter.
Examples
science Read a nested response
Try {"user":{"id":"001","active":true},"roles":["editor"]}. Formatting adds indentation; Tree lets you inspect user and roles separately. The quoted ID stays a string.
science Fix a trailing comma in strict JSON
{"name":"Ada",} is invalid strict JSON. Remove the comma before the closing brace to produce {"name":"Ada"}. The formatter reports invalid syntax; it does not automatically repair JSONC or JSON5.
science Keep an identifier's digits
Use {"accountId":"9007199254740993"} when those exact digits are an identifier. A bare numeric value that large exceeds JavaScript's safe integer range and may change when parsed.
Limitations
This uses JavaScript JSON parsing. JSONC comments, JSON5 syntax, single-quoted strings and trailing commas are not supported. Syntax validation does not check a JSON Schema or verify whether field values are correct. Integers beyond JavaScript's safe range may lose precision, and duplicate object keys may be overwritten during parsing; retain your source.
Frequently Asked Questions
Is JSON validation the same as JSON Schema validation? expand_more
Can I format JSON with comments or trailing commas? expand_more
What is the difference between formatting and minifying JSON? expand_more
Why should large IDs be strings? expand_more
Processing & Privacy
Processing uses your browser rather than uploading the supplied input to a processing server. Fonts and tool libraries can make third-party network requests. Optional analytics loads after consent. See the Privacy Policy for site-wide details.