What is JSON? Complete Guide with Examples

What is JSON?

JSON (JavaScript Object Notation) is a lightweight, text-based data interchange format that is easy for humans to read and write, and easy for machines to parse and generate. It was created by Douglas Crockford in the early 2000s and has become the dominant format for data exchange on the web, replacing XML in most modern applications.

Despite its name, JSON is language-independent. It is supported natively or through libraries in virtually every programming language including Python, Java, PHP, Ruby, Go, Rust, C#, and of course JavaScript.

JSON Data Types

JSON supports exactly six data types:

JSON Syntax Rules

JSON has strict syntax rules. Violating any of these causes a parse error:

• Keys must be strings wrapped in double quotes (single quotes are not valid)
• Strings must use double quotes — single quotes are not allowed
• No trailing commas after the last item in an object or array
• No comments — JSON does not support // or /* */ comments
• Numbers cannot have leading zeros (e.g., 007 is invalid)
• Special characters in strings must be escaped with backslash: \", \\, \/, \b, \f, \n, \r, \t

JSON Object Example

{
  "user": {
    "id": 1,
    "name": "Jane Doe",
    "email": "jane@example.com",
    "age": 28,
    "isActive": true,
    "address": {
      "street": "123 Main St",
      "city": "New York",
      "country": "US"
    },
    "tags": ["developer", "designer"],
    "lastLogin": null
  }
}

JSON vs XML

JSON has largely replaced XML for web APIs because it is more concise and easier to work with. Here is the same data in both formats:

{
  "name": "Jane",
  "age": 28
}

<user>
  <name>Jane</name>
  <age>28</age>
</user>

JSON is ~30% more compact, natively supported in JavaScript, and easier to parse in most languages. XML still has advantages for document-centric data, namespaces, and schemas.

Common JSON Errors and How to Fix Them

JSON Best Practices

• Use camelCase for key names in JavaScript APIs (e.g., firstName, not first_name)
• Use snake_case for Python and Ruby APIs following their conventions
• Always validate JSON before parsing in production — use try/catch around JSON.parse()
• Use ISO 8601 format for dates: "2024-01-15T10:30:00Z"
• Keep JSON responses flat when possible — deeply nested structures are harder to work with
• Use pagination for large arrays instead of returning thousands of items at once
• Minify JSON in production to reduce payload size, but keep it formatted in development