JSON repair helper

What this tool does

The helper uses a repair pass for common syntax issues, then parses and pretty-prints the result. It is meant for log snippets, copied objects, and JSONC that you need to feed to a strict parser.

How to use it

1. Paste the broken JSON.
2. Read the warning. Repair is best-effort.
3. Diff the output against what you expected before using it.

Privacy

This tool processes files and text locally in your browser. Your content is not uploaded or stored by this site.

ConvertPass does not include your input in analytics, URLs, or error reports. Encoding: UTF-8. Limit: 2 MB (2.00 MB).

Limitations

• Repair can invent structure. Always review the output.
• Binary data, truncated files, and mixed log lines may produce nonsense rather than a useful document.

Example

{name: 'ConvertPass', local: true,}

{
  "name": "ConvertPass",
  "local": true
}

Troubleshooting

Repair succeeds but the data looks wrong

Stop and fix the source document. The helper cannot know whether a missing brace should close an object or an array.

FAQ

Can I use this in a production pipeline?

Only with review. Silent repair in a pipeline hides data loss. Prefer rejecting invalid JSON at the boundary and fixing producers.

Does it execute JavaScript?

No. It does not evaluate the input. It only rewrites text toward JSON grammar.

Will it keep comments?

No. Comments are discarded because JSON has nowhere to put them.

What mistakes can it usually fix?

Trailing commas, single quotes, unquoted keys, and simple comments. Truncated files and concatenated objects are much less reliable.