About minifying JSON
Minifying JSON means stripping out every space, tab, and line break that a human added for readability but a machine does not need. The data is identical; only the whitespace is gone. This tool parses your JSON, confirms it is valid, and prints it back as a single compact line. It also works the other way with the Prettify button, re-indenting a minified blob so you can read it. Everything happens in your browser.
Because it parses before it prints, the tool doubles as a validator. If the output is empty and you see an error, the input is not valid JSON, usually a trailing comma, a single quote where a double quote belongs, or an unquoted key.
Why bother minifying?
Size. Whitespace can be a surprising share of a JSON file, especially one that is deeply indented. Stripping it makes the payload smaller, which means less to send over the network and less to store. The tool shows you the before and after byte counts so you can see exactly how much you saved.
In practice you minify at the boundary where size matters and keep a formatted copy while you work. A config file or an API response you are debugging should stay pretty and readable. The version that ships to production, gets embedded in another string, or travels over a slow connection is the one worth minifying.
Minify is not compression
Minifying only removes whitespace, so the savings are modest compared to real compression like gzip, which most servers already apply on top. The two stack: gzip shrinks a minified file a little further. But minifying is free, reversible, and safe, since the parsed data never changes.