Can it fix any broken file?
No. It targets common “almost JSON” mistakes. Completely truncated or binary data still fails.
Paste almost-JSON — trailing commas, comments, unquoted keys — and get valid JSON back. Useful for logs, LLM output, and copy-paste from JS.
JSON formatter
Run a tool to see a polished result here
Typical issues: trailing commas, // and /* */ comments, single-quoted strings, and unquoted keys. If the text is too far from JSON, you still get a clear error. All processing stays on this device.
The editor is prefilled with a small example for JSON Repair. Repair turns almost-JSON (trailing commas, comments, single quotes, unquoted keys) into parseable JSON when the text is close enough. Replace it with your own file; the sample and your payload stay in this tab.
{
// trailing comma + comment
name: 'jfmt',
tags: ['json', 'local',],
}This dedicated JSON Repair URL matches that search intent; the homepage stays the general formatter. Repair turns almost-JSON (trailing commas, comments, single quotes, unquoted keys) into parseable JSON when the text is close enough. Related tools on this site include beautify, validate, minify, JSON to CSV, JSON to YAML and JSON to XML — all local. JFmt runs in a Web Worker in this tab. Do not paste production secrets if you share your screen. Read errors in the output pane instead of sending production payloads to another service.
No. It targets common “almost JSON” mistakes. Completely truncated or binary data still fails.
It applies conservative fixes. It will not invent business data that was never there.
No. Repair runs in the browser like every other JFmt tool.
No. Parsing and conversion run in a Web Worker in this tab. jfmt.dev does not receive the payload.
So people searching for this operation land on a page that already selects it. Repair turns almost-JSON (trailing commas, comments, single quotes, unquoted keys) into parseable JSON when the text is close enough.