A precise JSON minifier: parses any valid JSON and returns the smallest byte-equivalent representation, computed locally with no server round trip.
Free · no account · nothing leaves your browser
The tool
This tool parses any valid JSON, however it is currently formatted, spread across many lines, inconsistently indented, already partly compact, and returns the smallest valid representation of the exact same data: no line breaks, no indentation, no unnecessary whitespace between tokens.
The conversion runs entirely in JavaScript in your browser. There is no request sent to a server, and no run limit, since nothing here costs anything to serve.
The underlying fact
JSON's grammar treats the spaces, tabs and line breaks between its structural characters, braces, brackets, colons, commas, as entirely optional. '{"a":1}' and the same object spread across five indented lines describe identical data to any parser. The formatting exists solely for a human reader, never for the machine consuming it.
That fact is precisely what minifying exploits: since none of that whitespace carries meaning, removing all of it produces output that is functionally identical to the original while occupying fewer bytes.
How it works
No configuration, nothing to install.
Why it matters
The saving is purely a byte count, nothing about the data's structure or meaning is altered. For a payload embedded in a URL query parameter, a value placed into an environment variable, a script tag's inline data, or a '.min.json' asset shipped to every visitor, each removed byte is one less byte to transmit and parse.
For a small, one-off object the difference is negligible. For a large configuration file, a sizeable API response used as a test fixture, or an asset served across thousands of page loads, the removed whitespace amounts to a real, if modest, reduction in transfer size.
A side effect worth knowing
Minifying anything requires this tool to parse it first, so anything that is not syntactically valid JSON, a trailing comma, an unquoted key, a comment, is rejected outright with an error rather than silently mangled. That makes this tool a quick validity check as a side effect, even when reducing size was not the original purpose.
A frequent cause of that rejection is pasting JSON5 or JSONC, formats permitting comments and trailing commas that look almost identical to plain JSON. Standard JSON supports neither, so text copied from a configuration file written in one of those relaxed formats fails here until the comments and trailing commas are removed.
Straight answer
No, and this is worth stating directly. This tool confirms that the pasted text follows JSON's syntax rules, correctly matched braces and brackets, properly quoted keys, no trailing commas. It has no way of knowing whether the values inside are the right values, whether a required field is missing, or whether a number should have been a string.
Syntactic validity and correctness are distinct properties. Minifying, and its counterpart, pretty-printing, address only the first.
Who it's for
Developers use it to shrink a configuration value that must fit into a single environment variable, a URL parameter or a command-line argument. Front-end engineers use it to compact a small JSON asset before it ships to every page load, when a build tool's own minification step is unavailable.
Anyone preparing a JSON payload for a single-line log entry, a database column that handles line breaks poorly, or a message field with a length limit uses it to compress the JSON to one clean line without altering any of the data inside.
All answered in full, nothing to click open.
Paste the JSON into the input field and press Minify. The compact, single-line version appears in the output panel, ready to copy.
Yes. No signup, no length cap, no run limit, since the conversion runs on your own device.
No, parsing and minifying happen entirely client side. Nothing is transmitted, stored or logged.
No, only whitespace between structural characters is removed. Every key, value and array item remains exactly as it was.
The pasted text doesn't follow JSON's syntax rules, most commonly a trailing comma, an unquoted key, or a comment, none of which standard JSON permits.
No, standard JSON supports neither comments nor trailing commas, so text in those relaxed formats needs both removed first.
No, keys retain the exact order they appeared in the input. Minifying only removes whitespace, it does not reorganise structure.
No. There's no cap and no run limit, only your device's own memory.
Yes, the layout adapts to narrow screens.
This removes all unnecessary whitespace to minimise size. The prettifier does the reverse, adding indentation and line breaks for readability.
No, it only confirms the syntax parses. It cannot determine whether a value is wrong, a field is missing, or a number should have been a string.
No, the result describes exactly the same data as the input. Minifying is a lossless transformation with respect to the data itself.
Yes, any valid JSON value, an object, an array, a string, a number, minifies identically.
Not currently. This is a single-paste, browser-based tool.
It cannot, since standard JSON does not support comments at all, so a file containing them fails to parse rather than having them stripped.
A manual find-and-replace can corrupt string values that legitimately contain a line break or extra spaces. This tool parses the structure first, so it never touches a string value incorrectly.
Yes, valid JSON string content passes through unchanged, since minifying affects only whitespace between structural characters.
Yes, nothing is transmitted anywhere. Processing happens locally in your browser.
That depends entirely on how much whitespace the original carried. A heavily indented, deeply nested file shrinks more than one that was already fairly compact.
Yes, minified JSON is exactly as valid as pretty-printed JSON to any parser. The formatting change has no bearing on how it is consumed.
Computed locally, no upload, no run limit.
Open the minifier