JSON Minifier

Making JSON smaller without changing the data

Minifying JSON removes the spaces, tabs and line breaks that make it easy for people to read but add nothing for machines. The data itself stays exactly the same: every key, value and array item is kept. Smaller JSON is quicker to send over a network, takes less space in a database or cache, and fits more comfortably into places with size limits, such as environment variables, URL parameters or message queues.

This tool parses the input before writing it back out, which brings two benefits. The output is guaranteed to be valid JSON, and any errors in the input are reported rather than silently copied. If the original contained comments or trailing commas, they will need to be fixed first, since standard JSON does not allow them.

How much you save depends on how the original was formatted. Deeply indented files with many short values can shrink by a third or more, while data that is mostly long strings will shrink less. For APIs, compression such as gzip or Brotli on the server usually saves more than minifying alone, and the two work well together. Keep the readable version in your source code or documentation and minify only when the data is stored or sent, because hand-editing minified JSON is error-prone. If you need to inspect a minified response later, the formatter turns it back into an indented, readable layout in one step. Everything runs locally, so production data and secrets never leave your browser. Running it as a final check before deploying configuration also catches stray errors before they reach production.