The History of JSON: From 2000 to Industry Standard

Douglas Crockford and the origin

In the early 2000s, Douglas Crockford — a veteran JavaScript developer — was frustrated with XML, the dominant data format of the era. XML was verbose, hard to parse in browsers, and overkill for simple server-to-client data transfer.

Working at State Software, Crockford realized that JavaScript's object-literal syntax was already a near-perfect data format: compact, human-readable, and natively understood by every browser. He named it JSON — JavaScript Object Notation — and registered json.org in 2002 to publish the specification.

The Web 2.0 adoption wave

JSON's big break came with the Web 2.0 movement (2005–2006). As AJAX-powered apps needed lightweight server responses, developers reached for JSON instead of XML. Yahoo was an early adopter, shipping JSON in several of its web services.

For a time, JSON was parsed with eval() — fast but dangerous, since it could execute arbitrary code. The introduction of a native, safe JSON.parse() in ECMAScript 3.1 (which became ES5, 2009) removed that risk and cemented JSON in the platform.

Becoming a standard

JSON was formalized as the ECMA-404 standard in 2013, and published as RFC 7159 by the IETF in 2014 (later revised as RFC 8259 in 2017). These moves established JSON as a language-independent format — not a JavaScript feature, but a universal standard.

From there, adoption was total. REST APIs defaulted to JSON. NoSQL databases like MongoDB stored documents as JSON (BSON). Configuration files, JWT authentication tokens, and cloud-native tooling all standardized on JSON or its superset, YAML.

Why JSON beat XML

JSON is roughly 30–40% smaller than equivalent XML (no closing tags, no attributes), maps directly to native data structures in every language, and parses far faster. XML retains niches — document markup, SOAP, config with schemas — but JSON dominates data interchange.