Format vs Minify — The Core Difference
Both operations parse your JSON and output the same data. The only thing that changes is whitespace.
Formatting adds indentation and line breaks to make JSON readable for humans. Minifying removes all whitespace to make JSON as small as possible for machines. The actual data — keys, values, structure — is identical in both versions.
When to Format JSON
Format JSON when you need to read it:
- You received a minified API response and want to understand its structure
- You are debugging and need to inspect the shape of your data
- You are writing documentation and want readable examples
- You are doing a code review and need to compare two JSON payloads
When to Minify JSON
Minify JSON when size matters:
- Sending JSON in an HTTP request body — smaller payload means faster transfer
- Storing JSON in a database TEXT column — fewer bytes means lower storage cost
- Embedding JSON in an HTML page inside a script tag
- Deploying a large JSON configuration file to production
How Much Size Does Minification Save?
A typical API response with moderate nesting saves around 20 to 35 percent. Heavily indented JSON with 4-space indent can save up to 50 percent.
JSONKit's Minifier shows the exact input size, output size, bytes saved, and percentage saved in the stats bar at the bottom of the output panel so you always know the real impact.
Sort Keys — a Third Option
Between format and minify there is a third option. Sort Keys formats the JSON with alphabetically sorted keys at every level. This is useful for diffing, documentation, and producing deterministic output.
The Workflow
Paste once, toggle between Format and Minify as needed, then download or copy the version you want. Both actions work from the same input without re-pasting.