JSON Guide: Syntax, Examples, Validation & Best Practices

Learn JSON from the syntax and basic data types through nested structures, parsing, validation, APIs, JSON Schema, formatting, common errors, and practical development workflows.

Format JSON Online Validate JSON

What is JSON?

JSON, short for JavaScript Object Notation, is a text-based data format commonly used to represent structured data and exchange it between applications. JSON supports objects, arrays, strings, numbers, booleans, and null. Its syntax is deliberately small, which makes it easy for software to parse and generate while remaining readable to people.

json

{
  "name": "Ramesh",
  "age": 30,
  "active": true,
  "skills": [
    "Python",
    "JavaScript"
  ]
}

JSON Guide: Learn JSON Syntax and Work With Real Data

JSON shows up almost everywhere in modern software development: API responses, request bodies, configuration files, database exports, application state, logs, webhooks, and data exchange between services. You don't need a large language specification to start using it, but understanding the small set of rules behind JSON prevents many common errors. This guide builds those rules from the ground up and then connects them to practical development tasks such as parsing, formatting, validation, API debugging, and JSON Schema.

What Is JSON?

JSON stands for JavaScript Object Notation. Despite its name, JSON is a language-independent data format rather than JavaScript code. It represents structured data using a small collection of values and syntax rules. Applications can serialize data into JSON text, send that text across a network, store it in a file, and parse it back into an in-memory representation.

Why Is JSON Used So Widely?

JSON is compact, straightforward to generate, and supported by standard libraries in most programming languages. Its object and array structures map naturally to common application data models. Web APIs frequently use JSON for request and response bodies, while configuration and data files often use it because developers can inspect the contents without specialized binary tools.

Basic JSON Syntax

A JSON document can contain an object, an array, or a JSON value. Objects use curly braces and contain name-value pairs. Arrays use square brackets and contain ordered values. Object property names must be strings enclosed in double quotes. Values can be strings, numbers, objects, arrays, true, false, or null.

A simple JSON objectjson

{
  "name": "Ramesh",
  "age": 30,
  "active": true
}

JSON Data Types

JSON has six fundamental value categories: object, array, string, number, boolean, and null. There is no separate JSON type for dates, undefined values, functions, BigInt, or comments. Applications commonly represent those concepts using strings, numbers, booleans, null, or a surrounding object structure.

type	example	purpose
Object	`{"name":"Ramesh"}`	Key-value data
Array	`["Python","JavaScript"]`	Ordered collection
String	`"Hello"`	Text
Number	`42`	Numeric value
Boolean	`true`	True or false state
Null	`null`	Explicit absence of a value

JSON Objects

A JSON object is an unordered collection of name-value pairs enclosed in curly braces. Each property name is a double-quoted string followed by a colon and its value. Properties are separated by commas.

JSON objectjson

{
  "id": 101,
  "name": "Ramesh",
  "role": "developer"
}

JSON Arrays

A JSON array is an ordered collection enclosed in square brackets. Array elements can be strings, numbers, booleans, null, objects, or other arrays. Arrays are common in API responses when an endpoint returns a list of records.

JSON arrayjson

[
  "Python",
  "FastAPI",
  "PostgreSQL"
]

Nested JSON

Objects and arrays can be placed inside other objects and arrays. This nesting is what allows JSON to represent data with multiple levels, such as a user containing an address and a list of permissions.

Nested JSON examplejson

{
  "user": {
    "id": 42,
    "profile": {
      "name": "Ramesh",
      "location": "Nepal"
    },
    "roles": [
      "developer",
      "admin"
    ]
  }
}

JSON Strings

JSON strings use double quotation marks. Characters that have special meaning inside JSON strings must be escaped when necessary, including quotation marks and backslashes. Common escape sequences include \" for a quotation mark, \\ for a backslash, \n for a newline, and \t for a tab.

JSON Numbers

JSON supports numbers without separate integer and floating-point syntax categories. A number can include a negative sign, a fractional part, and an exponent. JSON does not define NaN or Infinity as valid JSON numbers. Applications also need to consider the numeric precision supported by the programming language that parses the JSON.

JSON Booleans and Null

