Why it matters
JSON is everywhere in web work: API responses, config files, structured data and package files. One missing comma or a trailing comma breaks the lot, and the error messages browsers give are often cryptic.
Many online formatters send what you paste to a server, which is a problem for API keys and customer data. This one runs in your browser and explains errors in plain English.
How it works
- InputJSON from an API or a file
- In your browserParsed and checked by the browser
- OutputFormatted or minified JSON, or the exact error line
Where it fits in a designer's workflow
- Plan
- Design
- Build
- Test
- Launch
By the numbers
Show the numbers as a table
| Style | Bytes |
|---|---|
| Minified | 145 |
| 2-space indent | 198 |
| 4-space indent | 230 |
| Tab indent | 182 |
How to use it
- Paste JSON into the box.
- Choose an indent, or minify.
- If there's an error, read the hint and press Jump to the error.
- Copy or download the result.
FAQ
Why is my JSON invalid?
The usual causes are a trailing comma, single quotes instead of double quotes, keys without quotes, or comments. JSON allows none of them.
Is my data sent anywhere?
No. It's parsed by your browser's own JSON parser on this page.
Does sorting keys change the data?
No. Object keys have no meaning in their order. Arrays keep their order.
Can it handle big files?
Yes, several megabytes are fine. Very large files may take a second to format.