JSON Minifier — Compact & Minify JSON Online

What is JSON Minifier?

A JSON minifier removes indentation, line breaks, and whitespace between tokens to produce the smallest possible representation of a JSON document. The saving is meaningful anywhere bytes matter: embedding payloads in URLs or QR codes, storing snapshots in a database column, shipping bundles to the browser, or sending data over slow / metered networks. Because JSON is whitespace-insensitive outside of string literals, minifying is fully lossless — every parser will read the compact form and the pretty-printed form as the exact same value. This tool parses your input with the native JSON.parse then re-serializes with JSON.stringify, so the output is guaranteed to be spec-compliant, and you get a precise before/after byte count.

How to minify JSON online

1. 1Paste your JSON (pretty-printed or already partially compacted) into the left editor.
2. 2The right pane immediately shows the minified single-line output.
3. 3Read the byte-count card below: original size, minified size, and percentage saved.
4. 4Copy the compact output, or fix any parsing errors flagged on the input side with 'Jump to line'.

Use Cases

Code Examples

const minified = JSON.stringify(JSON.parse(input));

import json
minified = json.dumps(json.loads(input), separators=(",", ":"))

jq -c . input.json > minified.json

Key Concepts

Whitespace insensitivity

Per RFC 8259, spaces, tabs, carriage returns, and line feeds are allowed between any two structural tokens but carry no meaning. Removing them is guaranteed lossless.

Minify vs. compress

Minifying removes redundant characters at the JSON syntax level. Compression (gzip, brotli) operates on the byte stream and can further shrink a minified payload — the two are complementary, not overlapping.

Key order preservation

JSON.stringify serializes object keys in the order returned by Object.keys — insertion order for string keys. Minifying does not sort keys; use a JSON sort tool if you need a canonical form for diffing or hashing.

Byte count vs. character count

This tool reports UTF-8 byte counts, which is what actually travels on the wire and what most storage backends charge for. Non-ASCII characters (CJK, emoji) can occupy 2-4 bytes each even though they render as one glyph.

Tips & Best Practices

• ▸gzip already collapses runs of whitespace efficiently — pre-minifying a gzipped API response only saves a few percent. The win is much larger for uncompressed transports.
• ▸If your API sits behind a CDN with automatic minification, don't double-minify — measure first.
• ▸For canonical JSON (for hashing, signing, or diffing), you need a spec like RFC 8785 (JCS) that also sorts keys and normalizes numbers. Plain minifying is not canonical.
• ▸Minified JSON is technically valid but often unreadable in logs — keep pretty-printed copies for debugging and minify only at the transport layer.
• ▸For very large documents, streaming minification (stream-json in Node) avoids loading the whole file into memory.