Question 1

What is JSON and why does formatting matter?

Accepted Answer

JSON (JavaScript Object Notation) is a lightweight, human-readable text format for representing structured data — objects (key-value pairs) and arrays. It's the standard data format for REST APIs, configuration files, and data storage. Formatting (also called beautifying or pretty-printing) adds consistent indentation and line breaks so the structure is easy to read and debug. Minifying removes all whitespace to reduce file size for transmission. A common example: '{"name":"Alice","age":30}' is valid but hard to read at scale; formatted JSON with 2-space indent makes nested structures immediately clear. Good JSON formatting is essential for debugging API responses, reading config files, and reviewing data schemas.

Question 2

What are the most common JSON errors and how do I fix them?

Accepted Answer

Common JSON errors: (1) Trailing commas — JSON does not allow a comma after the last item in an object or array: {"a":1,} is invalid. (2) Single quotes — JSON requires double quotes around all strings and keys. 'name' must be written as "name". (3) Unquoted keys — all keys must be quoted: {name: 1} is invalid, {"name": 1} is correct. (4) Comments — JSON does not support comments. Remove any // or /* */ style comments before parsing. (5) Undefined values — undefined is not a valid JSON value (null is). (6) Control characters — raw newlines inside a string must be escaped as 
. (7) Missing brackets — unclosed {, [, or missing } ] at the end. Most JSON parse errors include a position or character index — count to that position in your JSON to find the exact issue.

Question 3

What is the difference between JSON and JSONC or JSON5?

Accepted Answer

Standard JSON (RFC 8259) is strict: no comments, no trailing commas, no unquoted keys, no single-quoted strings. JSONC (JSON with Comments) is a superset used by VSCode's tsconfig.json and settings.json — it allows // and /* */ comments but is not valid JSON for parsing with standard parsers. JSON5 is a broader superset that also allows trailing commas, single-quoted strings, unquoted keys, multiline strings, and hexadecimal numbers. Both JSONC and JSON5 are human-friendly config formats — strip comments before parsing them with a standard JSON parser. This tool validates against strict JSON (RFC 8259), which is what most programming languages and browsers use.

Question 4

How do I minify JSON and when should I?

Accepted Answer

Minifying JSON removes all unnecessary whitespace, newlines, and indentation, reducing the string to the most compact valid representation. A 50KB formatted JSON might become 20-25KB minified — a 50-60% size reduction. When to minify: (1) HTTP API responses sent over the network — smaller payloads load faster. (2) JSON stored in databases where space matters. (3) JSON embedded in JavaScript bundles. When NOT to minify: (1) Config files you read and edit manually. (2) Log files where readability matters. (3) Source-of-truth JSON stored in repos. Minification is typically done by your build tools or at the server level rather than manually, but it's useful for one-off payloads and debugging large files.

Question 5

What is JSON Schema and how does it validate JSON?

Accepted Answer

JSON Schema is a vocabulary for describing the structure and constraints of a JSON document. A schema might specify that a field must be a string, that a number must be between 0 and 100, that an array must contain at least one item, or that a specific set of keys is required. For example: {"type": "object", "properties": {"name": {"type": "string"}}, "required": ["name"]} would validate that any JSON object has a 'name' property of string type. JSON Schema validators (like AJV for JavaScript, jsonschema for Python) check a JSON document against a schema and report violations. This tool validates structural correctness (is this valid JSON?) rather than schema conformance (does it match a specific schema?). For schema validation, use a dedicated JSON Schema validator with your schema file.

JSON Formatter & Validator

Formatting and Validating JSON

Common JSON syntax errors

JSON vs JSONC vs JSON5

Minifying JSON payloads