JSON Minifier.

Minify and compress JSON online — free and lossless

A JSON minifier removes every byte of unnecessary whitespace — spaces, tabs, and newlines — to make your JSON as small as possible. Paste your JSON above and press Minify JSON; the tool compresses it to one line and reports the before-and-after size plus the percentage saved. The result is byte-for-byte equivalent data, just smaller.

Why compress JSON?

• Faster transfers. Smaller API responses and bundles load quicker and cost less bandwidth.
• Production payloads. Minified JSON is the standard form for data shipped to clients.
• Storage. Compact JSON takes less room in databases, caches, and logs.

Minifying is lossless — here is exactly what it removes

Minification strips only the whitespace between tokens, which JSON parsers ignore. Nothing inside your strings is touched, and no key, value, type, or ordering changes:

{
  "user": {
    "name": "Ada Lovelace",
    "roles": [ "admin", "dev" ]
  }
}

becomes:

{"user":{"name":"Ada Lovelace","roles":["admin","dev"]}}

The space inside "Ada Lovelace" survives, because it is part of the data. Parse both and you get an identical object — which is why minifying is always safe, and always reversible with the JSON formatter.

Minifying is not the same as compressing

This is the most common misunderstanding, and it matters if you are trying to make an API faster.

Minifying removes whitespace and gives you a smaller but still readable JSON document — typically 10–30% smaller, depending on how deeply indented the original was.

Compression (gzip or Brotli) is a binary encoding applied on top, usually by your web server, and routinely achieves 70–90%. It is a far bigger win.

They stack, but with diminishing returns: compression algorithms are extremely good at collapsing repeated whitespace, so gzipping a pretty-printed file gets you most of the way there on its own. Minify anyway — it is free — but if your payload is slow, enable compression first. That is where the real saving is.

Minify JSON in code

JavaScript — simply omit the indent argument:

JSON.stringify(data);            // minified
JSON.stringify(data, null, 2);   // pretty-printed

Python — you must set the separators, or you keep a space after every comma and colon:

import json
json.dumps(data, separators=(",", ":"))   # truly minified

Command line:

jq -c . data.json > data.min.json

When not to minify

Never minify JSON you commit to git. A minified file is a single line, so changing one field makes git report the whole file as rewritten — code review becomes impossible and merge conflicts become unresolvable.

The rule: format what you commit, minify what you ship. Keep the repository copy pretty-printed and minify at build time for the bytes that actually travel over the network.

Minify, then expand whenever you need

Minification is fully reversible: run the output back through the JSON formatter to pretty-print it again. You can also validate first to be sure the input is well-formed, or view it as a tree. Learn more in minify vs. pretty-print JSON.