The History of JSON

From a "hack" to pass objects in browser frames to the universal standard for data exchange. Discover how 6 simple characters { } [ ] : , changed the web.

1999

The Origin

It wasn't 'invented' but discovered. They needed a way to pass data to a browser frame without reloading the page. They realized JavaScript object literals could be used as a data format. It was originally called 'JSML' but that name was taken.

Historical Snippet / Context
doSomething({ "key": "value" })

Why JSON Won

XML The Old King

<user id="1">
  <name>John</name>
  <email>[email protected]</email>
</user>
  • Verbose (End tags duplicate data)
  • Ambiguous (Attribute vs Child Node?)
  • Complex parsing in Browser

JSON The Winner

{
  "id": 1,
  "name": "John",
  "email": "[email protected]"
}
  • Concise & Readable
  • Maps directly to Objects/HashMaps
  • Native JavaScript parsing

Where JSON Lives Today

Web APIs

The default response format for REST and GraphQL APIs.

Databases

MongoDB, CouchDB, and even Postgres (JSONB) store data as JSON.

Configuration

VS Code settings, package.json, tsconfig.json, cloud configs.

Logging

Structured logging (Datadog, ELK stack) relies on JSON streams.