Boolean values are written as true or false without quotation marks. The null value is written as null. These are JSON values, not strings, so "true" and "null" have different meanings from true and null.

JSON Property Names

JSON object property names must be strings and therefore use double quotes. This differs from JavaScript object literal syntax, where some property names can be written without quotes. The distinction matters when code that looks like a JavaScript object is passed to a strict JSON parser.

JSON Syntax Rules You Need to Remember

Most JSON syntax errors come from a small set of rules. Use double quotes for strings and property names, separate object properties and array elements with commas, use colons between property names and values, and close every object and array. JSON does not permit comments or trailing commas in standard JSON.

Object keys use double quotes.
String values use double quotes.
A colon separates each object key from its value.
Commas separate properties or array elements.
Objects use { and }.
Arrays use [ and ].
Boolean literals are true and false.
The null literal is null.
Standard JSON does not allow comments.
Standard JSON does not allow trailing commas.

A Complete JSON Example

A realistic document often combines several JSON features at once. The following example contains strings, numbers, booleans, null, an object, an array, and nested structures.

Real-world JSON structurejson

{
  "id": 1001,
  "name": "Ramesh Das",
  "email": "ramesh@example.com",
  "active": true,
  "profile": {
    "role": "developer",
    "experience": 6
  },
  "skills": [
    "Python",
    "FastAPI",
    "JavaScript"
  ],
  "metadata": null
}

JSON vs JavaScript Objects

JSON and JavaScript object literals look similar, but they are not interchangeable. JSON is a text format with stricter syntax. JavaScript objects are runtime values and can contain functions, undefined, symbols, and other JavaScript-specific values. A JavaScript object can be converted to JSON text with JSON.stringify(), while JSON text can be parsed with JSON.parse().

/guides/json-vs-javascript-object

JSON Parsing

Parsing converts JSON text into a data structure that a program can work with. If the text violates JSON syntax, a parser normally raises an error rather than returning the intended object. Parsing is therefore a useful first step when checking whether a string contains syntactically valid JSON.

Parse JSON in JavaScriptjavascript

const data = JSON.parse(jsonText);
console.log(data.name);

Parse JSON in Pythonpython

import json

data = json.loads(json_text)
print(data["name"])

JSON Serialization

Serialization converts an in-memory data structure into JSON text. In JavaScript, JSON.stringify() performs this conversion. In Python, json.dumps() serializes a Python value to a JSON string. Serialization is commonly used before sending a request body or writing structured data to a text file.

Serialize a JavaScript objectjavascript

const user = {
  name: "Ramesh",
  active: true
};

const json = JSON.stringify(user);

Serialize data in Pythonpython

import json

data = {
    "name": "Ramesh",
    "active": True
}

json_text = json.dumps(data)

How JSON Is Used in APIs

HTTP APIs commonly use JSON for request and response bodies. A client can send JSON describing an operation or resource, while the server can return JSON containing the result. The Content-Type header is commonly used to indicate that a body contains JSON, typically with application/json. API documentation should also define the expected fields, types, and semantics because valid JSON alone does not describe an application's complete contract.

JSON Request Bodies

A JSON request body carries structured data from a client to a server. Before sending it, the client should serialize the data correctly and use the content type expected by the endpoint. The server may then perform syntax, schema, authentication, authorization, and business-rule validation.

Send JSON with fetchjavascript

fetch("/api/users", {
  method: "POST",
  headers: {
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    name: "Ramesh",
    active: true
  })
});

JSON API Responses

API responses can contain a single object, an array, or a more structured response envelope. When debugging a response, inspect the HTTP status, response headers, raw body, JSON syntax, expected fields, and application-level semantics. Formatting the response makes nested data easier to inspect but does not determine whether the API returned the correct business result.

JSON Validation

JSON validation can mean two different things. Syntax validation asks whether the document is valid JSON. Structural validation asks whether valid JSON satisfies a defined contract, often through JSON Schema or application-specific rules. Keeping these checks separate makes API debugging much easier.

JSON Schema

JSON Schema provides a way to describe the expected structure and constraints of JSON data. A schema can specify required properties, data types, allowed values, array rules, string constraints, numeric limits, and nested object structures. This is useful for API contracts, configuration validation, testing, and documentation.

Formatting JSON

