Question 1

What is the difference between JSON formatting and JSON validation?

Accepted Answer

JSON formatting (also called beautifying or pretty-printing) adds indentation and line breaks to make JSON human-readable — it does not change the data, only its presentation. JSON validation checks whether the JSON is syntactically correct according to the JSON specification (RFC 8259). Both are often done together: you format JSON to make it readable, and the formatter also validates it, flagging any syntax errors with the exact line and character position.

Question 2

Why is my JSON invalid? What are the most common JSON errors?

Accepted Answer

The six most common JSON errors are: (1) using single quotes instead of double quotes for strings and keys — JSON requires double quotes; (2) leaving a trailing comma after the last key-value pair in an object or the last element in an array; (3) including comments — JSON does not support comments of any kind; (4) unquoted keys like {name: "Alice"} — all keys must be quoted strings; (5) using undefined, NaN, or Infinity as values — these are JavaScript-specific and not valid JSON; (6) a stray character or byte at the start of the string (common when copying from some editors). Paste your JSON into the formatter to get the exact error location.

Question 3

How does JSON to CSV conversion handle nested objects and arrays?

Accepted Answer

Standard JSON to CSV conversion only works cleanly on a flat array of objects — where every item has the same top-level keys with primitive values. Nested objects ({"address": {"city": "London"}}) are typically either flattened (address_city: "London"), serialized as a string in the cell, or cause the converter to fail. Arrays within objects ({"tags": ["a","b"]}) are usually serialized as a comma-separated string. If your JSON has deep nesting, you may need to pre-process it to flatten the structure before converting.

Question 4

When should I convert JSON to XML instead of keeping it as JSON?

Accepted Answer

Convert JSON to XML when integrating with a system that requires XML — most commonly SOAP web services, enterprise APIs (banking, healthcare with HL7/FHIR over XML, government), legacy middleware, and tools that consume XML natively (XSLT transformations, XML-based configuration systems, RSS/Atom feeds). Microsoft Office formats (DOCX, XLSX) and Android resource files are also XML internally. For any new modern REST API, stay with JSON — it is faster to parse, more compact, and has direct browser support.

Question 5

Does the JSON diff tool care about key order?

Accepted Answer

No — JSON object key order does not matter in the diff. The objects {"a":1,"b":2} and {"b":2,"a":1} are treated as identical because JSON objects are unordered by definition. Array order does matter though: [1,2,3] and [3,2,1] are treated as different. This is the correct semantic behavior — reordering array items is a real change in most contexts.

Question 6

What delimiter should I use for CSV to JSON conversion?

Accepted Answer

Use commas for standard CSV files exported from most tools. Use semicolons for CSV files exported from European versions of Excel — European locales use commas as decimal separators, so Excel uses semicolons to separate fields instead. Use tabs for TSV files (tab-separated values), which are common in data pipelines and Google Sheets exports. The TSV format is also safer when your data contains commas, since tab characters rarely appear in normal text.

Question 7

Is my JSON data sent to any server?

Accepted Answer

No. Every operation in every JSON tool on this page — formatting, validation, minification, CSV conversion, XML conversion, and diff comparison — runs entirely in your browser using JavaScript. Your JSON data never leaves your device. There is no backend call, no server-side processing, and no data stored anywhere. You can confirm this by turning off your internet connection after the page loads — all five tools will continue to work.

Type	Example	Rules
Object	{"key": "value"}	Keys must be double-quoted strings; no trailing comma after last pair
Array	["a", 1, true]	Ordered list; no trailing comma after last element
String	"hello world"	Must use double quotes — single quotes are invalid JSON
Number	42 or 3.14	No quotes; integers or decimals; no leading zeros
Boolean	true or false	Lowercase only — True and False are invalid
Null	null	Lowercase only — Null and NULL are invalid

Context	Example files / systems	Notes
REST API responses	GitHub API, Stripe, Twilio, OpenAI	Must be valid JSON; minified in production
Node.js config	package.json, tsconfig.json, eslintrc.json	Strict JSON — no comments, no trailing commas
Editor / IDE config	.prettierrc, .vscode/settings.json	Some tools support JSONC (JSON with Comments)
Document databases	MongoDB, Firestore, DynamoDB, CouchDB	Stored as BSON internally; queried as JSON
Frontend state	localStorage, sessionStorage, IndexedDB	Serialized via JSON.stringify; parsed via JSON.parse
Data interchange	Webhooks, message queues, event payloads	Usually minified; often wrapped in an envelope object

JSON Tools

What Is a JSON Formatter and Validator?

Indentation Styles

JSON Syntax Reference

Common JSON Errors and How to Fix Them

Where JSON Is Used in Real Projects

All JSON Tools

Frequently Asked Questions

Related Tools

Code Beautifier

Hash Generator

Timestamp Converter