What does minifying JSON do?

Minifying removes all unnecessary whitespace, indentation, and line breaks from JSON. The data stays identical — only the formatting characters are stripped. This reduces file size, often by 30-60% for typical JSON.

When should I minify JSON?

Minify JSON before sending it over a network (API responses, config files in production, stored data). The smaller payload means faster transfer times and lower bandwidth costs. Don't minify JSON that humans need to read.

How much space does minification save?

It depends on the indentation depth. A 2-space indented file with deeply nested objects can shrink by 40-60%. A flat array with short values might only shrink 10-15%. Use our Size Analyzer to see the exact difference.

Does minifying change the data?

No. Minification only removes formatting whitespace. All keys, values, arrays, and nested structures stay exactly the same. JSON.parse() produces identical results for both the formatted and minified versions.

Минификация JSON

Сжатие JSON, удаление пробелов

Loading editor...

Shrink JSON before it crosses the wire

Whitespace and indentation are great for humans but pure overhead for the network. Minifying JSON strips them out, often cutting payload size by 30-60%, so API responses, config files, and embedded data load faster without changing any of the actual data your code consumes.

Use the minifier when you need to

Reduce API response size

Strip indentation from JSON before serving it to clients to save bandwidth and reduce time-to-first-byte.

Embed JSON in HTML or strings

Compact JSON before injecting it into a script tag, environment variable, or single-line config value.

Compare actual payload size

Minify both versions of a payload to measure the structural difference without indentation noise.

How to minify JSON quickly

1
Paste the formatted JSON into the editor.
2
Click Minify to remove all whitespace, indentation, and line breaks.
3
Copy the result or download it for use in production payloads.

Keep going

See where the bytes go

Drill into which fields contribute most to payload size before deciding what to trim.

Format minified JSON

Reverse the process when you receive minified output and need to read it.

Validate before minifying

Make sure the input is syntactically valid so the minified output stays parseable.

Diff before and after

Confirm minification only removed whitespace and didn't touch any values.

Common minifier workflows

Trim API response payloads

Send JSON without indentation in production while keeping pretty-printed copies for debugging.

Inline configuration in build outputs

Embed JSON config inside JavaScript bundles or HTML templates without expanding bundle size.

Prepare data for storage size limits

Squeeze a payload under DynamoDB, Redis, or column-size limits without restructuring the data.

Часто задаваемые вопросы

Удаляются лишние пробелы, отступы и переносы. Семантика данных не меняется — только форматирующие символы. Размер файла обычно уменьшается на 30–60%.

Перед отправкой по сети: ответы API, продакшен-конфиги, хранение. Меньше полезная нагрузка — быстрее передача. Для ручного чтения минификация не нужна.

Зависит от глубины отступов: для глубокой вложенности с отступами 2 пробела часто 40–60%, для плоских массивов — 10–15%. Точную разницу покажет анализатор размера.

Нет. Убирается только пробельное форматирование. Ключи, значения, массивы и вложенность те же. JSON.parse даёт одинаковый результат для форматированного и минифицированного варианта.