JSON Minifier

What Is JSON Minification?

JSON minification removes insignificant whitespace from valid JSON and produces a compact representation. The output commonly appears on one line, but the important property is that whitespace between JSON tokens is removed without changing the parsed data.

A standard minifier parses the input and serializes it again. This is safer than deleting every space character because spaces inside JSON string values are meaningful and must remain unchanged.

How to Minify JSON

1. Enter JSON: Paste formatted JSON or open a local .json file.
2. Validate the input: Confirm that the source is valid standard JSON.
3. Minify: Parse and serialize the document without indentation or unnecessary token spacing.
4. Compare sizes: Review original and minified character or byte counts.
5. Copy or download: Use the compact output in an API, application asset, configuration workflow, or local file.

What Does a JSON Minifier Remove?

It normally removes whitespace between JSON tokens, including indentation, line breaks, and spaces around structural punctuation. For example:

{
  "name": "Alice",
  "active": true
}

can become:

{"name":"Alice","active":true}

The space inside a value such as "New York" is not removed because it is part of the string data.

JSON Minification vs Compression

Minification and compression are different operations. Minification changes the JSON text by removing formatting overhead. Network compression such as gzip or Brotli encodes the resulting bytes using a compression algorithm. Many HTTP servers can apply gzip or Brotli automatically even when the source JSON is formatted or minified.

Minification may still be useful for static assets, embedded payloads, storage, or workflows where the raw JSON text itself is transmitted or measured. Do not assume that minification alone provides the same benefit as HTTP compression.

How to Measure Savings

Character count and byte count are not always identical. For ASCII-only JSON they may be similar under common encodings, but non-ASCII text can occupy multiple bytes in UTF-8. A useful size comparison should identify whether it measures JavaScript string length, encoded UTF-8 bytes, or file bytes.

Percentage savings can be calculated as:

savings = (originalSize - minifiedSize) / originalSize × 100

Always compare the same measurement unit before interpreting the percentage.

Minification Does Not Change String Content

A safe minifier must preserve whitespace and escape sequences inside quoted strings. Consider:

{"message":"Line one\nLine two","title":"New York"}

The newline escape and the space inside New York are data. Removing them would change the value and make the operation incorrect.

JSON, JSONC, and JSON5

Standard JSON does not permit comments or trailing commas. JSONC and JSON5 are related formats that add features such as comments, single-quoted strings, or relaxed syntax. A strict JSON minifier should reject those inputs unless it explicitly supports a JSONC or JSON5 parsing mode.

Some specialized minifiers remove comments from JSON-like content, but that is a transformation beyond standard JSON minification. It should be clearly labeled because comments may contain important documentation.

When to Minify JSON

• Production assets: Reduce raw file size for static JSON resources.
• Embedded data: Place compact JSON inside generated code or templates.
• Storage: Store a compact representation when human readability is not needed.
• Fixtures: Create one-line test data when that format is useful for a test harness.
• Build pipelines: Automate minification during deployment while preserving a readable source file.

When Not to Minify JSON

Keep formatted JSON when people need to review or edit it, when it is maintained in version control, or when clear diffs are more valuable than raw text size. A common workflow is to keep a readable source version and generate minified output as a build artifact.

Browser-Based Privacy

This minifier is designed to parse and serialize JSON in the browser instead of sending the input to a remote service. That is convenient for development data and configuration snippets, but it is not a secret-management system. Avoid entering credentials, tokens, private customer data, or confidential production information into any online tool.

Production Alternatives

For repeatable builds, use a local formatter, a CI step, or a command-line tool such as jq -c. A production workflow should validate the output, retain a readable source copy, and test the minified file in the target application.