Private browser-based developer tool
Preview suggested corrections for common JSON syntax mistakes before applying them. Repairs are deliberately limited so that an uncertain guess does not silently replace your source.
The repair process shows the proposed output, describes the detected changes, and parses the result again. You decide whether to apply it and can continue editing if another issue remains.
Paste the malformed document and select Repair. Read every listed change and inspect the preview, especially strings, numbers, and punctuation near the original error. Apply only when the repaired value matches what the producer intended.
Automatic repair is appropriate for mechanical errors, not missing business data. A tool cannot infer a deleted property, choose between two plausible values, or know whether a string was intended to contain a quote.
The repair logic targets recognizable patterns such as common quote and punctuation mistakes. After transformation it validates the entire result. A “high confidence” label describes the syntactic pattern, not the semantic correctness of the data.
Fix the source manually when it contains truncated content, ambiguous escaping, duplicate keys with different values, or a mixture of JSON and another language. If the data came from an API or exporter, correcting the producer prevents the same defect from recurring.
No. Suggested output is shown in a preview and changes only after you apply it.
No. Some errors are ambiguous or indicate missing data. The tool intentionally avoids inventing content.
Review it. Valid syntax proves the text can be parsed, not that the repaired values match the original intent.