JSON Formatter: Frequently Asked Questions

Formatting adds whitespace and indentation to make JSON readable without changing its data. Validation checks whether the JSON is syntactically correct — whether it can be parsed by a JSON parser without errors. The ToolHive tool does both simultaneously.

Standard JSON (RFC 8259) does not allow trailing commas after the last item in an array or object. This is a common mistake when writing JSON by hand or copying from JavaScript code, where trailing commas are permitted. Remove the comma after the last item to fix it.

The formatter handles large JSON well since it runs in your browser. Files up to several megabytes format instantly. For extremely large files (tens of megabytes), a command-line tool like `jq` or a desktop editor with JSON support may be faster.

Keys are shown in indigo to stand out as structure identifiers. String values use orange. Numbers use green. Boolean values (true/false) use blue. Null uses grey. The colours work in both light and dark mode.

The formatter uses the browser's native JSON.parse(), which follows the strict JSON standard. JSON5 and JSONC are extensions of JSON and will fail validation if they include comments or unquoted keys. Remove comments before formatting.

Yes. Paste the contents of any JSON config file — package.json, tsconfig.json, .eslintrc, etc. — format it, then copy and paste it back. The formatter preserves all data exactly; only whitespace changes.

There is no artificial depth limit in the formatter. Very deeply nested JSON (100+ levels) may hit browser call stack limits in rare cases, but typical JSON responses rarely exceed 10 levels of nesting.

JavaScript object literals are not the same as JSON. JavaScript allows single quotes, unquoted keys, trailing commas, comments, and undefined values — none of which are valid JSON. Convert JavaScript objects to JSON using JSON.stringify() first.