Minify JSON while retaining string values
Minifying creates a copy without indentation and unnecessary whitespace between values. Spaces inside strings are data, so inspect them separately from the formatting whitespace that surrounds objects and arrays.

How to use this tool
- Choose files in JSON format. Maximum files per batch: 1.
- Check the input format and file order, then start processing.
- Download the JSON result and check its content and quality.
Choose the right settings
Choose a valid JSON file and run the tool without additional settings. Keep a readable source copy so that later review of the values and structure does not depend on reading the compact output.
- Supported input
- JSON
- Output
- JSON
Before you start
Establish the meaning of the input
Before converting or arranging data, identify what a row or value represents and keep a source copy. In tabular files, review headers, separators and text encoding; in structured files, inspect the required object or array shape. Identifiers, dates and amounts should not be interpreted solely from how a spreadsheet happens to display them.
Where the tool offers matching columns, type rules or output fields, choose them according to the destination’s requirements. Test a sample with a blank, a repeated value and a value containing punctuation. For labels, charts or personalized documents, check which column supplies each displayed value and whether the source units and wording are correct.
Define a few checks before processing: an identifier that must retain its spelling, a value with a known interpretation and an expected relationship between records. If the tool offers type conversion or matching rules, distinguish a source value from the program’s display of it. Test ambiguous dates or differently written keys before accepting a broad rule. Keep the chosen rules and destination requirements with the result; this makes a discrepancy traceable to input, interpretation or the requested transformation.
Verify values, structure and exceptions
Reopen or import the result using the destination’s settings. Compare headers, record counts and several values with the source, allowing for the operation you requested. A summary, split or duplicate-removal task can legitimately change the count; verify why it changed rather than expecting every transformation to keep identical rows.
Inspect any exception or validation report before continuing. If columns shift, characters are garbled or a key is not found, check delimiters, encoding and exact header spelling first. Encoding data does not encrypt it, and formatting a value does not confirm its meaning. For printed codes or labels, test the actual output before making the full set.
Example input and output
indented JSON → compact JSONExamples describe the workflow. Results depend on the source file and settings.
Check the saved result before using it
Parse the saved file again and compare required keys and array lengths. Review string values such as names and sentences that contain spaces to confirm that their content remains appropriate.
If the result is different from what you expected
Comments or trailing commas must be corrected before processing valid JSON. The result remains a JSON text file; it does not become a compressed format such as GZIP simply because formatting space was removed.
Limits to keep in mind
- Minification is not ZIP compression. Parsed numbers remain subject to JavaScript precision limits.
Continue with a related tool
This guide explains the public browser tool. Keep a copy of the original and inspect the result before sharing it.