JSON Formatter

Understanding JSON: Syntax, Data Types, Validation, and Best Practices

JSON (JavaScript Object Notation) is a lightweight, text-based data interchange format that has become the universal language of web APIs, configuration files, and data storage. Created by Douglas Crockford in the early 2000s and standardized as ECMA-404 and RFC 8259, JSON's success stems from its simplicity: it uses a small set of syntax rules that map directly to data structures found in virtually every programming language. Over 90% of public web APIs use JSON as their primary response format, and it has largely replaced XML for most modern data interchange tasks.

This free JSON formatter and validator lets you paste raw JSON, instantly check whether it is valid, and see it pretty-printed with proper indentation. All processing happens locally in your browser — your data is never sent to any server, making this tool safe for formatting sensitive API responses, configuration files, or database exports.

JSON Syntax Rules: The Complete Reference

JSON syntax is a strict subset of JavaScript object literal syntax, with several important restrictions that trip up even experienced developers. Understanding these rules will help you avoid the most common validation errors.

Objects are enclosed in curly braces {} and contain zero or more key-value pairs separated by commas. Every key must be a double-quoted string — no single quotes, no unquoted identifiers. Values are separated from keys by a colon. Arrays are enclosed in square brackets [] and contain zero or more values separated by commas. Arrays can hold values of any type, including mixed types within the same array.

JSON Data Types

Notably absent from JSON's type system: Date — dates are represented as ISO 8601 strings like "2026-03-26T12:00:00Z". undefined — does not exist in JSON; use null instead. Comments — JSON provides no comment syntax. If you need comments, consider JSON5 or JSONC (JSON with Comments), used by VS Code configuration files. Functions — not a valid JSON value.

The Most Common JSON Errors (and How to Fix Them)

Trailing commas: JavaScript allows {"a": 1, "b": 2,} but JSON does not. Remove the comma after the last element. This is the single most common JSON validation error.

Single quotes: {'name': 'John'} is valid JavaScript but invalid JSON. All strings and keys must use double quotes: {"name": "John"}.

Unquoted keys: {name: "John"} is valid JavaScript but invalid JSON. Keys must always be double-quoted strings.

Comments: // this is not allowed and /* neither is this */ will cause parsing failures. JSON has no comment syntax by design.

Special number values: NaN, Infinity, and -Infinity are not valid JSON numbers. Use null or a string representation instead.

Unescaped control characters: Literal tabs, newlines, and other control characters inside strings must be escaped as \t, \n, etc.

JSON vs XML: A Detailed Comparison

JSON in the Wild: Where You Encounter JSON Every Day

REST APIs: When your browser or mobile app makes requests to services like Twitter, Stripe, or Google Maps, the response is almost always JSON. API responses contain nested objects, arrays of records, and metadata — all structured in JSON format.

Configuration files: package.json (npm/Node.js), tsconfig.json (TypeScript), .eslintrc.json (ESLint), appsettings.json (.NET), and composer.json (PHP) all use JSON to store project configuration. VS Code settings use JSONC, which extends JSON with comments.

NoSQL databases: MongoDB stores documents as BSON (Binary JSON), and CouchDB uses pure JSON for both storage and queries. Firebase Realtime Database stores its entire data tree as JSON. DynamoDB represents items as JSON-like attribute maps.

JSON-LD and Schema.org: Structured data for search engines (the Schema.org markup that powers Google rich results) is typically embedded in web pages as JSON-LD script tags — in fact, every page on WorldlyCalc uses JSON-LD for its FAQ and breadcrumb schema markup.

Logging and analytics: Modern logging systems like ELK Stack (Elasticsearch, Logstash, Kibana), Datadog, and Splunk prefer structured JSON logs over plain text because JSON makes fields queryable, filterable, and aggregatable.

Tips for Working with JSON Effectively

Always validate before parsing: Wrap JSON.parse() in a try-catch block. Invalid JSON will throw a SyntaxError with a helpful message indicating the position of the error — this is exactly what this formatter displays.

Use JSON.stringify() for pretty-printing: JSON.stringify(obj, null, 2) formats JSON with 2-space indentation. The second parameter (replacer) can filter which keys to include; the third parameter controls indentation.

Watch for large numbers: JSON numbers are parsed as JavaScript floating-point numbers, which lose precision for integers larger than 2^53 - 1 (9,007,199,254,740,991). APIs returning large IDs (like Twitter's snowflake IDs) should send them as strings to avoid precision loss.

Handle dates carefully: JSON has no date type. The convention is to use ISO 8601 strings ("2026-03-26T12:00:00Z") or Unix timestamps (integers). Always document which format your API uses.