What Is JSON?

JSON (JavaScript Object Notation) is a lightweight, text-based data format used to exchange information between systems. Despite the name, JSON is language-independent and used across virtually every programming language and platform.

JSON Syntax Rules

JSON is strict about syntax. Here are the rules you must follow:

• Keys must be strings in double quotes: "name" ✅, name ❌, 'name' ❌
• Strings use double quotes only: "hello" ✅, 'hello' ❌
• No trailing commas: {"a": 1, "b": 2} ✅, {"a": 1, "b": 2,} ❌
• No comments: JSON does not support // or /* */ comments
• Numbers can't have leading zeros: 42 ✅, 042 ❌
• Boolean values are lowercase: true / false ✅, True / FALSE ❌

Common JSON Errors

These are the errors developers hit most frequently — and how to fix them:

Error	Wrong ❌	Correct ✅
Trailing comma	{"a": 1,}	{"a": 1}
Single quotes	{'key': 'val'}	{"key": "val"}
Unquoted keys	{key: "val"}	{"key": "val"}
Missing comma	{"a": 1 "b": 2}	{"a": 1, "b": 2}
Comments	{"a": 1} // note	{"a": 1}
Undefined/NaN	{"val": undefined}	{"val": null}

JSON vs. Other Formats

How does JSON compare to alternative data formats?

Feature	JSON	XML	YAML	CSV
Readability	Good	Verbose	Excellent	Simple
Data types	6 types	Text only	Rich types	Text only
Nested data	✅ Yes	✅ Yes	✅ Yes	❌ No
File size	Compact	Large	Compact	Smallest
Comments	❌ No	✅ Yes	✅ Yes	❌ No
API standard	Dominant	Legacy	Config files	Data export

Why Use a JSON Formatter?

Raw JSON from APIs often comes as a single compressed line — impossible to read or debug. A formatter:

• Pretty-prints with proper indentation so you can see the structure
• Validates syntax and pinpoints the exact line and character of errors
• Minifies for production use (removing whitespace to reduce file size)
• Sorts keys alphabetically for consistent, comparable output
• Tree view for exploring deeply nested objects visually

Validation Tips

Follow these practices to avoid JSON headaches:

1. Use a linter in your editor — VS Code, Sublime Text, and JetBrains IDEs all highlight JSON errors in real-time
2. Validate API responses — don't assume the data you receive is always valid JSON
3. Use JSON Schema — define the expected structure and validate programmatically
4. Test with edge cases — empty arrays, null values, Unicode characters, very long strings
5. Pretty-print during development — minify only for production

Frequently Asked Questions

What's the maximum size of a JSON file?

There's no official size limit in the JSON spec. In practice, limits come from the parser or system: most languages handle files up to hundreds of megabytes. For very large datasets, consider streaming parsers or formats like NDJSON (newline-delimited JSON).

Can I add comments to JSON?

No — the JSON specification explicitly does not allow comments. If you need comments, consider using JSONC (JSON with Comments, supported by VS Code), JSON5, or YAML for config files. Alternatively, use a "_comment" key as a convention.

What's the difference between JSON.parse() and JSON.stringify()?

JSON.parse() converts a JSON string into a JavaScript object. JSON.stringify() does the reverse — converts an object into a JSON string. Use JSON.stringify(obj, null, 2) for pretty-printed output with 2-space indentation.

← Back to Blog