The errors it explains
A trailing comma after the last item, single quotes instead of double ones, a comment, an unquoted key, NaN or a missing bracket: JSON allows none of them, and each is reported with its line, its column and a plain explanation, so you can fix an API response or a config file without hunting for the character. Duplicate keys, which most parsers accept silently while keeping only the last value, are flagged too.
Numbers, depth and size
Integers larger than JavaScript can represent exactly (above 2^53, such as 64-bit ids from Twitter, Discord or databases) are kept digit for digit when you indent or minify, where most online formatters silently round them. Documents of several MB format in a second; anything nested deeper than 500 levels is refused with a clear message.
Format, minify, or convert
Indent with 2 or 4 spaces or tabs to read and review, minify to send it over the network or store it compactly, explore it as a collapsible tree, or turn it into CSV, YAML or XML with the converters. The result can be copied or downloaded, and a share link reopens the tool with the same JSON.
Understanding JSON structure
JSON supports six data types: strings (enclosed in double quotes), numbers (integers or decimals), booleans (true/false), null, arrays (ordered lists in square brackets), and objects (key-value pairs in curly braces). Keys must always be strings in double quotes.
APIs almost always send an object or an array as the root, but the JSON standard (RFC 8259) also accepts a single value — a string, a number, true, false or null — as a whole document. Values can be nested inside each other; this tool accepts up to 500 levels, far more than real files use.
JSON vs XML: why JSON won for web APIs
JSON has largely replaced XML for web API data exchange due to its lighter syntax, smaller file sizes, and native compatibility with JavaScript. While XML offers features like schemas, namespaces and attributes, JSON's simplicity makes it faster to parse and easier to work with in modern web applications.
Most REST APIs, configuration files (package.json, tsconfig.json), and NoSQL databases like MongoDB use JSON natively. XML remains relevant in enterprise systems, SOAP web services, and document formats like SVG and XHTML.