JSON Format Guide

About JSON Format

JSON (JavaScript Object Notation) is a lightweight data interchange format created by Douglas Crockford in 2001. It is standardized as RFC 8259 and ECMA-404. Despite being derived from JavaScript, JSON is language-independent and supported natively by virtually every modern programming language, making it the de facto standard for data exchange on the web.

JSON uses a simple, strict syntax with curly braces for objects, square brackets for arrays, and quoted strings for keys. It supports six data types: strings, numbers, booleans, null, objects, and arrays. Its simplicity and universality have made it the dominant format for REST APIs, configuration files (package.json, tsconfig.json), NoSQL databases (MongoDB, CouchDB), and browser localStorage.

Available Conversions

JSON Features

• Universal Standard: RFC 8259 / ECMA-404, supported by every programming language
• Data Types: Strings, numbers, booleans, null, objects, and arrays
• Strict Syntax: Unambiguous parsing with no room for interpretation
• Native Browser Support: JSON.parse() and JSON.stringify() built into JavaScript
• Compact Format: Efficient data representation with minimal overhead
• UTF-8 Encoding: Mandatory UTF-8 support for international text
• Schema Validation: JSON Schema for structure validation
• YAML Subset: Valid JSON is also valid YAML 1.2
• Database Support: Native JSON types in PostgreSQL, MySQL, MongoDB
• API Standard: Dominant format for REST and GraphQL APIs

Common Uses

• Web APIs: REST, GraphQL responses and request bodies
• Package Managers: package.json (npm), composer.json (PHP), Pipfile.lock (Python)
• Configuration: tsconfig.json, .eslintrc.json, settings.json
• NoSQL Databases: MongoDB, CouchDB, DynamoDB document storage
• Browser Storage: localStorage and sessionStorage
• Data Exchange: Cross-platform, cross-language data transfer
• Serverless: AWS Lambda events, Azure Functions triggers
• Logging: Structured logging (JSON Lines format)