Loading…
Paste JSON and minify it to the smallest valid form, with a live before/after size comparison — processed entirely in your browser.
Formatted JSON will appear here after you click Format.
Minifying JSON removes every piece of insignificant whitespace — the spaces, tabs, and newlines between tokens — leaving the smallest text that still represents the same data. It is the reverse of beautifying. The values themselves never change.
Smaller payloads mean less data to transfer and slightly faster parsing. Minified JSON is common for production API responses, config embedded in HTML, and data sent over the network where every byte counts. During development you can keep it readable and minify only when shipping.
Minification and compression are different. Minification removes whitespace from the JSON text, and the result is still plain JSON. Compression algorithms such as gzip or brotli further shrink the bytes sent over the wire and are applied by your server or CDN — not by this tool. The two are complementary: you can minify and still serve the result compressed.
Pretty-printed JSON on the left, minified on the right.
{
"id": 1,
"name": "Ada",
"tags": ["json", "tools"]
}{"id":1,"name":"Ada","tags":["json","tools"]}Minifying JSON removes all insignificant whitespace — spaces, tabs, and newlines between tokens — producing the smallest text that still represents the same data.
No. Only whitespace is removed. Every key, value, and type is preserved exactly, so a minified document parses to the same result as the original.
It depends on how much whitespace the original contains. Pretty-printed JSON often shrinks noticeably; already-compact JSON changes little. The tool shows the original size, minified size, and the percentage reduction.
No. Minification only removes whitespace from the text. Compression algorithms like gzip or brotli further shrink the bytes on the wire and are applied by your server/CDN, not by this tool.
No. Minification runs in your browser; your data stays on your device.