About this tool
Whenever JSON has to travel through URL parameters, QR codes, log lines or request bodies, size matters. A nicely indented document can easily be several times larger than it needs to be.
This tool parses your input and re-emits it in its most compact form — a single line with no extra whitespace. The before/after byte count and compression ratio are shown so you can gauge the benefit.
How to use
- Paste your indented JSON into the input panel.
- Click "Minify".
- The output is a single-line JSON alongside a size report.
- Copy it straight into a request body, URL or env var.
Use cases
- Shrink frontend telemetry payloads to reduce bandwidth and log storage cost.
- Pack structured parameters into URLs or QR codes without exceeding length limits.
- Store JSON config inside env vars without worrying about multi-line escaping.
Notes
- Minification only removes whitespace; keys, values and structure are untouched.
- Invalid JSON is rejected with a helpful error pointer.
- The result is still standard JSON — reversible via the Formatter tool.
Frequently Asked Questions
Does minification lose information?
No. Only formatting is affected; the data is identical.
How does this compare to gzip?
Different layer. Minification removes whitespace. gzip compresses bytes. You can layer both for maximum savings.
Is the output still valid JSON?
Yes. Any compliant JSON parser will read it correctly.
Is there a nesting-depth limit?
Browsers cap JSON depth at hundreds of levels — far beyond typical business data.