JSON stands for JavaScript Object Notation. Despite the JavaScript in the name, it has nothing to do with writing code. JSON is simply a way of writing down information in a format that computers can read and humans can understand. If you know what a shopping list looks like, you are already 80% of the way there.
Think of JSON as a box with labels. You have a label called "name" and next to it you write "Alice". Another label called "age" with "30". A third label called "email" with "alice@example.com". JSON groups these together in a clean, predictable structure that any programming language can parse in milliseconds. Here is what that looks like:
This four-line block is JSON. It represents a person with four properties. The curly braces { } mean "this is an object" — a collection of related information. Inside, each line is a key-value pair: the key ("name") identifies what kind of information this is, and the value ("Alice") is the actual data. JSON supports six types of values: strings (text in double quotes), numbers (no quotes), booleans (true or false), null, arrays (lists in square brackets), and objects (nested curly braces).
Where do you encounter JSON in real life? Every time you open a weather app and it shows you tomorrow's forecast, that data arrived from a server as JSON. When you log into a website, the server responds with your user profile as JSON. If you use Spotify, your playlists are stored as JSON. Your phone's settings backup is probably JSON. It is the default language that web services use to talk to each other, which means if you work anywhere near the internet — as a developer, a designer, a marketer who reads API docs, or just someone who wants to understand how the apps they use actually work — reading JSON is a genuinely useful skill.
JSON's entire rulebook fits on a napkin. There are only a handful of rules, and they never change. Master these and you can read any JSON document in existence.
Rule 1: Everything starts and ends with either curly braces { } for an object, or square brackets [ ] for an array (a list). Objects contain key-value pairs. Arrays contain comma-separated values.
Rule 2: Keys must be wrapped in double quotes. "name" is valid. 'name' (single quotes) and name (no quotes) are not.
Rule 3: String values must also use double quotes. Numbers, booleans, and null do not need quotes. Commas separate items, but you cannot have a trailing comma after the last item.
Rule 4: Whitespace (spaces, tabs, line breaks) between elements is ignored. This means you can write JSON as a dense single line or spread it across multiple lines with indentation — both represent the exact same data.
Rule 5: JSON has no comment syntax. You cannot write // this is a comment inside JSON. This surprises beginners because many programming languages allow it, but JSON's design intentionally excludes comments to keep the format purely about data.
Almost every JSON error falls into one of these five categories. Once you recognize the patterns, you will spot them instantly. If you are ever unsure whether a JSON snippet is valid, paste it into a free JSON validator and it will highlight the exact line where the problem is.
A comma after the last item in an object or array is illegal in JSON. It is allowed in JavaScript and Python, which is why it trips people up.
JSON requires double quotes for both keys and strings. This is the number one issue when people copy from JavaScript or Python code.
In JavaScript you can write { name: "Alice" } and it works. In JSON, the key must be quoted: { "name": "Alice" }.
Comments are not part of the JSON specification. If you need them, use JSON5 or YAML instead.
Every key-value pair except the last needs a comma after it. Forgetting one is easy to do and the error message is rarely helpful.
The easiest way to avoid all of these is to let a tool check your work. Paste your JSON into our free JSON formatter and it will tell you within seconds whether it is valid and exactly where any errors are.
Before JSON became the standard, the web ran on XML — a markup format that looks a lot like HTML. Here is the same data (Alice's profile) in both formats:
JSON uses roughly half as many characters to represent the same data. It is simpler, faster to parse, and maps directly to the data structures that every programming language uses (objects and arrays). XML's advantages are in document-centric use cases: it supports comments, has a mature schema validation system, and can represent mixed content (text with inline markup). For a web API that needs to send data from a server to a browser or mobile app, JSON won decisively. There is a reason every major API in the last 15 years — from Stripe to GitHub to Google Maps — uses JSON.
When JSON is valid, it just works. When it is invalid, it fails completely. Unlike HTML — which browsers render optimistically even when the markup is broken — JSON parsers are strict. A single misplaced comma, one unquoted key, one missing bracket, and the entire file is rejected. This strictness is actually a feature: it means that when you do receive valid JSON, you can trust that the data is intact and correctly structured.
The two operations you will do most often with JSON are formatting and validation. Formatting (also called pretty-printing) takes a compressed, single-line JSON blob and spreads it across multiple lines with proper indentation so a human can read it. This is invaluable when you are debugging an API response or inspecting a configuration file. Validation checks whether the JSON follows the syntax rules and points to the exact line and column where any problem occurs.
Both are one click away with our JSON formatter. It uses syntax highlighting to color-code strings, numbers, and keys, making the structure visible at a glance. If there is an error, it tells you the line number so you can fix it immediately. The tool runs entirely in your browser — your data is never sent to any server — which matters if you are working with API responses that contain tokens, user data, or internal configuration.
Paste any JSON, click Format, and see it beautifully indented with syntax highlighting. Errors are shown with exact line numbers. Free, no signup, all processing in your browser.
Open JSON Formatter