About JSON Minifier

Minify JSON with size statistics. Part of the DevTools Surf developer suite. Browse more tools in the JSON collection.

Use Cases

• Reduce JSON config size before embedding in HTML pages
• Minimize payload size for bandwidth-constrained mobile APIs
• Compact JSON logs before archiving to save storage costs
• Prepare minified JSON for URL query parameters or cookies

Tips

• See the byte savings percentage after minification
• Compare original and minified sizes side by side
• Use minified JSON to reduce API payload transfer size

Fun Facts

• Removing whitespace from a typical pretty-printed JSON file can reduce its size by 20-40%, depending on nesting depth and key lengths.
• JSON was specified by Douglas Crockford in 2001 and formalized as ECMA-404 in 2013, deliberately designed to be a minimal data format.
• HTTP compression (gzip/brotli) applied after minification typically achieves 70-90% total size reduction compared to pretty-printed JSON.

FAQ

How much smaller does minification make my JSON?

Typically 20–40% smaller depending on how much whitespace and indentation your source had. API payloads minify less than hand-formatted config files.

Does minifying change the actual data?

No. Key order and values are identical — only whitespace (spaces, newlines, tabs between tokens) is removed. Every parser produces the same result from minified and pretty-printed input.

Is minification worth it for HTTP responses?

Gzip compresses pretty-printed JSON almost as well as minified JSON, so at the HTTP layer the gain is small. Minify when you can't gzip — localStorage, embedded JSON in HTML, Terraform state.

Can I re-expand a minified JSON file?

Yes — paste it into the JSON Formatter with the indent of your choice. Minification is fully reversible.