Compact payload
Input: { "user": { "id": 42, "name": "Ada" }, "active": true }
Output: {"user":{"id":42,"name":"Ada"},"active":true}
Build and debug
JSON Minifier
Use JSON Minifier to minify JSON online, strip whitespace, and create compact output for smaller payload size without changing the data.
Developer ToolsPublished Mar 12, 2026Last reviewed Mar 12, 2026
Loading tool…
How to use JSON Minifier
- 1
Paste the JSON you want to compress
Start with a valid JSON payload. Formatted fixtures, copied API responses, and exported configuration blocks all work well here.
- 2
Run the minifier
The tool parses the input first, then rewrites it as compact JSON. If parsing fails, fix the syntax issue before trying to generate a smaller payload.
- 3
Copy or download the compact result
Use the output in a request body, embed field, test fixture, or transfer flow where payload size matters more than human readability.
Workflow
Use JSON Minifier when compact output matters more than readability
JSON Minifier is the right tool when you already know the payload should stay the same, but you want compact JSON for transport, embedding, or storage. It removes whitespace that humans like and machines do not need, which helps when payload size is part of the job.
That can be useful for request bodies, test fixtures, configuration fields, or small embed contexts where readable JSON is no longer the priority. The result is smaller, but the parsed structure stays intact.
How it works
Compact output is regenerated from the latest successful parse
The tool does not simply strip spaces from the text you pasted. It parses the input first, then serializes the parsed value as compact JSON. That means whitespace removal happens on a known-good JSON value, not on a random string transformation.
Copy and download actions stay tied to the latest successful run. If you change the input, the previous output becomes stale until you minify again, which prevents accidental reuse of an outdated payload.
Limits
Strict parsing keeps whitespace removal honest
JSON Minifier requires strict JSON because whitespace removal is only safe after a successful parse. Comments, trailing commas, JSON5 syntax, and other non-standard patterns are rejected instead of being normalized into something new.
The page also keeps browser-oriented size and complexity limits. That keeps compact payload generation fast for everyday work, but it also makes it clear that this is not a bulk compression pipeline for huge datasets.
Compare tools
When to use JSON Minifier instead of JSON Formatter or JSON Validator
Use JSON Formatter when the job is readable indentation or pretty JSON for human review. Use JSON Validator when you need syntax, structure, or schema checks and a clear valid or invalid result.
Use JSON Minifier when payload size, whitespace removal, or compact JSON output is the real goal. In short, use this tool when smaller transfer-friendly output matters more than readability or validation.
Example scenarios
Compact array
Input: [ { "service": "payments", "enabled": true }, { "service": "search", "enabled": false } ]
Output: [{"service":"payments","enabled":true},{"service":"search","enabled":false}]
Frequently asked questions
Does minifying change my data?
No. It removes unnecessary whitespace only after the JSON parses successfully, so the parsed values and structure stay the same. That makes it suitable for compact output without semantic changes.
Does it support top-level primitives?
Yes. Strings, numbers, booleans, null, arrays, and objects are all valid top-level JSON values, so the tool can minify more than object-shaped payloads when your workflow starts from a primitive or list.
When are copy and download enabled?
Only when the output belongs to the latest successful minify run. Editing the input makes the compact result stale until you run the tool again, which helps prevent accidental reuse of old output.
How are duplicate keys handled?
JSON Minifier follows `JSON.parse` semantics, so duplicate keys keep the last parsed value before the compact output is generated. If duplicate keys are a problem in your data model, fix them before minifying.
Is processing local to the browser?
Yes. Parsing and minification run in your browser after the page loads, so the JSON stays in this browser session while you work and does not need a server round-trip for whitespace removal.