Loading...
Strip whitespace from JSON to reduce file size. Shows exact savings. Your data never leaves your browser.
JSON Input
Minified Output
Pro tip
Shipping oversized JSON configs in your PRs? Git AutoReview flags unnecessary whitespace bloat and suggests minification where it matters.
Paste your JSON into the editor and the tool minifies it automatically as you type. Press Ctrl+Enter to trigger manually, or drag and drop a .json file. The result shows original size, minified size, and exact percent saved.
API responses are the biggest win — a formatted 80KB response can shrink to 50KB minified, and that 37% reduction shows up in real transfer time on slow mobile connections and high-traffic endpoints where you pay per GB. Config files that ship with a deployed app are another good target: tsconfig.json, package.json, and similar files read by build tools at startup do not need human-readable indentation once they leave your repo.
Where it does not matter: JSON files that developers edit directly. Minifying your .eslintrc and accidentally committing it makes the next person who opens it miserable. Keep source configs formatted; minify only the production artifact.
The tool calls JSON.parse() on your input (which validates it), then JSON.stringify() with no spacing argument. The result is semantically identical JSON with all indentation, newlines, and spaces around delimiters removed. String values and object keys preserve their content exactly.
The formatter takes valid JSON and spreads it out with indentation and line breaks so humans can read it. The minifier strips all of that back out. Both run a JSON.parse() validation pass first, so both reject malformed input with a clear error message rather than silently producing garbage output.
This tool uses JSON.parse() and JSON.stringify() — both browser built-ins. No network requests, no server. Your JSON stays on your machine. Verify this by opening DevTools Network tab while using the tool; you will see zero outbound requests.
Press Ctrl+Enter to minify manually. Press Ctrl+Shift+C to copy the minified output. The tool also auto-minifies as you type with a short debounce.
Strips all whitespace that JSON uses for human readability — indentation, newlines, spaces around colons and commas. The structure and values stay exactly the same. Only the bytes used to make it readable get removed.
Everything runs in your browser via JSON.parse() and JSON.stringify(). No server calls, no data transmitted. Open DevTools Network tab to confirm zero outbound requests.
API responses are the main win — every byte you cut shows up in transfer time, especially on slow mobile connections and high-traffic endpoints where bandwidth costs real money. Build artifacts are another good target: your tsconfig.json and package.json do not need human-readable indentation once they ship. Where you should NOT minify: any config file a developer edits directly, because the next person to open it will hate you.
They do the exact opposite thing. Formatting takes valid JSON and spreads it out with indentation and line breaks so humans can read it comfortably. Minifying strips all of that back out. Both tools validate the input first, so both reject malformed JSON with a clear error message rather than silently producing garbage output.
Typically 20-40% on well-formatted JSON — a config with deep nesting and 4-space indentation can hit 50%+. But JSON that was already barely formatted saves almost nothing; if your original file has no extra whitespace, there is nothing to strip. The tool shows exact original size, minified size, and percent saved so you can see immediately whether it is worth doing.
No — JSON.parse produces an identical object tree before and after minification. The only thing that changes is byte count. We validate the JSON first, so if your input is malformed the tool tells you rather than silently mangling output.
Ctrl+Enter (Cmd+Enter on Mac) to minify, Ctrl+Shift+C to copy the minified output.
Developer Toolkit by Git AutoReview
Free tools for developers. AI code review for teams.