Minify is not encryption and not gzip
Removing spaces, tabs, and newlines from JSON makes the text shorter. It does not hide data, and it is weaker than HTTP gzip or Brotli, which your server should still enable. Use ToolPin JSON Minify when you need the JSON text itself to be compact: inline config, a file on disk, or a message body you will paste somewhere that does not compress. Everything runs in the browser. Nothing is uploaded. The tool is free and needs no account.
The correct way to minify JSON is parse-then-stringify with no extra whitespace. Deleting spaces with a regex can break strings that contain spaces you actually need. ToolPin parses first; if the input is invalid, you get an error instead of a corrupted file.
What stays, what goes
Keys, strings, numbers, booleans, null, and nesting are unchanged. Indentation and extra blank lines disappear. The order of object keys follows what the JavaScript parser emitted (generally insertion order for ordinary objects). Do not rely on minify to sort keys; if you need canonical JSON for hashing, sort keys in code.
String contents keep their spaces. "hello world" remains "hello world". Only insignificant whitespace between tokens is removed.
Comments are not JSON. They must be gone before minify, or parse fails. Trailing commas fail the same way.
Size expectations
Pretty-printed JSON with 2-space indent is often 20–40% larger than minified, more if it was deeply nested with short keys. After minify, gzip on the wire still helps a lot because keys repeat. Minify plus gzip is normal for production APIs; minify alone is for places without a compressor.
Huge integers have the same precision caveat as the formatter: JavaScript numbers are IEEE doubles. Snowflake IDs should be strings.
Privacy and limits
Minifying in the browser means you can compact a file that contains credentials without sending it to a website that logs pastes. Still, do not paste production secrets into a shared screen.
Very large documents can stall the tab. Use jq -c or a build step in CI for multi-megabyte artifacts.
After you minify
Put the compact file behind gzip in production. Keep a formatted copy in git if humans edit it; many teams store formatted JSON and minify at build time. If you minified only to share a snippet, say so — a one-line blob is hostile in code review.
Need rows for Excel? JSON to CSV wants an array of objects and is also local. Need to inspect the minified result? Paste it into JSON Formatter.