How this tool works
The text is parsed with the browser's own JSON parser, which is the same one your code will use, so anything accepted here will be accepted there. Beautifying re-prints the parsed data with two-space indentation; minifying re-prints it with no whitespace at all. Both produce the same data, and both report the root type, the key or item count, and the byte size.
When parsing fails, the message is turned into a line and column rather than a character offset, because an offset in a 40,000-character payload tells you nothing. It is strict JSON throughout: comments, trailing commas, single quotes and unquoted keys are all rejected, exactly as they would be by an API.
Reading the result honestly
- The output is a re-print, not your text: the data is parsed and written out again, so whitespace, line breaks and formatting choices are replaced rather than tidied.
- Duplicate keys silently collapse: JSON allows them and the parser keeps the last one. If a payload had two keys of the same name, only one survives the round trip and nothing warns you.
- Very large integers lose precision: anything beyond about sixteen digits is rounded, because numbers are parsed as doubles. Identifiers of that size belong in strings.
- Numeric-looking keys are reordered: a key such as "2" is moved ahead of ordinary text keys when the object is written out. The data is identical; the order is not what you pasted.