JSON Minifier Online

What minifying removes

Minifying strips whitespace that sits between tokens: spaces, tabs and line breaks outside of strings. RFC 8259 says this whitespace is insignificant, so a minified document parses to exactly the same data as the formatted one. Keys, values, array order and member order are untouched.

What it does not change

Minifying does not touch the inside of strings. Spaces and escape sequences like \n within a value stay as they are, because they are part of the value. It also does not shorten your keys, remove null values, drop empty arrays or round numbers. If you want a smaller payload by changing the data itself, that is a design decision for the API, not something a minifier should do silently.

One more limit: minified JSON is still JSON. If the input was invalid, the minifier cannot meaningfully produce valid output, so run Validate first.

When to minify

Minify when bytes travel. That includes request and response bodies, values stored in a database column or a cache, a JSON string embedded in an environment variable, and data placed in a URL or a single-line field. The saving is real on large, deeply indented documents, though how much depends on your data. In practice, HTTP compression such as gzip shrinks whitespace-heavy text very well, so the extra gain from minifying before compression is smaller than people expect.

When not to

Do not minify files that humans edit or review. A config checked into a repository should stay formatted, so that diffs show which line changed. The same is true for test fixtures, documentation examples and anything that goes through code review. A single-line file makes every change look like the whole file was rewritten. The sensible pattern is to keep the readable version as the source and produce the minified version at the point where it is sent or stored. Because the data is identical, you can format it again at any time.

Checking your result

After minifying, confirm the output still parses, and spot-check a value that contains a space or an escaped character. If you are putting the result inside another string, such as a shell argument or a JavaScript literal, remember that the quotes now need escaping for that outer context. That is a separate concern from JSON itself, and it is a frequent source of errors when minified JSON gets pasted into code.

Minified is not obfuscated

A related point is that minifying is reversible in practice. Because only insignificant whitespace is removed, you can run the compact text through a formatter and get a readable document back with the same data. What you cannot recover is the original indentation style or any blank-line habits, since those were never data. That makes it safe to minify a copy for transport while keeping the formatted original as your working file. It also means you can paste a one-line response from a log or a network tab into a formatter or viewer whenever you need to read it, and the minified form is no obstacle to debugging.