Format Guide

Complete Guide to JSON Format: Structure, Syntax, and Examples

December 23, 2025 12 min read Format Guide

JSON (JavaScript Object Notation) is a lightweight, text-based data interchange format that has become the de facto standard for web APIs and configuration files. This comprehensive guide will take you from JSON basics to advanced nested structures, helping you understand when and how to use JSON effectively.

What is JSON?
JSON Syntax Basics
JSON Data Types
JSON Objects
JSON Arrays
Nested JSON Structures
JSON Variations (JSON5, JSONL)
JSON Best Practices
Converting JSON to CSV

What is JSON?

JSON is a human-readable data format derived from JavaScript syntax, but it's language-independent and supported by virtually all modern programming languages. Originally specified by Douglas Crockford in 2001, JSON has become the primary format for:

REST API responses and requests - Web services exchange data in JSON format
Configuration files - Application settings and deployment configs
NoSQL databases - MongoDB, Couchbase, and others store documents as JSON
Log files - Structured logging in JSON Lines format
Data interchange - Between systems and applications

JSON Syntax Basics

JSON has a simple, minimal syntax with just a few rules to remember:

Data is represented as key-value pairs
Keys must be strings enclosed in double quotes
Values can be strings, numbers, objects, arrays, boolean, or null
Objects are enclosed in curly braces {}
Arrays are enclosed in square brackets []
Commas separate key-value pairs and array elements
No trailing commas are allowed (in strict JSON)
Whitespace (spaces, tabs, newlines) is allowed for formatting

{
  "name": "John Doe",
  "age": 30,
  "city": "New York"
}

JSON Data Types

JSON supports six fundamental data types:

Type	Description	Example
String	Text in double quotes	`"Hello World"`
Number	Integer or floating-point	`42`, `3.14`
Boolean	true or false	`true`, `false`
Null	Empty/absent value	`null`
Object	Key-value pairs in {}	`{"key": "value"}`
Array	Ordered list in []	`[1, 2, 3]`

JSON Objects

A JSON object is an unordered collection of key-value pairs enclosed in curly braces. Objects are perfect for representing complex entities:

{ "userId": 1001, "username": "johndoe", "email": "[email protected]", "isActive": true, "lastLogin": null }

JSON Arrays

Arrays represent ordered lists of values. Array elements can be of any type, including objects:

{
  "tags": ["javascript", "json", "web-development"],
  "scores": [95, 87, 92, 88],
  "users": [
    {"id": 1, "name": "Alice"},
    {"id": 2, "name": "Bob"}
  ]
}

Nested JSON Structures

One of JSON's most powerful features is the ability to nest objects and arrays within each other, creating complex hierarchical data structures:

{ "user": { "id": 1001, "name": { "first": "John", "last": "Doe" }, "contact": { "email": "[email protected]", "phone": "+1-555-0123" }, "address": { "street": "123 Main St", "city": "New York", "state": "NY", "zipCode": "10001", "country": "USA" } }, "orders": [ { "orderId": "ORD-001", "items": [ {"productId": "P101", "quantity": 2, "price": 29.99}, {"productId": "P102", "quantity": 1, "price": 49.99} ], "total": 109.97, "status": "shipped" } ] }

JSON Variations: JSON5 and JSONL

JSON5

JSON5 is an extension that makes JSON more user-friendly for configuration files:

Comments - Supports // and /* */ comments
Trailing commas - Allows commas after the last element
Unquoted keys - Keys don't need quotes in many cases
Multiline strings - Strings can span multiple lines

// User configuration file { userName: "admin", // Unquoted key email: '[email protected]', roles: ["user", "admin"], // Trailing comma allowed settings: { theme: "dark", notifications: true, } }

JSON Lines (JSONL)

JSON Lines format has one valid JSON object per line, commonly used for log files:

{"timestamp": "2025-12-23T10:00:00Z", "level": "INFO", "message": "Server started"}
{"timestamp": "2025-12-23T10:01:00Z", "level": "INFO", "message": "User login", "userId": 1001}
{"timestamp": "2025-12-23T10:02:00Z", "level": "ERROR", "message": "Connection failed", "error": "timeout"}

JSON Best Practices

Use consistent naming conventions - camelCase for keys is standard
Keep JSON files readable - Use proper indentation and line breaks
Validate JSON before use - Use linters to catch syntax errors
Avoid deeply nested structures - More than 3-4 levels deep becomes hard to process
Use dates in ISO 8601 format - "2025-12-23T10:00:00Z"
Include version numbers in API responses - Helps with backward compatibility

Converting JSON to CSV

When you need to analyze JSON data in spreadsheets or import it into databases, converting to CSV format is essential. Our free JSON to CSV converter automatically:

Flattens nested objects using dot notation (user.address.city)
Handles JSON arrays by creating rows
Supports JSON5 and JSONL formats
Processes data locally in your browser for maximum security

Pro Tip

When converting nested JSON to CSV, the converter creates column headers by joining nested keys with dots. For example, {"user": {"name": "John"}} becomes a column named user.name with value John.

Conclusion

JSON's simplicity and flexibility make it ideal for modern web applications and data exchange. Understanding JSON structure, data types, and best practices will help you work more effectively with APIs, configuration files, and data processing workflows.

Ready to convert your JSON data to CSV? Try our JSON to CSV converter - fast, secure, and completely free.