What Clean does and does not do
BOM, zero-width characters, trailing commas, and extra whitespace are in scope. Missing quotes, truncated model output, or JS treated as JSON belong on Repair.
JSON Tools for AI Developers · Runs locally
Natural language generation · Schema · Zod · OpenAPI · Function Calling · MCP · 30+ tools
Text copied from Excel, Windows Notepad, or a legacy API often carries a BOM or an extra comma at the end of an object.
Click Clean JSON to strip that noise so Format and Validate fail one less time.
Clean is conservative: it does not guess business fields or rewrite nesting. Thoroughly broken text belongs on Repair.
Data stays in the browser. Good for export files that contain internal fields.
BOM, zero-width characters, trailing commas, and extra whitespace are in scope. Missing quotes, truncated model output, or JS treated as JSON belong on Repair.
Clean first, then Format. Formatting dirty text often fails on line 1 and looks like "the tool is broken."
Common trailing commas at the end of objects and arrays, yes. Comments or odd concatenation need a human look.
Use Clean for junk characters, BOM, and trailing commas. Use Repair for missing brackets or quotes.
The goal is parseable text, not a single line. Minify on the Format page if you need that.
No.
An invisible mark at the start of a file, common when Notepad saves UTF-8. JSON.parse sometimes fails because of it.
We don't promise to strip comments. If you have // or /* */, delete them by hand or try Repair.
It does not rewrite values on purpose. Clean targets noise, not a business-data reserialize.
The input may not be JSON at all. Check whether it is XML, YAML, or a log fragment.