Explainers · 7 min read · 2026-09-08
Almost every app you use - every food delivery tracker, every weather widget, every chat client - spends its day sending and receiving JSON. Short for JavaScript Object Notation, JSON is a text format for describing structured data: objects with named fields, lists of items, and simple values like strings, numbers, booleans and null. It was standardised in the early 2000s precisely because it is simple enough for humans to read and strict enough for machines to parse unambiguously.
A JSON document is either an object in curly braces or an array in square brackets. Object keys are always double-quoted strings followed by a colon. Values can be strings, numbers, true, false, null, nested objects or arrays. That is the entire language - no comments, no single quotes, no trailing commas. Those three omissions cause the overwhelming majority of real-world JSON errors.
APIs usually send JSON minified - no indentation, no line breaks - because it saves bytes. That is efficient for machines and miserable for humans. A formatter re-indents the structure so nesting becomes visible at a glance; a validator tells you not just that something is wrong but pinpoints the exact character position of the error. When a 3,000-character webhook payload rejects your request, that error location is the difference between a 30-second fix and an afternoon.
Validation is also how you catch invisible damage: a stray BOM character from a Windows editor, a non-breaking space pasted from a chat app, or a numeric field that quietly became a string. Running payloads through a strict validator before filing a bug report is one of the cheapest debugging habits you can build.
JSON is not alone. YAML is its indentation-sensitive cousin, common in CI pipelines and Kubernetes configs. CSV is its flat, spreadsheet-friendly counterpart. XML is its verbose, namespace-heavy ancestor. All four describe the same kind of data, and converting between them is a routine task - YAML for humans to edit, JSON for machines to exchange, CSV for analysts to pivot. Zoven has dedicated converters for each direction, all running locally in the browser.
If you can read {"hello": ["w", "o", "r", "l", "d"]}, you already know JSON. Everything else is punctuation discipline.