Formatting, also called pretty printing or beautifying, adds indentation and line breaks so people can inspect JSON more easily. Formatting should preserve the underlying data. It is useful when debugging API responses, reviewing configuration files, reading logs, or preparing examples for documentation.

Pretty print JSONjavascript

const formatted = JSON.stringify(JSON.parse(jsonText), null, 2);

Pretty print JSON in Pythonpython

import json

formatted = json.dumps(json.loads(json_text), indent=2)

JSON Minification

Minification removes unnecessary whitespace from JSON to produce a compact textual representation. It does not normally remove properties or values. Minified JSON is useful when compact output is preferred, while formatted JSON is easier for people to inspect.

JSON Files

A .json file stores JSON text. Common uses include application configuration, test fixtures, exported data, package metadata, and static datasets. The file must follow the syntax expected by the software reading it. An editor can format a JSON file to make it easier to maintain.

JSON Configuration Files

JSON is frequently used for configuration, but developers should check whether the specific tool expects strict JSON or a JSON-based variant. Some configuration formats add comments or other syntax that strict JSON parsers do not accept. A file extension alone does not determine the exact grammar.

JSON and Webhooks

Webhooks often deliver JSON event payloads through HTTP requests. The payload can contain an event type, identifiers, metadata, and nested resource data. During debugging, formatting the payload helps reveal its structure. When webhook signatures are calculated from the exact raw request body, preserve the original bytes for verification rather than replacing them with a formatted version.

/guides/format-webhook-json

JSON and Database Data

Applications may serialize database records or query results as JSON for APIs, exports, or inter-service communication. The database representation and JSON representation are not necessarily identical. Fields may be renamed, omitted, converted, or nested during serialization according to the application's API model.

Common JSON Errors

Most beginner and production JSON errors are syntax mistakes or mismatches between the JSON and an expected data contract. Missing commas, incorrect quotes, unmatched brackets, invalid escape sequences, trailing commas, and unquoted property names are common syntax problems.

Using single quotes

Invalid:{'name': 'Ramesh'}

Valid:{"name": "Ramesh"}

Trailing comma

Invalid:{"name": "Ramesh",}

Valid:{"name": "Ramesh"}

Unquoted key

Invalid:{name: "Ramesh"}

Valid:{"name": "Ramesh"}

Missing comma

Invalid:{"name": "Ramesh" "active": true}

Valid:{"name": "Ramesh", "active": true}

Valid JSON Can Still Be Wrong

Passing a JSON parser does not mean the data is acceptable to an application. For example, an API might require an email field, expect age to be a number, or permit only specific status values. A document can be syntactically valid while violating those application rules. Schema validation and business validation address this layer.

JSON Security Considerations

JSON itself is a data format, not a security boundary. Applications should treat external JSON as untrusted input and apply appropriate validation, authorization, size limits, and business rules. Developers should also avoid exposing credentials, access tokens, personal data, or internal secrets in logs and public JSON examples.

Handling Large JSON Documents

Large JSON documents can consume substantial memory during parsing because many common JSON libraries build an in-memory representation. For very large datasets, applications may need pagination, streaming approaches, chunked processing, or a different data-exchange strategy. Pretty printing also adds whitespace, so it is not usually desirable as the only representation for very large production payloads.

JSON Formatting vs Minification

Formatting and minification change presentation rather than the underlying JSON data. Formatting adds whitespace for readability; minification removes unnecessary whitespace for compactness. Minification is not the same as gzip or Brotli compression, and formatting is not the same as validation.

/guides/json-formatting-vs-minification

JSON vs XML

JSON and XML can both represent structured data, but they use different syntax and conventions. JSON maps naturally to objects and arrays and is widely used in web APIs. XML provides a richer markup model with elements, attributes, namespaces, and established document-oriented tooling. The appropriate format depends on the requirements of the system and its ecosystem.

JSON vs YAML

JSON and YAML can both represent structured data, but YAML has a broader and more flexible syntax that is often used for human-maintained configuration. JSON has a smaller grammar and stricter syntax. Some YAML parsers can read JSON because JSON is compatible with a subset of YAML syntax, but the two formats should not be treated as identical.

JSON Best Practices

