About JSON Files
JSON Data
JSON (JavaScript Object Notation) is a lightweight data interchange format that is human-readable and easy for machines to parse and generate. It has become the dominant format for web APIs, configuration files, and structured data exchange.
Family
Documents & Text
Extension
.json
MIME Type
application/json
Can Use As
HOW JSON
CAME TO BE.
JSON — JavaScript Object Notation — was popularized by Douglas Crockford around 2001-2002 as a lightweight alternative to XML for browser-server data exchange. The syntax was lifted directly from the way JavaScript already defined object literals, which made parsing trivially cheap in the browser: eval(jsonString) worked (before anyone realized that was a security nightmare).
JSON went from a hack to a standard remarkably fast: ECMA-404 in 2013, RFC 8259 in 2017, and by then nearly every new REST API used it instead of XML. Crockford\u2019s famous line was "I don\u2019t want to maintain JSON" — he refused to version the format, arguing simplicity was its main virtue. Today JSON carries config files, API payloads, logs, database documents, build manifests, and an ever-growing chunk of the data plumbing of the internet.
CURIOSITIES &
TRIVIA.
JSON is a subset of JavaScript, but not a strict one — some valid JSON (like leading zeros) is invalid JS, and vice versa.
Douglas Crockford intentionally refused to version the format: "JSON is done. It does not need a v2."
JSON does not permit trailing commas or comments — which is why JSONC (JSON with Comments) and JSON5 were invented.
The largest public JSON file is OpenStreetMap's planet dump — over 100 GB minified.
JSON's only allowed whitespace outside strings is tab, space, newline, and carriage return — nothing else.
STRENGTHS &
LIMITATIONS.
Strengths
- Dead-simple — you can memorize the entire grammar on one page.
- Native parsers in every programming language.
- Human-readable and easy to debug.
- Compact — much smaller than equivalent XML.
- Frozen spec — a JSON parser written in 2010 still handles new JSON files from 2026.
Limitations
- No comments allowed — config files feel verbose.
- No trailing commas — a constant source of parse errors.
- No native date, decimal, or binary types — everything is strings or numbers.
- Easily bloated by repeated keys; large payloads compress poorly vs binary alternatives.
- Streaming is awkward — JSON wants to be parsed whole.
Typical Sizes & Weights
Small config
< 1 KB
REST API payload
1-100 KB
Database export
10 MB - 100 GB
Technical Specifications
- MIME type
- application/json
- Extension
- .json
- Standard
- ECMA-404, RFC 8259
- Encoding
- UTF-8, UTF-16, or UTF-32
- Allowed types
- object, array, string, number, boolean, null
CONVERT FROM
JSON
Common Use Cases
Web APIs, configuration files, data exchange, NoSQL databases
Related Formats
Popular comparisons
JSON vs PDF
Differences, file size, and when to choose each format.
JSON vs DOCX
Differences, file size, and when to choose each format.
JSON vs ODT
Differences, file size, and when to choose each format.
JSON vs TXT
Differences, file size, and when to choose each format.
JSON vs MD
Differences, file size, and when to choose each format.
JSON vs HTML
Differences, file size, and when to choose each format.
Popular JSON conversions
The most-requested destinations when starting from JSON.
Frequently Asked Questions about JSON
Frequently Asked Questions
JSON (JavaScript Object Notation) is a lightweight text format for data exchange, popularized by Douglas Crockford around 2001. JSON represents nested objects, arrays, strings, numbers, booleans, and null values in a syntax derived from JavaScript. It is the default data format for modern web APIs.
JSON files are plain text — open them in any text editor (Notepad, VS Code, Sublime Text, TextEdit). For formatted reading, use JSON-aware editors (VS Code auto-indents) or online viewers like jsonformatter.org. Every web browser displays JSON directly if you open the file locally.
Use KaijuConverter's JSON-to-CSV converter for nested data flattened into a tabular format. For simple flat JSON (array of objects), command-line tools like jq + csvkit give more control. Python's pandas and JavaScript's PapaParse also handle the conversion in one line of code.
JSON for machine-to-machine data exchange (APIs, config) — strict spec, fast parsers in every language. YAML for human-edited config files — supports comments, multi-line strings, and references. Kubernetes, Docker Compose, and GitHub Actions use YAML; REST APIs overwhelmingly use JSON.
JSON's strict specification disallows comments to keep parsers simple and unambiguous. Workarounds include JSONC (JSON with Comments, used by VS Code config), JSON5 (relaxed syntax with comments), or a convention of adding a "comment" or "_doc" field in your data.
JSON itself cannot execute code like JavaScript eval() can, making it safer than older exchange formats. However, deeply nested JSON can exhaust memory (a "billion laughs" variant) — use streaming parsers and limit recursion depth when processing untrusted input.