Minify
JSON Minifier
Paste JSON on the left, hit Run, copy a smaller file that is harder to read and quicker to download. No Node, no pip, no Docker for a five-minute job. That is the json minifier.
Drop a file on the left. Drafts stay in this browser. Shortcut: Ctrl or Cmd + Enter to run.
How this json minifier works
- Paste or drop a .json file into the input on the left.
- Flip options if you see them (comments, indent, case). Defaults are the safe ones.
- Hit Run, or Ctrl / Cmd + Enter. Leave “Process on server” off unless you mean it.
- Read the status line, then copy, download, or jump to a related tool.
What this json minifier is for
The file is already in front of you. You need to minify it without opening a whole IDE profile. Paste, run, copy. Typical timing: right before a static deploy, an email snippet, or an inline SVG — not while you are still designing the component.
You walk away with a smaller file that is harder to read and quicker to download.
What it will not pretend to be
This is not a replacement for gzip/Brotli, tree-shaking, or a real bundler. Those still matter more at scale. JSON has no comments, no trailing commas, and no undefined. If your payload has those, you want JSONC or a JS object — not strict JSON.
By default nothing leaves the tab. Tick “Process on server” only if you want to compare results or use gzip numbers that match the server library.
A practical way to use it
Drop a .json file onto the input or paste. Flip options if they are there. Run. Read the status line. Copy or download. Drafts stay on this device so a refresh does not punish you.
When you are done, hop a related tool instead of starting over: minify and beautify toss the file back and forth, format and validate often share a parser, convert wants valid input first.
The small print that saves a round-trip
JSON has no comments, no trailing commas, and no undefined. If your payload has those, you want JSONC or a JS object — not strict JSON.
You searched “json minifier online.” You got an editor, not a login wall. That is the deal.
Frequently asked questions
What does JSON minify remove?
Whitespace only — and only if the JSON is valid. {\n "ok": true\n} becomes {"ok":true}. It will not delete keys. It will refuse trailing commas instead of “being helpful.”
Example?
Pretty: {"tools": ["minify", "format"]}. Minified: {"tools":["minify","format"]}. Same document. Smaller paste into an env var or a single-line log.
Fun fact?
Fun fact: gzip loves pretty JSON almost as much as minified JSON because keys repeat. Minify still wins a little. The dramatic win is gzip on the API response, not deleting two spaces in a config you keep in git.
Should config files in git be minified?
Usually no. Humans diff pretty JSON. Minify for the wire, the cookie, or the process.env.PAYLOAD that hates newlines.
Can I minify JSONC?
Strip comments first, then minify as JSON. {"ok": true // flag} is not JSON until the comment is gone.
Will minify sort keys?
It should not, unless you asked a canonicalizer. Order can matter to some naive diffs and to some signed payloads. Do not sort “for beauty” on a JWT-like JSON blob.
Unicode and minify?
{"city":"München"} can stay as UTF-8 or become \u00fc depending on the encoder. Both are valid. UTF-8 is nicer to read. Escapes are nicer for some old pipes.
Minify vs stringify in code?
JSON.stringify(obj) is minify in code. This page is for the string already sitting in your paste buffer. Same idea, different door.