Add your JSON
Paste text, load the example, or open a local .json file up to 10 MB.
100% local JSON tool
Paste JSON, make it smaller or readable, then copy the result. Nothing is uploaded.
No account · no upload · no installation
01 — 03
The tool validates before it transforms, so invalid input never becomes a misleading result.
Paste text, load the example, or open a local .json file up to 10 MB.
Remove optional whitespace or format the data with two or four spaces.
Review the UTF-8 byte change, then use the valid result wherever you need it.
EXAMPLES & SYNTAX
The parser preserves JSON values while changing only the representation required by this tool.
{
"site": "jsonminify.org",
"enabled": true,
"items": [1, 2]
}{"site":"jsonminify.org","enabled":true,"items":[1,2]}{"name":"value"}Keys and string values require double quotes.
[1, 2, 3]Items keep their original order.
true · false · nullThese tokens are lowercase and are not quoted.
space · tab · line breakOptional outside strings; meaningful inside quoted strings.
WHY JSONMINIFY.ORG
Standard browser APIs do the work. There is no account, upload queue, or hidden repair step.
Your JSON is parsed on this device and is not sent to our server.
Strict JSON.parse behavior catches comments, trailing commas, and unquoted keys.
Compare actual UTF-8 bytes before and after minifying instead of character counts.
COMMON USE CASES
Minification is most useful when whitespace adds no value to the next system or person receiving the data.
Reduce large copied payloads before saving them as fixtures, attaching them to bug reports, or moving them between development tools.
Compact JSON placed in HTML data blocks, static assets, or generated application bundles where optional formatting increases transfer size.
Produce a clean single-line value for environment variables, command-line arguments, and systems that expect compact JSON text.
Normalize valid JSON into a predictable compact form before comparing fixtures, storing examples, or sharing diagnostic output.
JSON REFERENCE
A minifier should remove presentation whitespace while preserving the parsed JSON value. Understanding that boundary prevents accidental data changes.
Spaces, tabs, and line breaks between JSON tokens are not part of the data model. After parsing succeeds, the tool serializes the value without optional whitespace.
Comments, trailing commas, unquoted property names, undefined, and JavaScript expressions are not standard JSON. The tool reports an error instead of silently guessing a repair.
File size is calculated with TextEncoder, so emoji and non-Latin characters are counted by their actual UTF-8 byte length rather than by JavaScript character count.
Removing whitespace makes JSON smaller, not secret. Anyone who receives the result can parse it, so sensitive values still require appropriate access controls.
FAQ
Straight answers about validity, privacy, file size, and what the tool changes.
No. Minifying, formatting, validation, copying, and download preparation happen in your browser. The site does not receive your JSON.
It removes optional whitespace after parsing standard JSON. Values remain equivalent, although object key order should not be treated as a semantic guarantee.
Standard JSON requires double-quoted keys and strings. It does not allow comments, trailing commas, undefined values, or JavaScript object literal syntax.
The local file importer accepts .json files up to 10 MB. Available device memory and browser limits can still affect unusually complex files.
Unminify parses the JSON and writes it again with either two or four spaces of indentation, making nested data easier to read.