Know what valid JSON permits
JSON uses double-quoted property names and string values. It supports objects, arrays, strings, numbers, booleans and null. Comments, trailing commas, unquoted keys and language-specific values such as undefined are not part of standard JSON.
Validate before formatting
A formatter can only reliably indent data after it parses successfully. When validation fails, inspect the reported position and the characters immediately before it; a missing quote or bracket often causes the parser to report the next token rather than the original mistake.
- Paste a redacted copy into the validator.
- Fix the first reported error.
- Validate again until the complete document parses.
- Format the valid result for review.
Remove secrets and personal data
Logs and API payloads can contain access tokens, cookies, email addresses or customer records. Replace sensitive values before using any debugging tool. Local browser processing reduces exposure to the application server, but screen sharing, browser extensions and clipboard history can still reveal data.
Preserve machine meaning
Formatting changes whitespace, not the data model. Minification can reduce transfer size, but it does not encrypt or secure information. After editing, run application tests because a syntactically valid value can still violate the API’s required schema or business rules.
Frequently asked questions
Is JSON formatting the same as validation?
Formatting makes parsed data easier to read. Validation confirms syntax; application-specific schema validation is a further step.
Can JSON contain comments?
Standard JSON does not support comments. Some configuration formats extend JSON, but their output may not work with a strict parser.