Good JSON design is less about making every document look identical and more about keeping the data predictable and unambiguous.

Use descriptive and consistent property names.
Keep data types stable across API responses.
Use arrays for ordered collections.
Use objects when named properties describe a record.
Avoid unnecessary nesting.
Document required and optional fields.
Use JSON Schema when a formal structure needs to be shared.
Validate external JSON before relying on it.
Keep human-maintained JSON consistently formatted.
Avoid placing secrets in JSON logs or examples.
Use pagination for large API collections.
Distinguish null from a missing property when the application semantics require it.
Do not treat syntactic validity as proof that business data is correct.

How to Debug JSON Step by Step

When JSON causes a problem, start with syntax rather than immediately changing application code. Determine whether the source is a file, API response, request body, webhook, or generated string. Then parse or validate it, format the valid document for inspection, compare it with the expected structure, and finally check application-specific rules.

Capture the original JSON.
Determine where the JSON came from.
Check whether it is syntactically valid.
Read the parser error if parsing fails.
Format valid JSON for easier inspection.
Compare its structure with the expected contract.
Validate against JSON Schema when available.
Check application and business rules.
Inspect the producer if the payload itself is incorrect.
Retest using the smallest reproducible example.

JSON Tools and When to Use Them

Different JSON tasks call for different tools. A formatter is useful for readability, a validator for syntax or structure checks, a minifier for compact output, and a schema validator for contract-level checks. Choosing the tool based on the actual problem prevents formatting from being used as a substitute for debugging or validation.

Format or pretty print

Go to resource

Minify JSON

Go to resource

Fix malformed JSON

Go to resource

Understand parser errors

Go to resource

Validate JSON

Go to resource

Understand JSON Schema

Go to resource

Format an API response

Go to resource

Format a webhook payload

Go to resource

JSON Guide: Where to Go Next

Once the basic syntax is familiar, the most useful next step depends on what you are trying to do. If you are working with raw JSON, formatting and validation are good starting points. If an API is returning unexpected data, move into API debugging. If your application needs a defined contract, JSON Schema is the natural next topic.

JSON Formatting Examples

Parse JSON in JavaScript

javascript

const data = JSON.parse('{"name":"Ramesh","active":true}');
console.log(data.name);

Format JSON in JavaScript

javascript

const formatted = JSON.stringify(JSON.parse(jsonText), null, 2);
console.log(formatted);

Minify JSON in JavaScript

javascript

const minified = JSON.stringify(JSON.parse(jsonText));
console.log(minified);

Parse JSON in Python

python

import json

data = json.loads(json_text)
print(data["name"])

Format JSON in Python

python

import json

formatted = json.dumps(json.loads(json_text), indent=2)
print(formatted)

Validate JSON with jq

bash

jq empty input.json

Format JSON with jq

bash

jq . input.json

JSON Fundamentals Checklist

Know the six JSON value categories.
Use double quotes for JSON strings and object keys.
Use commas between object properties and array elements.
Use a colon between an object key and its value.
Close every object and array.
Do not use comments in standard JSON.
Do not use trailing commas in standard JSON.
Remember that JSON is data, not executable JavaScript.
Parse JSON before using it as application data.
Validate structure separately from basic JSON syntax when needed.
Use JSON Schema for explicit data contracts.
Format JSON when readability matters.
Minify JSON when compact textual output is useful.
Treat external JSON as untrusted input.
Avoid exposing secrets and sensitive data in JSON logs.
Use pagination or streaming strategies for very large datasets.

Frequently Asked Questions

Q:What is JSON?

JSON is a text-based format for representing and exchanging structured data. It supports objects, arrays, strings, numbers, booleans, and null.

Q:What does JSON stand for?

JSON stands for JavaScript Object Notation.

Q:Is JSON a programming language?

No. JSON is a data format. Its syntax was derived from JavaScript object notation, but JSON itself is used independently of JavaScript.

Q:What are the JSON data types?

JSON supports objects, arrays, strings, numbers, booleans, and null.

Q:Does JSON use single or double quotes?

Standard JSON uses double quotes for strings and object property names. Single-quoted strings are not valid standard JSON.

Q:Can JSON contain comments?

Standard JSON does not support comments. Some JSON-based configuration formats add comment support, but those are extensions rather than standard JSON.

