JSON Formatter & Validator

JSON is stricter than JavaScript object syntax, and the differences cause most parse errors. Keys must be double-quoted strings. Single quotes are invalid anywhere. Trailing commas are invalid. Comments are invalid. Numbers cannot have leading zeros or a trailing decimal point, and NaN and Infinity are not representable.

Most parse failures in practice are a trailing comma or a copied JavaScript literal with unquoted keys. A formatter that reports the character offset of the failure usually points within a few characters of the real problem.

The specification requires UTF-8 and permits any Unicode in strings, so emoji and accented characters need no escaping. Escapes are still valid, which is why the same document can appear in two very different-looking but equivalent forms.

JSON numbers have no defined precision, but JavaScript parses them as doubles, which represent integers exactly only up to 2^53 - 1. Discord snowflakes exceed that, which is why the API returns every ID as a quoted string.

Parsing such a string as a number silently rounds it and produces an ID that is close but wrong - and wrong in a way that looks plausible, so it survives casual inspection. Any code touching Discord IDs should keep them as strings or convert to BigInt, never to Number.

Every webhook payload, embed object and bot API response uses JSON. Being able to format a messy response into readable indentation, or minify a large embed JSON for storage, is an everyday task for bot developers and server admins.

The three errors people hit most often are trailing commas after the last item, single quotes around keys or strings, and unescaped quotes inside a value. A validator that points to the exact position saves you from reading a huge file line by line.