Validate JSON and remove whitespace outside strings.
When is it useful? Minify JSON removes all unnecessary spaces and line breaks from JSON, making the file smaller for websites, apps and APIs, and easier to paste into a single line.
Good to know: the JSON is validated first. Only whitespace outside of text values is removed — spaces inside strings are kept — and numbers are not rewritten. The data stays exactly the same; only its layout changes. Files up to 2 MB are supported.
| In your JSON | After minifying |
|---|---|
| Spaces and line breaks outside text | Removed |
| Spaces inside strings | Kept |
| Numbers | Not rewritten |
| The data | Stays exactly the same |
| JSON check | Done first |
Browser processing: your files are processed on your own device and are never uploaded to our server.
Spaces, indentation and line breaks make JSON readable for people but add size that computers do not need. Minified JSON loads faster in websites and apps, uses less bandwidth, and fits into a single line for configuration fields, environment variables and API tests.
Upload a .json file of up to 2 MB. It is checked to be valid JSON first, then all whitespace outside text values is removed. Spaces inside strings are kept, numbers are not rewritten, and key order is unchanged — the data stays exactly the same.
Savings depend on how the file was formatted: nicely indented JSON often shrinks by 20–40%. For websites, combine minification with gzip or Brotli compression on your server for the biggest savings.
“Invalid JSON”: fix the reported problem — often a trailing comma or comments. You need to read the file again: use Format JSON to expand it. Escaped characters look strange: they were already in the original and are kept exactly.
Keep a formatted copy for editing, minify only for deployment, and test the application with the minified file.