Q:Can JSON contain trailing commas?

No. Standard JSON does not allow a trailing comma after the last property or array element.

Q:What is the difference between JSON and a JavaScript object?

JSON is text with a defined syntax, while a JavaScript object is an in-memory runtime value. JSON.parse() converts JSON text into JavaScript data, and JSON.stringify() converts JavaScript data into JSON text.

Q:How do I format JSON?

Use a JSON formatter or parse and serialize the data with indentation. In JavaScript, JSON.stringify(JSON.parse(json), null, 2) is a common approach.

Q:How do I validate JSON?

Parse the JSON with a JSON parser to check syntax. Use JSON Schema or application-level validation when you also need to verify structure, data types, required fields, or business rules.

Q:What causes JSON parsing errors?

Common causes include missing commas, unmatched brackets, invalid quotes, unquoted property names, invalid escape sequences, trailing commas, and other syntax violations.

Q:Can valid JSON still fail an API request?

Yes. An API can reject syntactically valid JSON because required fields are missing, values have the wrong types, an allowed value is invalid, authentication is missing, or a business rule is violated.

Q:What is JSON Schema?

JSON Schema is a vocabulary for describing the expected structure and constraints of JSON data. It can define properties, types, required fields, array rules, and other constraints.

Q:What is JSON parsing?

JSON parsing converts JSON text into an in-memory data structure that a program can access and manipulate.

Q:What is JSON serialization?

JSON serialization converts an in-memory data structure into JSON text, commonly before sending it through an API or saving it to a file.

Q:Is JSON case-sensitive?

JSON syntax distinguishes uppercase and lowercase literal names such as true, false, and null. Property names are strings, so application code can also treat differently cased property names as different keys.

Q:Can JSON contain Unicode characters?

Yes. JSON text can represent Unicode characters. JSON also provides escape syntax for representing characters when an escaped representation is preferred.

Q:Can JSON represent dates?

JSON has no dedicated date type. Applications commonly represent dates as strings, often using an agreed format such as an ISO-style timestamp.

Q:Can JSON represent undefined?

No. undefined is a JavaScript value, not a JSON value. Applications generally omit such properties or represent the absence of a value with null when appropriate.

Q:Is JSON the same as YAML?

No. JSON and YAML are different data formats with different syntax and features, although JSON syntax is compatible with a subset of YAML.

Explore More Resources

JSON Formatter

JSON Minifier

JSON Syntax

JSON Pretty Print

JSON vs JavaScript Object

Read more about JSON vs JavaScript Object

How to Validate JSON

JSON Validation

JSON Schema

Fix Invalid JSON

JSON Parsing Errors

Debug JSON API Response

Format JSON API Response

Read more about Format JSON API Response

Format REST API Response

Read more about Format REST API Response

Format JSON Payload

Format Webhook JSON

Format JSON File

Format JSON in Browser

JSON Formatting vs Minification

Read more about JSON Formatting vs Minification

JSON Guide

Learn JSON from the syntax and basic data types through nested structures, parsing, validation, APIs, JSON Schema, formatting, common errors, and practical development workflows.

Format JSON Online Validate JSON

What is JSON?

json

{
  "name": "Ramesh",
  "age": 30,
  "active": true,
  "skills": [
    "Python",
    "JavaScript"
  ]
}

JSON Guide: Learn JSON Syntax and Work With Real Data

What Is JSON?

Why Is JSON Used So Widely?

Basic JSON Syntax

A simple JSON objectjson

{
  "name": "Ramesh",
  "age": 30,
  "active": true
}

JSON Data Types

type	example	purpose
Object	`{"name":"Ramesh"}`	Key-value data
Array	`["Python","JavaScript"]`	Ordered collection
String	`"Hello"`	Text
Number	`42`	Numeric value
Boolean	`true`	True or false state
Null	`null`	Explicit absence of a value

JSON Objects

JSON objectjson

{
  "id": 101,
  "name": "Ramesh",
  "role": "developer"
}

JSON Arrays

JSON arrayjson

[
  "Python",
  "FastAPI",
  "PostgreSQL"
]

Nested JSON

Nested JSON examplejson

