Convert commented configuration to strict JSON

Prepare the actual source

Paste a commented configuration or select one UTF-8 file, then download strict JSON and its conversion report.

Paste up to 1 MiB or select one UTF-8 file up to 2 MiB; a selected file takes priority over pasted text. One leading UTF-8 BOM is removed and recorded.

Accept standard JSON values with // line comments, /* block comments */ and trailing commas. JSON5 single quotes, unquoted keys, hexadecimal numbers, NaN, Infinity and executable expressions are rejected.

• Paste JSONC or select your original UTF-8 configuration.
• Convert and review the removed-comment and trailing-comma counts.
• Download converted.json and conversion-report.json.
• Open the JSON in the intended application and check its numeric handling.

Review the conversion and both downloads

Reject malformed syntax and duplicate decoded keys in each object. No missing comma, broken string or invalid escape is automatically repaired.

At most 128 nested containers and 200,000 non-comment syntax tokens. Strict JSON is limited to 4 MiB; accepted source limits dominate that output guard.

{"url":"https://example.org/a//b",/* note */"id":9007199254740993,"items":[1,2,],}

Check the receiving application

Original numeric tokens, including large integers, decimal exponents and negative zero, stay byte-for-byte in the output. A consuming application may still round them; choose a reader with suitable precision.

The compact result omits comments, whitespace and trailing commas. Keys, strings, array order and number spellings are retained; this is syntax conversion, not configuration validation. Files and contents stay in this browser.

Correct the indicated syntax, use double-quoted keys and strings, and remove duplicate keys. Select a supported UTF-8 file or clear the file selection to use pasted input.

{"url":"https://example.org/a//b","id":9007199254740993,"items":[1,2]}