JSON5 / JSONC → strict JSON

Client

Paste relaxed JSON (comments, trailing commas, JSON5-style keys) and convert it to standard JSON for transport, tests, or pipelines that expect JSON.parse-compatible text.

Learn more: JSON5 and JSON with comments

Parse relaxed JSON (JSON5 or common JSONC-style configs) and emit strict JSON text—useful before feeding data to tools that only accept standard `JSON.parse` input.

Why strict JSON

Many APIs, test runners, and CLIs accept only RFC 8259 JSON: double-quoted keys, no comments, no trailing commas. Converting here keeps your editor-friendly source and produces transport-safe output in one step.

Limits

The parser follows JSON5 rules; extremely large files may stress the tab—trim or split in your editor first. Numeric precision follows JavaScript’s JSON number rules after parsing.

Relaxed JSON → strict JSON

?

Parses JSON5 (unquoted keys where allowed, trailing commas, comments) and common JSONC config shapes, then emits standard JSON for APIs and JSON.parse.

Output is RFC 8259 JSON only—comments and relaxed syntax are stripped.

Common use cases

  • Convert JSON with comments or trailing commas (JSONC-style) into strict JSON for APIs and tests that call JSON.parse.
  • Normalize editor-friendly config drafts into RFC 8259 output before committing or publishing.
  • Explore JSON5-specific syntax (unquoted keys where allowed) and emit portable JSON for downstream tools.

Common mistakes to avoid

  • Sending JSON5 to a service that only accepts strict JSON

    Relaxed syntax is for authoring. Production HTTP bodies and many parsers still require standard JSON—convert first.

  • Assuming comments are preserved after conversion

    Strict JSON cannot store comments. They are stripped when producing standard JSON.

FAQ

Does conversion run on your servers?

No. Parsing and emitting strict JSON happen locally in your tab.

Is JSON5 the same as JSONC?

They overlap in practice (comments, trailing commas). This page accepts common relaxed inputs and outputs strict JSON; exact dialect flags depend on the source file and consumer.

More tools

Related utilities you can open in another tab—mostly client-side.