JSON Formatter & Minifier

How to use the JSON Formatter

1. Paste your JSON into the left textbox. Formatting begins automatically after you stop typing for 300ms.
2. Choose your indent: 2 spaces (default), 4 spaces, tab, or minified (single line).
3. Read the result in the right textbox. On parse errors, the status line shows exact line and column.
4. Click Copy to copy the output, or use Ctrl/⌘ + Shift + C.

What makes a JSON document "valid"?

Per RFC 8259, a valid JSON document is exactly one of: an object, an array, a string, a number, true, false, or null. Trailing commas are not allowed. Comments are not allowed. Strings must be double-quoted, single quotes are invalid JSON even if JavaScript accepts them.

Common JSON errors and what they mean

"Unexpected token" errors

Almost always one of these four:

• Trailing comma: {"a":1,} is invalid. Remove the final comma.
• Single quotes: {'a':1} is invalid. Convert to double quotes.
• Unquoted keys: {a:1} is invalid. Wrap keys in double quotes: {"a":1}.
• JavaScript values: undefined, NaN, and Infinity are not valid JSON. Use null.

"Unexpected end of JSON input"

Usually a missing closing brace, bracket, or quote. Look for unbalanced {}, [], or "".

"Bad control character in string literal"

Raw newlines, tabs, or other control characters in strings must be escaped: use \\n for newline, \\t for tab.

Privacy and performance

Parsing happens entirely in your browser via the built-in JSON.parse. No data is transmitted to any server. The browser's native parser processes hundreds of kilobytes of JSON in single-digit milliseconds, much faster than any "online formatter" that round-trips to a server. You can inspect the JavaScript running this tool via your browser's DevTools.

JSON minifier: when minified output is the right choice

The minified option (0-indent / single-line) in this tool strips all whitespace not required by the JSON spec. That is exactly what the JSON minifier does. Use it in these situations:

• Production API responses: minified JSON is typically 15-30% smaller than 2-space-indented output. On a high-traffic endpoint that returns 5 KB of JSON, minification shaves 1-1.5 KB per response, which compounds into meaningful bandwidth savings at scale.
• localStorage / sessionStorage: browser storage has a 5 MB quota per origin. Minifying JSON before writing reduces the chance of hitting that limit.
• Environment variables and CI secrets: some CI systems have length limits on secret values. A minified JSON config often fits where a formatted one doesn't.
• Log payloads: one JSON object per log line is the standard for structured logging. Minified keeps each line a single line.

Use the formatter (2-space or 4-space indent) during development and debugging, and the minifier for anything that goes to production or a byte-limited channel.

JSON formatter vs JSON linter: not the same thing

These terms are often used interchangeably but describe different operations:

• JSON formatter: takes valid JSON and rewrites it with consistent indentation and whitespace. It does not change the data; it only changes the presentation. If the input is already valid, formatting always succeeds.
• JSON linter: checks for structural correctness: balanced braces, valid string escapes, no trailing commas, no comments, no JavaScript-specific values like undefined or NaN. A linter catches errors; a formatter cannot fix them.

This tool does both. If the JSON is valid, it formats it. If the JSON is invalid, it shows a linter-style error message with exact line and column. You get a formatter and a validator in one step.

JSON in APIs: best practices

• Always set Content-Type: application/json: clients use this header to decide how to parse the response. Omitting it causes framework-level bugs in some HTTP clients.
• Consistent key naming: pick camelCase or snake_case and stick to it across the entire API. Mixing both in the same response is a common source of client bugs.
• null vs omitting a key: these have different semantics. {"middle_name": null} means the field exists but has no value. {} (key absent) means the client should make no assumption. Be deliberate, inconsistency here breaks client-side null checks.
• Dates as ISO 8601 strings: JSON has no native date type. Represent dates and datetimes as strings in ISO 8601 format ("2026-05-13T00:00:00Z"). Never use Unix timestamps as bare integers if humans will read the API, they're impossible to debug at a glance.
• Avoid deeply nested structures: more than 3-4 levels of nesting is a sign the data model needs to be reconsidered. Deep nesting makes client-side destructuring verbose and error-prone.

JSON types reference

Related articles

• 4 min readJSON Minification: Remove Whitespace and Reduce Payload SizeMinifying JSON removes all whitespace and produces compact payloads for API responses and storage. Learn how to minify JSON in JavaScript, Python, and at the server level with...
• 4 min readJSON Parse Errors: SyntaxError, Common Causes, and Safe ParsingJSON.parse throws SyntaxError for any malformed input. Learn the most common JSON parse errors, how to debug them, safe parsing with try/catch, and handling partial/streaming...
• 4 min readJSON.stringify Options: replacer, space, and Circular Reference HandlingJSON.stringify accepts three arguments: value, replacer, and space. Learn how to use the replacer function to filter keys, the space parameter for pretty-printing, handle...
• 6 min readJSON to C# Classes: Generate .NET Model Classes InstantlyPaste JSON and get C# classes with properties, data annotations, and Newtonsoft or System.Text.Json attributes. Copy straight into your .NET project.
• 6 min readJSON to Go Struct: Generate Golang Types from a JSON SamplePaste JSON and get Go struct definitions with json tags. Handles nested structs, arrays, and null fields. Copy directly into your Go project and start unmarshalling.
• 6 min readJSON to TypeScript Interface: Auto-Generate Types from Any JSONPaste JSON and get TypeScript interfaces instantly. Auto-generates nested types, optional fields, and union types. No manual typing, copy and paste into your project.
• 4 min readJSON5 Format: Comments, Trailing Commas, and Extended JSON SyntaxJSON5 extends JSON with JavaScript-style comments, trailing commas, unquoted keys, single-quoted strings, and hexadecimal numbers. Learn when to use JSON5 for config files and...
• 6 min readJSON Formatting Explained: Why Pretty-Printing MattersA JSON formatter takes compact, hard-to-read JSON and adds whitespace and indentation for readability. Here's what formatters do, why they're indispensable for API debugging,...
• 6 min readJSON Schema Validation: Validate JSON Structure and TypesJSON Schema defines the structure and types your JSON must conform to. Here's how to write JSON Schema definitions, validate JSON in JavaScript and Python, and handle common...
• 11 min readThe 10 Most Common JSON Validation Errors (and How to Fix Them)Every JSON parse error in production traces back to one of ten root causes. This is the field guide, what each error means, why it happened, and the exact fix.
• 9 min readWhat Is JSON and Why You Should Always Format ItJSON is the universal data format of the modern web. This is what it actually is, why formatting matters even for machines, and how to keep your sanity when JSON breaks.

Pillar

Written and maintained by Mian Ali Khalid. Last updated 2026-05-13.