{
  "user": {
    "id": 42,
    "profile": {
      "name": "Ramesh",
      "location": "Nepal"
    },
    "roles": [
      "developer",
      "admin"
    ]
  }
}

JSON Strings

JSON Numbers

JSON Booleans and Null

JSON Property Names

JSON Syntax Rules You Need to Remember

Object keys use double quotes.
String values use double quotes.
A colon separates each object key from its value.
Commas separate properties or array elements.
Objects use { and }.
Arrays use [ and ].
Boolean literals are true and false.
The null literal is null.
Standard JSON does not allow comments.
Standard JSON does not allow trailing commas.

A Complete JSON Example

A realistic document often combines several JSON features at once. The following example contains strings, numbers, booleans, null, an object, an array, and nested structures.

Real-world JSON structurejson

{
  "id": 1001,
  "name": "Ramesh Das",
  "email": "ramesh@example.com",
  "active": true,
  "profile": {
    "role": "developer",
    "experience": 6
  },
  "skills": [
    "Python",
    "FastAPI",
    "JavaScript"
  ],
  "metadata": null
}

JSON vs JavaScript Objects

/guides/json-vs-javascript-object

JSON Parsing

Parse JSON in JavaScriptjavascript

const data = JSON.parse(jsonText);
console.log(data.name);

Parse JSON in Pythonpython

import json

data = json.loads(json_text)
print(data["name"])

JSON Serialization

Serialize a JavaScript objectjavascript

const user = {
  name: "Ramesh",
  active: true
};

const json = JSON.stringify(user);

Serialize data in Pythonpython

import json

data = {
    "name": "Ramesh",
    "active": True
}

json_text = json.dumps(data)

How JSON Is Used in APIs

JSON Request Bodies

Send JSON with fetchjavascript

fetch("/api/users", {
  method: "POST",
  headers: {
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    name: "Ramesh",
    active: true
  })
});

JSON API Responses

JSON Validation

JSON Schema

Formatting JSON

Pretty print JSONjavascript

const formatted = JSON.stringify(JSON.parse(jsonText), null, 2);

Pretty print JSON in Pythonpython

import json

formatted = json.dumps(json.loads(json_text), indent=2)

JSON Minification

JSON Files

JSON Configuration Files

JSON and Webhooks

/guides/format-webhook-json

JSON and Database Data

Common JSON Errors

Using single quotes

Invalid:{'name': 'Ramesh'}

Valid:{"name": "Ramesh"}

Trailing comma

Invalid:{"name": "Ramesh",}

Valid:{"name": "Ramesh"}

Unquoted key

Invalid:{name: "Ramesh"}

Valid:{"name": "Ramesh"}

Missing comma

Invalid:{"name": "Ramesh" "active": true}

Valid:{"name": "Ramesh", "active": true}

Valid JSON Can Still Be Wrong

JSON Security Considerations

Handling Large JSON Documents

JSON Formatting vs Minification

/guides/json-formatting-vs-minification

JSON vs XML

JSON vs YAML

JSON Best Practices

Good JSON design is less about making every document look identical and more about keeping the data predictable and unambiguous.

Use descriptive and consistent property names.
Keep data types stable across API responses.
Use arrays for ordered collections.
Use objects when named properties describe a record.
Avoid unnecessary nesting.
Document required and optional fields.
Use JSON Schema when a formal structure needs to be shared.
Validate external JSON before relying on it.
Keep human-maintained JSON consistently formatted.
Avoid placing secrets in JSON logs or examples.
Use pagination for large API collections.
Distinguish null from a missing property when the application semantics require it.
Do not treat syntactic validity as proof that business data is correct.

How to Debug JSON Step by Step

Capture the original JSON.
Determine where the JSON came from.
Check whether it is syntactically valid.
Read the parser error if parsing fails.
Format valid JSON for easier inspection.
Compare its structure with the expected contract.
Validate against JSON Schema when available.
Check application and business rules.
Inspect the producer if the payload itself is incorrect.
Retest using the smallest reproducible example.

JSON Tools and When to Use Them

Format or pretty print

Go to resource

Minify JSON

Go to resource

Fix malformed JSON

Go to resource

Understand parser errors

Go to resource

Validate JSON

