JSON Formatter & Validator (Minify, Beautify, Fix JSON)

How this page is maintained

• Steps and copy are checked against the current tool behavior.
• Browser limits, file-size constraints, or compatibility gaps are documented when relevant.
• Unless a page explicitly says otherwise, files and text stay in the browser during processing.

How to Format, Validate, and Minify JSON in the Browser

Paste a JSON document into the input panel and choose Format, Minify, or Validate. Formatting adds two-space indentation so nested objects and arrays line up; minifying removes every space and newline; validating tells you whether the text parses at all.

A Worked Example

Start with this single line, the shape most API logs and network tabs give you:

{"user":{"id":42,"tags":["admin","beta"]},"active":true}

After Format:

{
"user": {
"id": 42,
"tags": [
"admin",
"beta"
]
},
"active": true
}

After Minify you get the original 68-character line back, with no whitespace left to carry.

Why a Trailing Comma Breaks It

The validator follows the strict JSON standard (RFC 8259). JavaScript object literals tolerate a comma before a closing brace; JSON does not. Given a line like {"a":1,}, the parser stops at the final comma and reports its line number, so you can delete that one character and format again. The same applies to unquoted keys, single-quoted strings, and comments.

What Minify Actually Saves

On small objects the saving looks trivial. On configuration files with hundreds of repeated keys it is the entire indentation overhead, which is why minified payloads ship smaller over the wire.

Every step runs in your browser: the JSON text is not uploaded to JW Tool Box. The site separately collects usage information as described in the Privacy Policy, and you should still avoid pasting secrets on a shared or monitored machine.

Where to Go Next

Compare JSON against the alternatives in JSON vs XML vs YAML, convert legacy documents with the XML to JSON converter, or turn spreadsheets into objects using the CSV to JSON converter.

What Format, Minify, and Validate Actually Do to Your JSON

Formatting and minifying are the same parse step with two different outputs. Both call the browser's own JSON.parse first, so a document that does not parse produces no output at all and instead shows an error message like Invalid JSON with a short reason such as Unexpected token }. When the parse succeeds, Format runs JSON.stringify with an indent of two spaces, which adds newlines and two spaces per nesting level. Minify runs the same stringify with an indent of zero, which removes every space, tab, and newline that was not inside a string.

A concrete example you can check by hand: paste {"user":{"id":42,"tags":["admin","beta"]},"active":true} into the input panel. That line is 56 characters. Click Format JSON and the counter under the output panel reads 99 characters spread over 10 lines, because every brace and bracket now sits on its own line. Click Minify and the counter reads 56 again, character for character identical to what you pasted.

The Exact Clicks

Paste or type your JSON in the input panel on the left. Click Format JSON. Read the character count under the output panel and click Copy above it to take the result. For a production payload, click Minify instead and copy the single line. Click Load sample at any time to restore the built-in demo document, or Clear to empty both panels. The Layout buttons on the right switch between Split, which shows input and output side by side, and Full-width, which puts the input above the output. Full-width is easier when your JSON lines are long, because the narrower split columns force horizontal scrolling.

Format or Minify: Which One

Choose Format when a human has to read or diff the document: config files in a repository, API responses you are debugging, fixtures in a test suite. Choose Minify when only a machine reads it: a request body, an embedded config string, a payload you are about to paste into a URL or an environment variable. The saving is unglamorous but real. The built-in sample document is 142 characters as loaded and 118 characters after Minify, so 40 characters disappear, about a quarter of the formatted 158-character version.

Common Mistakes

Pasting already-minified JSON and clicking Minify, then wondering why nothing shrank. There is no whitespace left to remove, so the output length equals the input length. Pasting JavaScript object literals that only look like JSON. A trailing comma before a closing brace, single-quoted strings, unquoted keys, and comment lines are all legal in JavaScript and all rejected here, because the parser enforces the strict RFC 8259 grammar. Typing credentials or API keys into the panel on a shared or screen-shared machine, then leaving the tab open; parsing happens in your browser, but the text still sits in that tab.

Where to Go Next

For an array of records rather than a single document, run it through the CSV to JSON converter instead. If your source data is not JSON at all, the XML to JSON converter and the comparison in JSON vs XML vs YAML cover the other two formats you are most likely to receive.

Key features

• Instant Beautiful Output: Turn unreadable one-line JSON strings into perfectly indented, color-coded structures. Easier to read than your raw console logs.
• Minify for Production: Strip unnecessary whitespace and newlines to create the smallest possible valid JSON string for API payloads or config files.
• Syntax Error Highlighting: Don't guess where the error is. We point out the exact location of syntax issues (like a trailing comma) so you can fix them fast.

Frequently asked questions

Related guides

• JSON vs. YAML vs. XML: The Ultimate Comparison for Developers (2026)

  Every developer faces the choice: How should I structure my configuration files? How should my API send data? In 2026, the "Big Three" data serialization formats—JSON, YAML, and XML—still dominate the landscape. But they are not interchangeable. Each has a specific superpower (and a specific kryptonite). Here is the definitive breakdown to help you choose the right tool for the job. 1. JSON (J…

• Convert CSV to JSON (and Back) Free Online — No Excel Needed (2026)

  Switching between CSV spreadsheets and JSON API payloads is one of those daily developer tasks that sounds simple but constantly bites you: mismatched delimiters, quoted fields with commas, encoding issues. This guide covers how to convert CSV to JSON (and back) instantly in your browser—no Excel, no Python script, no uploads. ⚡ Quick Start → CSV to JSON Converter — paste your data, convert, c…