Blog / How the internet works /
JSON explained for non-developers
If you run a website for long enough, someone will send you a block of text full of curly brackets and quotation marks and say “just paste this in”. That block is probably JSON.
JSON stands for JavaScript Object Notation, which is an unhelpful name. Here is a better one: it’s a labelled list. Every value comes with a label saying what it is.
What it looks like
{
"name": "Ada",
"plan": "premium",
"active": true,
"sites": 3
}
Read it left to right. There’s a label ("name"), a colon, then the value ("Ada"). Pairs are separated by commas, and the whole thing sits inside curly brackets.
That’s most of it. If you can read a form (“Name: Ada, Plan: premium”), you can read JSON.
The analogy
Think of a form that a computer fills in for another computer. A human doesn’t need labels because we know what a phone number looks like. A program does. JSON is the form with every box labelled, in a style any programming language can read.
That’s why it took over. It’s light, readable by people, and nearly every tool understands it.
The building blocks
JSON has only a few building blocks:
| Type | Example | Notes |
|---|---|---|
| Text (string) | "hello" |
Always in double quotes |
| Number | 42 or 3.5 |
No quotes |
| True or false | true, false |
Lower case, no quotes |
| Nothing | null |
Means “no value” |
| List (array) | ["a", "b", "c"] |
Square brackets |
| Object | { "key": "value" } |
Curly brackets, can nest |
Lists and objects can sit inside each other, which is how JSON describes complicated things:
{
"store": "Demo shop",
"products": [
{ "title": "Mug", "inStock": true },
{ "title": "Poster", "inStock": false }
]
}
Here products is a list, and each item in it is an object. Once you see that pattern, even long files stop looking scary.
Where you meet JSON on a website
You don’t need to be a developer to run into it.
- Structured data. Those schema markup snippets that help search engines understand a page use a flavour called JSON-LD. If you’ve pasted a
<script type="application/ld+json">block, you’ve handled JSON. I have a starting guide to schema markup on WordPress if that’s new. - APIs. When one service asks another for data, the answer typically comes back as JSON. I explained APIs for website owners a few weeks ago.
- Settings and exports. Many tools let you export your configuration or your data as a JSON file.
- The WordPress REST API. Add
/wp-json/to a WordPress site’s address and you will see JSON describing the site’s endpoints. - Browser developer tools. The Network tab shows JSON responses as pages load.
How to read a messy one
Raw JSON from a machine often arrives as one long line. It’s technically valid and impossible to read. Paste it into a “JSON formatter” or “JSON viewer” and it will indent it nicely. Many code editors and browsers do this too. Be careful which online tool you use: don’t paste anything private into a website you don’t trust. API keys and customer data should never go into random formatters.
The mistakes that break it
JSON is strict. Computers don’t guess what you meant. The same handful of slips cause most of the errors.
- A trailing comma. A comma after the last item makes the whole file invalid.
- Single quotes. JSON requires double quotes around labels and text.
- Missing quotes on labels.
name: "Ada"is wrong;"name": "Ada"is right. - A missing bracket. Every
{needs a}and every[needs a]. - Comments. JSON doesn’t allow them. Anything with
//in it will break. - Curly “smart” quotes. If you copy JSON through a word processor or some chat apps, straight quotes can turn into curly ones, and then nothing works.
If a validator says there’s an error “at line 7”, look at line 6 as well. The mistake is often one line earlier than where the tool noticed.
JSON and AI tools
If you use ChatGPT or Claude to help with data work, you’ll hear about asking for output “as JSON”. It’s a way to get a predictable answer you can feed into a spreadsheet, script or automation. I went into this in JSON mode and schemas explained for builders. One caution from experience across tools: AI will sometimes return JSON with a stray explanation sentence around it, or an extra comma. Run it through a validator before you trust it.
JSON versus a spreadsheet
People ask whether JSON is “just a spreadsheet”. Close, but not quite. A spreadsheet is flat: rows and columns. JSON can nest, which suits data where an order contains items, and each item has options. That’s why shops, apps and APIs prefer it. For a simple contact list, a spreadsheet or CSV is easier for humans.
Should you learn it?
You don’t have to write it by hand every day. But a basic reading knowledge saves you from being stuck when a plugin wants a settings file, a webhook shows an error, or an integration refuses your pasted data. An hour of poking at examples is enough.
Key takeaways
- JSON is data with labels:
"label": value. - Strings use double quotes; lists use square brackets; objects use curly brackets.
- You meet it in schema markup, APIs, exports and WordPress.
- Most errors are a stray comma, wrong quotes or a missing bracket.
- Never paste private data into a random online formatter.
FAQ
Is JSON a programming language? No. It’s a format for describing data.
Is JSON the same as JavaScript? It borrows the look of JavaScript objects but is used by almost every language.
Why not just use plain text? Because a program needs to know which part is the name and which is the price. Labels make that unambiguous.
Related reading
- APIs explained for website owners
- Wildcard DNS explained
- DNS records explained: A, AAAA, CNAME, MX and TXT
Next time you see a block of curly brackets, try reading it aloud as a list of labels and values. Does it start to make sense?