Go to resource

Understand JSON Schema

Go to resource

Format an API response

Go to resource

Format a webhook payload

Go to resource

JSON Guide: Where to Go Next

JSON Formatting Examples

Parse JSON in JavaScript

javascript

const data = JSON.parse('{"name":"Ramesh","active":true}');
console.log(data.name);

Format JSON in JavaScript

javascript

const formatted = JSON.stringify(JSON.parse(jsonText), null, 2);
console.log(formatted);

Minify JSON in JavaScript

javascript

const minified = JSON.stringify(JSON.parse(jsonText));
console.log(minified);

Parse JSON in Python

python

import json

data = json.loads(json_text)
print(data["name"])

Format JSON in Python

python

import json

formatted = json.dumps(json.loads(json_text), indent=2)
print(formatted)

Validate JSON with jq

bash

jq empty input.json

Format JSON with jq

bash

jq . input.json

JSON Fundamentals Checklist

Know the six JSON value categories.
Use double quotes for JSON strings and object keys.
Use commas between object properties and array elements.
Use a colon between an object key and its value.
Close every object and array.
Do not use comments in standard JSON.
Do not use trailing commas in standard JSON.
Remember that JSON is data, not executable JavaScript.
Parse JSON before using it as application data.
Validate structure separately from basic JSON syntax when needed.
Use JSON Schema for explicit data contracts.
Format JSON when readability matters.
Minify JSON when compact textual output is useful.
Treat external JSON as untrusted input.
Avoid exposing secrets and sensitive data in JSON logs.
Use pagination or streaming strategies for very large datasets.

Frequently Asked Questions

Q:What is JSON?

JSON is a text-based format for representing and exchanging structured data. It supports objects, arrays, strings, numbers, booleans, and null.

Q:What does JSON stand for?

JSON stands for JavaScript Object Notation.

Q:Is JSON a programming language?

No. JSON is a data format. Its syntax was derived from JavaScript object notation, but JSON itself is used independently of JavaScript.

Q:What are the JSON data types?

JSON supports objects, arrays, strings, numbers, booleans, and null.

Q:Does JSON use single or double quotes?

Standard JSON uses double quotes for strings and object property names. Single-quoted strings are not valid standard JSON.

Q:Can JSON contain comments?

Standard JSON does not support comments. Some JSON-based configuration formats add comment support, but those are extensions rather than standard JSON.

Q:Can JSON contain trailing commas?

No. Standard JSON does not allow a trailing comma after the last property or array element.

Q:What is the difference between JSON and a JavaScript object?

Q:How do I format JSON?

Use a JSON formatter or parse and serialize the data with indentation. In JavaScript, JSON.stringify(JSON.parse(json), null, 2) is a common approach.

Q:How do I validate JSON?

Parse the JSON with a JSON parser to check syntax. Use JSON Schema or application-level validation when you also need to verify structure, data types, required fields, or business rules.

Q:What causes JSON parsing errors?

Common causes include missing commas, unmatched brackets, invalid quotes, unquoted property names, invalid escape sequences, trailing commas, and other syntax violations.

Q:Can valid JSON still fail an API request?

Q:What is JSON Schema?

JSON Schema is a vocabulary for describing the expected structure and constraints of JSON data. It can define properties, types, required fields, array rules, and other constraints.

Q:What is JSON parsing?

JSON parsing converts JSON text into an in-memory data structure that a program can access and manipulate.

Q:What is JSON serialization?

JSON serialization converts an in-memory data structure into JSON text, commonly before sending it through an API or saving it to a file.

Q:Is JSON case-sensitive?

Q:Can JSON contain Unicode characters?

Yes. JSON text can represent Unicode characters. JSON also provides escape syntax for representing characters when an escaped representation is preferred.

Q:Can JSON represent dates?

JSON has no dedicated date type. Applications commonly represent dates as strings, often using an agreed format such as an ISO-style timestamp.

Q:Can JSON represent undefined?

No. undefined is a JavaScript value, not a JSON value. Applications generally omit such properties or represent the absence of a value with null when appropriate.

Q:Is JSON the same as YAML?

No. JSON and YAML are different data formats with different syntax and features, although JSON syntax is compatible with a subset of YAML.