Starting from RFC 8259 and ECMA-404, this category lays out JSON's grammar, types, encoding, and parsing boundaries — the foundation every piece of JSON work rests on.
6 articlesTranslating the grammar productions of RFC 8259 into plain language: which characters may appear directly, which must be escaped, and where the specification deliberately leaves room.
JSON has only six types, but each of them can silently reshape your data. This article covers the pitfalls of numbers, strings, and null in one pass.
Turn JSON.parse errors into a line and character, then rule out six causes: trailing commas, single quotes, comments, control characters, BOM and truncation.
From garbled text in Notepad to three ways to open a JSON file, plus how to confirm nothing broke after editing and what to do when a huge file will not open.
Look up the cause by the exact JSON.parse message: 12 frequent errors across Chrome, Firefox and Safari, including HTML error pages, truncation and double parsing.
A 4 MB one-line JSON file reports line 1 column 23611, which tells you nothing. Using locally measured samples, this guide explains why Python, Node and jq report three different numbers, how a character offset takes you straight to the broken byte, and which three traps silently corrupt data after the syntax is fixed.
