JSON WORKSPACE
JSON Minifier
Compact JSON text.
Input is processed on this site only when you run the tool. The application does not save inputs or results.
input.json
Result result.json
A little clarity goes here.
Run the tool to see your result.
Result preview
UTF-8 text, at most 262144 bytes per input. Tab leaves the editor. Plain text disables syntax colors. Browser textareas may normalize line endings to LF.
{"minify":{"inputMode":"text","options":[]}}{"minify":{"input":"{\n \"project\": \"Example\",\n \"active\": true\n}","output":"{\"project\":\"Example\",\"active\":true}","options":[]}}A QUICK WALKTHROUGH
A familiar workflow,
with room to focus.
Paste a valid JSON document.
Choose Minify to remove insignificant whitespace.
Copy the compact JSON, with numbers and quoted text preserved.
When to use JSON Minifier
Remove indentation from JSON before using it in a compact text field or comparing the exact transport representation.
Read the result
The output is JSON text with insignificant whitespace removed. Spaces inside strings and number spellings remain; minification is not compression or semantic canonicalization.
SEE IT IN PRACTICE
Worked examples
Sample input. A result you can inspect.
Minify example
Input
{
"project": "Example",
"active": true
}Expected result
{"project":"Example","active":true}Formats, limits and common errors
Remove comments and trailing commas. Quoted spaces and escaped newlines belong to the data and are retained.
- Only whitespace outside strings changes; Unicode escapes, numeric spelling, member order and duplicate members remain.
- Duplicate keys produce an ambiguity warning. This tool does not compress files or repair JSON.
- At most 64 container levels and 10,000 values per input.
- Input: 262,144 UTF-8 bytes per text field. Output: at most 524,288 UTF-8 bytes; serialized responses have a separate 1 MiB ceiling. Size/work failures return no partial result.