Minify & Compress
JSON Online Free

Everything you need to shrink your JSON

Your data never leaves your device

Related JSON tools

Common questions answered

What is JSON minification?

JSON minification removes all unnecessary whitespace — spaces, tabs, and line breaks that exist purely for human readability. The result is a single-line string with the same data in the smallest valid representation. Minified JSON is standard practice for API payloads, configuration storage, and anywhere bandwidth or storage matters.

Minification can significantly reduce JSON size. A formatted 10 KB configuration file might shrink to 4 KB after minification — a 60% reduction. This adds up in APIs handling thousands of requests per second. This tool minifies instantly in your browser without uploading data, making it safe for production credentials and sensitive payloads.

{
  "name": "Alice",
  "age": 30,
  "roles": [
    "admin",
    "editor"
  ]
}

{"name":"Alice","age":30,"roles":["admin","editor"]}

Get the most out of this tool

• Minify JSON payloads before storing them in databases — it reduces storage costs and improves read performance.
• Compare file sizes before and after minification to measure the whitespace overhead in your configuration files.
• Always validate before minifying — minifying invalid JSON just produces a smaller broken string.

Why minify JSON and how it works

JSON minification removes all whitespace characters — spaces, tabs, newlines, and carriage returns — that are not inside string values. The resulting JSON is semantically identical to the original but occupies significantly less space. For a typical formatted JSON document with 2-space indentation, minification reduces file size by 20–40%. For deeply nested documents with many levels, the reduction can exceed 50%.

The minification process requires a full JSON lexer rather than a simple regular expression. A naive approach of removing all whitespace would corrupt string values that intentionally contain spaces or newlines. The correct approach tokenizes the JSON character by character, strips whitespace between tokens, and preserves whitespace within string token boundaries. This tool uses the same Lexer → AST pipeline as the formatter, guaranteeing that the minified output is valid JSON equivalent to the input.

HTTP payload size directly affects API latency. Every byte transmitted over the network takes time, especially on mobile connections where bandwidth is constrained. For an API endpoint called thousands of times per second, reducing response size by 30% can meaningfully reduce bandwidth costs and improve Time to First Byte (TTFB) metrics. Many production APIs minify JSON responses by default for exactly this reason.

Gzip and Brotli compression algorithms, used by every modern web server, are highly effective on JSON because JSON has many repeated patterns (keys appear many times across array elements). After gzip, a minified JSON and its pretty-printed version often compress to nearly the same size — the compression algorithm re-adds the predictable whitespace patterns efficiently. This means minification provides the most benefit for environments where content encoding is disabled or where you measure raw byte count (like localStorage quotas or Cloudflare Worker limits).

localStorage has a 5MB limit in most browsers. If you store large JSON structures client-side (caches, user preferences, offline data), minification is an easy way to fit more data within the quota. Similarly, Cloudflare Workers have a 128KB script size limit and a 128KB KV value size limit — minifying embedded JSON configuration objects can make the difference between fitting and not fitting.

Minified JSON is also used for embedding in HTML. When you include JSON-LD structured data for SEO or pass initial data to a JavaScript framework via a <script> tag, minified JSON reduces the bytes the browser must parse before the page is interactive. Google's PageSpeed Insights rewards smaller initial document sizes, making JSON minification relevant for Core Web Vitals scores.

When developers use this tool

Things to know before minifying

• Minification is reversible: A minified JSON document can always be reformatted to pretty-printed form. If you need to debug minified production JSON, paste it into the formatter tab to restore indentation and structure.
• String whitespace is preserved: Spaces and newlines inside string values are never removed. If a field value is "Hello, world" with a space, the space remains in the minified output. Only inter-token whitespace is stripped.
• Gzip often eliminates the size benefit: If your server sends gzip-encoded responses, the size difference between formatted and minified JSON after compression is typically under 5%. Minification still helps for uncached edge cases and environments without compression.
• Don't minify JSON you need to read: Log files, configuration files, and other developer-facing JSON should stay formatted. Reserve minification for machine-to-machine communication where a human will rarely inspect the raw data directly.

Additional frequently asked questions