JSON Formatter

A key-value pair is the fundamental unit of a JSON object. The key is always a string wrapped in double quotes (e.g., "username"), followed by a colon, followed by the value. The value can be one of six types. A String is text enclosed in double quotes: "hello world". A Number is an integer or decimal without quotes: 42 or 3.14. A Boolean is the literal word true or false (lowercase, no quotes) - useful for on/off flags or yes/no states. null represents the intentional absence of a value. An Object is a nested set of key-value pairs inside {}, and an Array is an ordered list inside []. Mixing these types correctly is the foundation of every valid JSON document.

This is one of the most common frustrations for developers coming from JavaScript. In JS, a trailing comma after the last item in an array or object is perfectly valid and often encouraged for cleaner version-control diffs. JSON, however, follows the original specification published by Douglas Crockford, which explicitly prohibits trailing commas. The grammar simply does not allow any token after the final value before the closing bracket. When a parser encounters {"name": "Alex",}, it sees a comma and expects another key-value pair - but it finds } instead, causing a "Unexpected token" error. The fix is straightforward: remove the comma after the last entry. Many code editors with JSON language support will highlight this error automatically.

Beautifying (also called "pretty-printing") takes compact or messy JSON and expands it with consistent indentation and line breaks, making the hierarchy immediately visible. A 500-character minified blob might become 60 legible lines once beautified. Minifying does the opposite - it strips all whitespace, newlines, and indentation that are not part of string values, producing the most compact representation possible. The actual data content is identical either way. Minification is used in production and API responses to reduce file size and speed up transmission: removing whitespace from a large JSON payload can cut its size by 20-40%. Beautification is used during development, debugging, logging, and code review, where human readability is more important than byte count.

The most common issues, in order of frequency, are: 1. Trailing commas - a comma after the last item in an object or array. Remove it. 2. Single-quoted strings - JSON requires double quotes for all strings and keys. Replace 'value' with "value". 3. Unquoted keys - unlike JavaScript object literals, keys in JSON must be quoted. Change {name: "Alex"} to {"name": "Alex"}. 4. Missing commas - forgetting a comma between two key-value pairs or array items. 5. Mismatched brackets - an opened { or [ that is never closed. This formatter pinpoints the line and character of the error to help you find the problem instantly without scanning the entire document manually.

An API (Application Programming Interface) is a defined channel that lets two software systems talk to each other. When you open a weather app, the app sends an API request to a remote server asking for forecast data. The server does the work, then sends back a structured response - almost always in JSON. JSON became the de-facto standard for APIs because it is compact, language-agnostic, and maps naturally onto the data structures (objects and lists) that every programming language understands. Earlier generations of APIs used XML, which is far more verbose and harder to read. REST APIs, GraphQL endpoints, and webhook payloads all rely on JSON today. Pasting an API response into this tool gives you an instant, readable view of exactly what data a service returned, which is an essential step in any integration or debugging session.