JSON to SQL Insert
Turn an array of JSON records into INSERT statements, with an optional CREATE TABLE.
Strip every optional byte from a JSON document and see what you saved.
The JSON Minifier strips every byte a parser does not need — indentation, line breaks and the spaces after colons and commas — and reports exactly how much smaller the document became. The data itself is untouched.
Minifying JSON removes every character a parser does not need: the indentation, the line breaks and the space after each colon and comma. The data is untouched — the same document goes in and comes out, only smaller.
The saving is usually larger than people expect. A pretty-printed API response is commonly 20 to 40 per cent whitespace, and on a payload sent thousands of times a day that adds up. The tool reports the size before, the size after, the bytes saved and the percentage, so you can decide whether it is worth doing. It can optionally sort keys at the same time, which makes two minified payloads directly comparable.
Size before, size after, bytes removed and the percentage are all reported, so you can judge whether minifying is worth it.
Only whitespace outside string values is removed. Spaces inside your strings, key order and array order all survive exactly.
Sort keys while minifying so two payloads from different services become directly comparable.
Escape non-ASCII characters as \u sequences when the payload has to pass through a system that mangles UTF-8.
A document that cannot be minified is a document that does not parse, and the error tells you where.
Any formatted or partially formatted JSON document works.
Optionally sort keys alphabetically or escape non-ASCII characters as \u sequences.
The stat row shows the original size, the minified size and the percentage removed.
Take the result to your clipboard or save it as a .json file.
No. Only whitespace outside string values is removed. Every key, value and array order is preserved exactly, and spaces inside a string are untouched.
It depends entirely on the indentation. A file indented with four spaces and deeply nested can lose 40 per cent of its size; an already compact one may lose almost nothing.
The gain is smaller because gzip compresses repeated whitespace very well, but minifying still helps: it reduces the bytes the parser has to walk and the memory the string occupies.
It rewrites characters such as é or 中 as \u00e9 and \u4e2d. The result is pure ASCII, which is safer through old systems but slightly larger.
What people who use the JSON Minifier think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the JSON Minifier. It takes half a minute and no account.
Write the first reviewTurn an array of JSON records into INSERT statements, with an optional CREATE TABLE.
Reformat a MAC address between every notation, and decode what it means.
Convert a TOML config to JSON, with tables and arrays of tables resolved.
Check a JWT signature against a secret or a public key, and see why it fails.
See your own user agent string and what a server can tell from it.
Convert between signed and unsigned, with the negation steps shown.
Build a cron schedule from controls and see the next times it runs.
Convert between bytes, KiB, MB, GB and bits, in both systems.