What Is JSON? A Plain-English Guide (With Common Errors)

You've probably seen JSON in a lot of places — wiring up an API, editing a config file, or just over a developer's shoulder — without quite knowing what it is. The good news is that JSON isn't hard, and being able to read it is genuinely useful for anyone who works with data, not just programmers. Here's the plain-English version.

What is JSON?

JSON stands for JavaScript Object Notation, and in everyday terms it's just a format for recording data — a way to describe information that humans can read and machines can parse.

It looks like this:

{
  "name": "Alex",
  "age": 25,
  "isStudent": false,
  "skills": ["design", "photography"],
  "contact": {
    "email": "[email protected]",
    "phone": "0912-345-678"
  }
}

You can read it at a glance: this is a person named Alex, 25, not a student, who does design and photography. That readability is JSON's whole appeal — clear structure, easy to scan.

The basic rules

There are only a few building blocks to remember:

Symbol	Meaning	Example
{ }	Object (a set of key/value pairs)	{"name": "Alex"}
[ ]	Array (a list)	["a", "b", "c"]
"key": value	A key/value pair	"age": 25
:	Separates key and value	—
,	Separates each item	—

Values can be: text (must use double quotes), numbers, true/false, null, or another object/array (that's "nesting").

Where is JSON used?

• Web and app APIs: open an app, it asks a server for data, and what comes back is usually JSON.
• Config files: many tools store settings as JSON (for example a front-end project's package.json).
• Front-end/back-end data exchange: it's the common language web front-ends and back-ends use to pass data.

In short, most of the data moving around the modern web travels as JSON.

The three mistakes that trip everyone up

JSON is strict — one missing symbol breaks the whole thing. The most common errors:

1. Trailing commas. The last item can't have a comma after it.

// ❌ wrong
{ "a": 1, "b": 2, }
// ✅ right
{ "a": 1, "b": 2 }

2. Wrong quotes. Strings and keys must use double quotes ", never single quotes.

// ❌ wrong
{ 'name': 'Alex' }
// ✅ right
{ "name": "Alex" }

3. Unbalanced brackets. Every { } and [ ] must be paired.

These are genuinely hard to catch by eye — especially in a long file.

How to format and validate JSON

The two things you'll need most:

• It's squashed and unreadable → use "beautify" to add indentation and line breaks
• You want to check it for errors → use "validate" to flag exactly which line is wrong

The fastest way is our JSON formatter / validator — paste your JSON and beautify, minify, or check the syntax in one click. It runs entirely in your browser, so your data is never uploaded, which makes it safe for debugging real work.

Squashed: {"name":"Alex","skills":["design","photography"]}

Beautified:
{
  "name": "Alex",
  "skills": ["design", "photography"]
}

The bottom line

JSON is simply a data format that both people and machines can read — {} holds key/value pairs, [] holds lists, and web APIs, config files and data exchange almost all rely on it. When you write it, watch the three traps: no trailing commas, use double quotes, and keep brackets balanced. When you hit JSON that's squashed or possibly broken, drop it into a JSON formatter and you'll instantly see it cleanly — and find out exactly where it's wrong. Want to understand another format you'll meet constantly? See what Base64 is.