🔧 TL3 Tools

By Todd L. · Published 2026-07-15 · 7 min read

Understanding JSON: A Beginner's Guide

If you have ever copied data from a website, used an API, or worked with any modern web application, you have likely encountered JSON without realizing it. JSON (JavaScript Object Notation) is the most widely used data format on the internet, powering everything from mobile app communications to configuration files and databases.

Despite its name suggesting a connection to JavaScript, JSON is a language-independent format that can be read and written by virtually any programming language. Understanding JSON helps you work with data more effectively, troubleshoot web applications, and communicate with developers. If you want to see how JSON and CSV represent the same data, our free CSV to JSON converter shows both formats side by side.

What Is JSON?

JSON is a lightweight text format for storing and transmitting structured data. Think of it as a universal language for data exchange. When your weather app fetches the current temperature, when a form submits your information to a server, or when a website loads product details — JSON is likely the format being used behind the scenes.

The format was invented by Douglas Crockford in the early 2000s and was standardized in 2013 as RFC 7159. It replaced XML (eXtensible Markup Language) as the preferred format for web APIs because it is simpler to read, easier to write, and produces smaller file sizes.

JSON Structure: Objects and Arrays

JSON has just two primary structures:

Objects are collections of key-value pairs, enclosed in curly braces {}. Each key is a string followed by a colon, and the value can be a string, number, boolean, null, another object, or an array. Think of an object as a dictionary or a form with labeled fields.

Arrays are ordered lists of values, enclosed in square brackets []. Each value is separated by a comma. Think of an array as a numbered list — the order matters and you can reference items by position.

Data Types in JSON

JSON supports six data types:

A Real-World Example

Here is a JSON representation of a user profile:

{
  "name": "Todd L.",
  "email": "todd@example.com",
  "age": 28,
  "active": true,
  "address": {
    "city": "Vancouver",
    "country": "Canada"
  },
  "hobbies": ["reading", "hiking", "photography"]
}

Notice how the address is a nested object and hobbies is an array. This nesting capability allows JSON to represent complex, hierarchical data structures in a readable format.

Common JSON Mistakes

Why JSON Validation Matters

Invalid JSON can cause applications to crash, data to be lost, and API calls to fail. Common scenarios where JSON validation is critical include:

Our JSON Validator instantly checks your JSON for syntax errors and pinpoints the exact location of problems. Paste your JSON and click validate — it highlights errors with line and column numbers so you can fix them quickly.

JSON vs. Other Formats

Reading a Nested Document: A Product Catalog

Real JSON rarely stays as flat as the profile above. A storefront API, for instance, returns a catalog where each product carries its own nested details. Here is a compact version of what such a response looks like:

{
  "store": "Northwind Outfitters",
  "currency": "CAD",
  "products": [
    {
      "sku": "TENT-204",
      "name": "Two-Person Backpacking Tent",
      "price": 189.99,
      "inStock": true,
      "dimensions": { "length": 48, "width": 16, "height": 7 },
      "tags": ["camping", "backpacking", "waterproof"]
    },
    {
      "sku": "STOVE-118",
      "name": "Titanium Camp Stove",
      "price": 74.5,
      "inStock": false,
      "dimensions": { "length": 4, "width": 3, "height": 3 },
      "tags": ["cooking", "ultralight"]
    }
  ]
}

Start reading from the outside in. The top level is an object with three keys: store, currency, and products. The first two hold plain strings. The third holds an array, and each element of that array is itself an object. Inside a product object, dimensions is another object and tags is an array of strings. To reach the price of the second product, you follow the path products[1].price, which evaluates to 74.5. Every level of nesting is just another object or array, so the same reading rules apply at any depth.

Escaping Special Characters in Strings

Double quotes mark the start and end of every string, so a quote that belongs inside the text needs a backslash in front of it. The same rule applies to the backslash itself. A product description that reads He said "it works" must be written as He said \"it works\" inside the JSON. A Windows file path such as C:\Users\Todd becomes C:\\Users\\Todd.

Two more escapes show up often. A newline inside a string is written as \n, and a tab as \t. For characters that do not appear on a standard keyboard, JSON accepts a Unicode escape in the form \uXXXX, where XXXX is a four-digit hexadecimal code. The emoji for a tent, for example, is \u26FA. Most editors and APIs handle these escapes for you, but knowing them helps when you inspect raw data or debug a file that will not parse.

Numbers in JSON: What Is and Isn't Allowed

JSON numbers look familiar, but the grammar is stricter than most people expect. A number may be an integer such as 42, a decimal such as 3.14, or a value in scientific notation such as 6.02e23. Leading zeros are forbidden, so 007 is invalid and must be written as 7. A decimal point needs at least one digit on each side, which means .5 and 5. are both rejected in favor of 0.5 and 5.0.

Two things that are not numbers in JSON are worth remembering. The special values NaN and Infinity are not part of the format, so a parser will reject them even though JavaScript accepts them. Negative numbers are fine, as in -12.5, but the minus sign must come directly before the digits with no space. If you export data from a spreadsheet, check for these values before you save it as JSON, because they are a common source of parse failures.

How JSON Moves in a Request and Response

Most of the JSON you encounter travels over HTTP as the body of a request or a response. When a browser submits a form, it often sends the field values as a JSON object. The server reads that object, does its work, and replies with another JSON object. The two sides agree on the shape of the data ahead of time, which is why an API description usually lists the expected keys and types.

A typical exchange looks like this. The client sends {"username": "todd", "quantity": 2} to place an order. The server responds with {"orderId": 8841, "status": "confirmed", "total": 149.98}. Notice that the response adds fields the client never sent, such as the order number and the computed total. That asymmetry is normal. The client and server each treat the other's JSON as data, not as a template to copy.

Debugging Invalid JSON with the TL3 Validator

When a parser rejects your JSON, the error message often points at the wrong spot, because the parser only realizes something is wrong after it has already passed the real problem. A missing comma between two keys, for example, makes the parser treat the second key as part of the first value, and the reported error lands several lines later. That is why a validator that shows the exact line and column is worth using.

The TL3 JSON Validator is built for this exact workflow. Paste your JSON into the box, run the check, and read the first reported error. Fix that one problem, then validate again. Parsers stop at the first error, so later mistakes stay hidden until the earlier ones are gone. Working through a file one error at a time is faster than trying to fix everything at once, and it catches the cascade of errors that a single missing brace can cause.

Key Takeaways

JSON is the backbone of modern web communication. Developers, data analysts, and anyone working with digital tools all get more from their work when they understand JSON. Remember: use double quotes, watch your commas, and validate your JSON before using it.

Related Tools

JSON Validator · JSON Formatter · Base64 Encoder/Decoder