Automatically fix missing quotes, trailing commas, bracket mismatches, single quotes, and escape issues. Supports local repair first, with AI-assisted deep repair when needed.
無効な JSON を入力すると、システムは次の方法を順に試します:
JSON の修復を開始
壊れた JSON を入力するか、Import でファイルから読み込みます。
Repair JSON works best between validation and formatting. Start with the raw broken payload, let the tool try deterministic local repair first, use AI-assisted repair only if needed, then move the recovered JSON into validation, formatting, or export.
Recover broken text into usable JSON
A lot of broken JSON is not just ugly - it is completely unusable. The repair step matters because it gets that payload back into a valid JSON shape so validation, formatting, comparison, and export are possible again.
If the JSON is too broken to parse at all, starting with Repair JSON is often faster than starting with manual validation.
Repair JSON is usually used for messy real-world payloads, not classroom examples. These examples match common issues in legacy systems, config cleanup, and corrupted logs.
Useful for old systems, script-generated payloads, or manually assembled responses that almost look like JSON but are not actually valid.
This category is usually fixed by local repair alone, without needing AI.
Teams often write JavaScript object style config and only realize later that strict JSON does not allow comments or trailing commas.
Repair JSON is ideal for pulling almost-JSON config back into a strict JSON form.
When a payload includes truncation, escape damage, and multiple bracket errors at once, deterministic local rules may not be enough. That is where AI repair becomes useful.
After this kind of repair, validate the result again before trusting it in downstream workflows.
Tutorial Step
手順 1 – 壊れた JSON を貼り付ける
The repair tool needs the original context more than a half-cleaned version. Logs, old API responses, and broken config files are often easier to repair when you keep the raw text intact instead of manually deleting large sections first.
Tutorial Step
手順 2 – 自動修復プロセス
Not every repair uses AI. Most broken JSON is fixed by deterministic local rules, so the real goal here is to understand the repair order instead of assuming every issue needs an AI rewrite.
Tutorial Step
手順 3 – 修復結果を確認する
A successful repair is not only about making the JSON parse again. You also need to confirm that the result still matches the intended business structure, especially for nested objects, arrays, and partially corrupted logs.
Tutorial Step
手順 4 – クリーンな JSON を使う
Repair is the recovery step, not the final destination. Once the JSON is usable again, you should immediately move it into the right next tool depending on whether you need validation, readability, schema generation, or field-level review.
A more reliable repair workflow
Paste the raw broken JSON into Repair JSON before doing broad manual cleanup.
Let local repair run first and use that result when it is enough, rather than forcing every case through AI.
If the structure is still too broken, split the payload or let AI repair handle the more complex reconstruction.
Validate the repaired output next, then move it to the formatter, table editor, or schema tools depending on your goal.
If the result matters for team review or rollback, download the repaired version instead of only copying it to the clipboard.
Repair JSON is most useful not because it saves one comma fix, but because it recovers data that would otherwise be blocked from the rest of your JSON workflow.
Practical repair tips
修復システムは多層アプローチです。まず JSONRepair ライブラリで高速かつ確実に修正し、次に基本的なパターン修正を行い、それでも難しい場合は AI プロバイダー（AI、OpenRouter、Groq）で複雑な問題に対応します。
はい。ローカル修復（JSONRepair とパターン修正）はすべてブラウザー内で完結し、データを保存しません。複雑なケースで AI 修復を使用する場合、JSON は処理のために AI プロバイダー（AI）へ送信されますが、保存や学習には使用されません。
1) JSONRepair — 多くの一般的な問題を高速かつ正確に修復。2) 基本修復 — 単純な構文エラーに対するパターン修正。3) AI 修復 — 複雑な構造問題に対して AI などの AI プロバイダーを使用します。
はい。キーの引用符不足、末尾の余分なカンマ、要素間のカンマ欠落、括弧の不一致などの一般的なエラーはローカル修復エンジンで自動的に修正されます。
はい。安定性のため、AI 修復は 1 リクエストあたり約（~18000 文字）までを想定しています。より大きい JSON はローカル（JSONRepair/基本修復）で直すか、AI 修復前に小さく分割してください。
いいえ。API キーは不要です。複雑なケースでは、ローカル修復と内蔵修正に加えて（当社が管理する）AI API 連携で結果を強化します。設定なしで利用できます。
一般的な問題に対しては JSONRepair が高い精度を発揮します。基本パターン修正は単純な構文エラーに対応し、必要に応じて AI プロバイダーが複雑な構造問題を解析して修正します。
If large sections of the payload are missing, truncated, or business meaning depends on context only you know, automatic repair can only recover syntax, not your original intent. In that case, combine validator diagnostics with manual fixes.
