JSON vs JSON5: which format makes sense?

Quick answer

Use JSON when a machine or standard expects strict syntax. Use JSON5 when humans need to edit the file often and the toolchain explicitly supports those conveniences.

Side-by-side comparison

Format	Best for	Why teams like it	Main risk
JSON	APIs, schema markup, strict config, interchange	Predictable and portable	Less pleasant to edit by hand
JSON5	Human-maintained local config and drafts	Comments, trailing commas, friendlier syntax	Breaks strict parsers and validation pipelines

When JSON is the right choice

• API payloads
• Structured data
• Files that are validated by strict tooling
• Anything that needs to move between systems reliably

JSON is strict on purpose. That strictness is what makes it safe for production exchange.

When JSON5 is worth it

• Long-lived config files edited by developers
• Draft data where comments help collaboration
• Local tooling that explicitly supports JSON5

JSON5 helps humans, but only when the next step in the workflow agrees with it.

Common failure patterns

• Copying JSON5 with comments into a strict JSON validator
• Assuming “formatter support” means “runtime support”
• Using an editor convenience as if it were a deployment standard

A safer content workflow

1. Draft in the friendliest format your local workflow allows.
2. Convert and validate before anything becomes production-bound.
3. Treat schema, API payloads, and exported files as strict JSON unless proven otherwise.

The JSON Formatter is the fastest way to normalize and validate payloads. If the JSON is feeding schema markup, check the final structure again in the Structured Data Helper before publishing.