How to Read and Format JSON (A Beginner's Guide)

If you've ever opened an API response or a config file and seen a dense wall of curly braces and colons, that's JSON — and it's much less intimidating once you know the handful of rules it's built on.

What JSON actually is

JSON (JavaScript Object Notation) is a simple text format for representing structured data — think of it as a universal way to write down "things with properties" that any programming language can read. It's built from just a few basic building blocks:

• Objects — a set of key-value pairs wrapped in curly braces: {"name": "Ayesha", "age": 28}
• Arrays — an ordered list wrapped in square brackets: ["marketing", "design"]
• Strings, numbers, booleans, and null — the actual values, which can be text in quotes, plain numbers, true/false, or null for "nothing here."

How to actually read it

Start from the outermost brackets and work inward. A curly brace {} means you're looking at an object — a set of labeled properties. A square bracket [] means a list of items. Indentation (when the JSON is formatted nicely) shows you which properties belong to which object, the same way indentation works in an outline.

The syntax mistakes that break JSON most often

Trailing commas

Unlike some programming languages, JSON does not allow a comma after the last item in a list or object. ["a", "b",] is invalid — that last comma has to go.

Single quotes instead of double quotes

JSON strings must use double quotes. {'name': 'Ayesha'} looks reasonable but is invalid JSON — it needs to be {"name": "Ayesha"}.

Unquoted keys

In JavaScript itself, you can sometimes get away with {name: "Ayesha"}. In strict JSON, keys always need double quotes too: {"name": "Ayesha"}.

Missing or extra brackets

Every opening { or [ needs a matching closing } or ]. In deeply nested JSON, it's easy to lose track of one — a good formatter will usually point out exactly where the mismatch is.

Why formatting matters more than it seems

Minified JSON (all on one line, no spacing) is efficient for machines but nearly unreadable for people. Formatting it — adding consistent indentation and line breaks — doesn't change the data at all, but turns a wall of text into something you can actually scan and debug.

The bottom line

JSON is just nested key-value pairs and lists, written in a strict but predictable format. Once you can spot the four common syntax mistakes above, most "broken JSON" problems become quick fixes instead of mysteries.