JSON

/ˈdʒeɪ.sɒn/ · Abbreviation · Development · Origin: 2001

Definitions

  1. JSON, or JavaScript Object Notation, is a lightweight, text-based data interchange format that uses human-readable key-value pairs and ordered lists to represent structured data. Despite its name, JSON is language-independent and supported by virtually every modern programming language and framework. Its simplicity and readability made it the dominant format for web API communication, replacing the more verbose XML in most use cases. A JSON document consists of objects (curly braces containing key-value pairs), arrays (square brackets containing ordered values), strings, numbers, booleans, and null. JSON is used for API request and response bodies, configuration files, data storage in NoSQL databases like MongoDB, log messages, and inter-service communication. Parsing and generating JSON is fast and native to JavaScript environments, which contributed to its rapid adoption alongside the rise of Node.js and single-page applications. Extensions like JSON Schema provide validation, and formats like JSONL (newline-delimited JSON) support streaming use cases.

    In plain English: A way to format data that's easy for both humans and computers to read — the standard language that web applications use to exchange information.

Etymology

2001
Douglas Crockford begins promoting a lightweight data interchange format based on JavaScript object literal syntax.
2006
RFC 4627 formalizes JSON. It rapidly displaces XML in web APIs due to its simplicity and readability.
2013
ECMA-404 standardizes JSON independently. JSON becomes the lingua franca of web services.
2020s
JSON is used nearly everywhere: APIs, configuration files, databases (JSONB in PostgreSQL). JSON5 and JSONC add minor extensions.

Origin Story

Discovered, not invented

Douglas Crockford was working at State Software in the early 2000s when he needed a lightweight data format for browser-server communication. XML was too verbose. He realized that JavaScript's object literal syntax was already a perfectly good data format — it just needed a name and a spec.

Crockford registered json.org in 2002 and wrote a one-page specification. He deliberately kept it minimal: no comments, no trailing commas, no extensibility. He famously said, 'I discovered JSON. I do not claim to have invented it, because it already existed in nature.'

The simplicity was its superpower. JSON spread from web APIs to configuration files to databases. Today it is arguably the most widely used data interchange format on the planet, and Crockford's insistence on keeping the spec frozen has been vindicated — there has never been a JSON 2.0.

Coined by: Douglas Crockford

Context: State Software, 2001-2002

Fun fact: Crockford trademarked the phrase 'JSON' but placed the specification in the public domain. The official JSON license has a quirky clause: 'The Software shall be used for Good, not Evil.'

Related Terms