JSON formatter

How to use it

1. Paste your JSON.
2. Choose 2 spaces, 4 spaces, a tab, or Minify.
3. If it is invalid, read the line and column and the reason, and fix that spot.
4. Copy the result.

What the error actually tells you

Invalid JSON gets the line and column of the first character the grammar cannot accept, and what it expected there. The usual causes are the things JavaScript allows and JSON does not: a trailing comma before a closing bracket, single quotes around a string, an unquoted key, a comment, or a number written .5 or 01. Each of those is named specifically rather than reported as “unexpected token”, because the fix is different for each.

Validity is decided by your browser’s own JSON.parse; the location is worked out separately, only when it fails, so a value that formats here is a value every JSON parser accepts.

What formatting changes, and what it does not

Whitespace and key order are the only things pretty-printing and minifying touch, with one exception worth knowing: numbers are normalised on the way through. 1.0 comes out as 1, 1e2 as 100, and an integer larger than 2⁵³ — a 64-bit database id, say — loses its low digits. That is how JavaScript numbers work, not a bug in this tool, and it is also what will happen when that JSON reaches any JavaScript that parses it. If those ids matter, send them as strings.

Everything happens in your browser. What you paste is never sent to Sellstamp, which is also why there is no size limit beyond what your browser can hold.