What JSON minification does
Minifying JSON strips every character that isn't part of the actual data — indentation, line breaks, and spaces around colons and commas — without changing the value it represents. The result parses to exactly the same object, just in fewer bytes.
Why it matters
- Smaller API payloads. Whitespace adds up fast in deeply nested or array-heavy responses — minifying can shave a meaningful percentage off response size, which matters most on slow or metered connections.
- Smaller config/data files. Bundled JSON (locale files, static data, generated manifests) ships smaller when minified.
- Faster to copy/paste. A single-line payload is easier to drop into a curl command, an environment variable, or a one-line config field.
Does minifying lose any information?
No. JSON whitespace outside of string values is not meaningful — removing it doesn't change a single key or value. The only thing minifying "loses" is human readability, which is exactly the tradeoff you're making on purpose.
FAQ
How is this different from the JSON Formatter?
Same underlying operation, different default: this page defaults to producing the smallest possible output and shows you exactly how many bytes you saved. If you also want to switch back and forth between pretty-printing and minifying in one place, the JSON Formatter tool supports both modes.
I'm minifying an IAM policy to fit AWS's size limit
Worth checking first: for most IAM policy quotas, AWS already ignores whitespace when measuring size, so minifying often doesn't change whether it fits — see IAM Policy Minifier, which checks the result against the actual limits and flags the one case (a passed STS session policy) where minifying genuinely helps.
Is my JSON uploaded anywhere?
No — minification happens entirely in your browser using the native JSON parser.