JSON Swiss 標誌

JSON Swiss

JSON Repair

損壞的 JSON 輸入

1

已修復的 JSON 輸出

設定

JSON 修復如何運作

當您輸入無效 JSON 時，系統會依序自動嘗試以下方法：

1
JSONRepair 函式庫
快速、精準地修復大多數常見問題
2
基礎模式匹配
處理簡單語法錯誤
3
AI 提供者
用於複雜情況的 AI 等

開始修復 JSON

輸入損壞的 JSON，或點選「匯入」從檔案載入。

逐步指南：如何修復損壞的 JSON

1步驟 1：貼上損壞的 JSON2步驟 2：自動修復流程3步驟 3：檢視修復後的 JSON4步驟 4：使用乾淨的 JSON

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

Repair JSON is most valuable when the payload is too broken to use anywhere else

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.

Broken input
1
{
2
name: "Project X",
3
'id': 1024,
4
items: [
5
"A",
6
"B",
7
]
8
}
Repaired output
1
{
2
"name": "Project X",
3
"id": 1024,
4
"items": [
5
"A",
6
"B"
7
]
8
}

If the JSON is too broken to parse at all, starting with Repair JSON is often faster than starting with manual validation.

3 repair examples that reflect real workflows

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.

Legacy API

Fix missing quotes and mixed quoting styles quickly

Useful for old systems, script-generated payloads, or manually assembled responses that almost look like JSON but are not actually valid.

損壞的 JSON
1
{
2
orderId: 'SO-1024',
3
customer: {
4
name: 'Maeve'
5
}
6
}
已修復的 JSON
1
{
2
"orderId": "SO-1024",
3
"customer": {
4
"name": "Maeve"
5
}
6
}

This category is usually fixed by local repair alone, without needing AI.

Config Cleanup

Strip comments and trailing commas so config parses again

Teams often write JavaScript object style config and only realize later that strict JSON does not allow comments or trailing commas.

損壞的 JSON
1
{
2
"env": "prod",
3
"retry": 3, // retry count
4
"features": {
5
"betaCheckout": false,
6
}
7
}
已修復的 JSON
1
{
2
"env": "prod",
3
"retry": 3,
4
"features": {
5
"betaCheckout": false
6
}
7
}

Repair JSON is ideal for pulling almost-JSON config back into a strict JSON form.

Complex Logs

Use AI only when deterministic repair is not enough

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.

損壞的 JSON
1
{"event":"checkout","user":{"id":42,"name":"Maeve"},"items":[{"sku":"A-1","qty":2},{"sku":"B-8","qty":1],"status":"paid"
已修復的 JSON
1
{
2
"event": "checkout",
3
"user": {
4
"id": 42,
5
"name": "Maeve"
6
},
7
"items": [
8
{
9
"sku": "A-1",
10
"qty": 2
11
},
12
{
13
"sku": "B-8",
14
"qty": 1
15
}
16
],
17
"status": "paid"
18
}

After this kind of repair, validate the result again before trusting it in downstream workflows.

  1. 01

    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.

    • 複製無效或損壞的 JSON（例如來自日誌、舊 API 或設定檔）。
    • 將其貼到左側編輯區；也可以拖曳檔案或使用「匯入」按鈕。
    • 不必擔心鍵名未加引號或尾隨逗號等錯誤——本工具就是為此而設計。
    • If the validator already showed a long list of syntax failures, switching here usually saves more time than fixing them one by one.
    • Keeping the raw payload intact gives both local repair and AI repair a better shot at reconstructing the intended structure.
  2. 02

    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.

    • 當 JSON 無效時，會出現「修復」按鈕（也可手動點擊）。
    • 工具會先嘗試快速的本地修復，立即修復語法問題。
    • 若本地修復不足，系統會自動升級至 AI 修復引擎以推斷意圖並修復結構。
    • The progress indicator helps you see whether the page is doing local repair, AI repair, or final validation of the repaired result.
    • If the input is too large for AI repair, split it into smaller logical chunks instead of retrying the same oversized payload.
  3. 03

    Tutorial Step

    步驟 3：檢視修復後的 JSON

    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.

    • 右側面板會顯示已修復且有效的 JSON。
    • 我們會自動美化格式，方便您確認資料結構與值。
    • 查看有效性指示，確認其符合標準 JSON 語法。
    • If the repaired result still looks suspicious, return to the validator or original source instead of pushing it downstream blindly.
    • For logs and configuration, pay special attention to booleans, numbers-as-strings, and datetime fields after repair.
  4. 04

    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.

    • 點選「複製」將修復後的 JSON 複製到剪貼簿。
    • 下載為 `.json` 檔案以便備份。
    • 若想繼續手動編輯，可使用「套用」將結果移回輸入區。
    • If you need row-and-column review, filtering, or bulk edits, continue into the table editor.
    • If the repaired JSON is now stable, it is also a much better input for schema generation, type generation, and transformation steps.

A more reliable repair workflow

1

Paste the raw broken JSON into Repair JSON before doing broad manual cleanup.

2

Let local repair run first and use that result when it is enough, rather than forcing every case through AI.

3

If the structure is still too broken, split the payload or let AI repair handle the more complex reconstruction.

4

Validate the repaired output next, then move it to the formatter, table editor, or schema tools depending on your goal.

5

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

If the payload only has a few syntax problems, repair is fast. If large sections are missing, repair can recover syntax but not invent the original business data.
For very large payloads, split the JSON into logical chunks before repair. Success rates are usually better that way.
Do not ship or store the repaired result blindly. Validate it first, then decide whether it also needs formatting.
If you need to inspect fields one by one after repair, the table editor is often easier than scanning a long JSON blob.

相關 JSON 工具

  • 修復完成後，您可能還需要格式化、驗證或轉換資料。

驗證 JSON

嚴格驗證 JSON 是否符合規範，並精準定位錯誤位置。

格式化 JSON

支援美化與壓縮，並提供進階縮排選項。

Schema 產生器

根據修復後的資料產生 JSON Schema，用於更穩健的驗證。

JSON 轉 TypeScript

將 JSON 直接轉換為 TypeScript 介面或型別。

JSON 轉表格

使用類似試算表的視覺化介面編輯 JSON 資料，即時更新。

常見問題

JSON 修復是如何運作的？

我們的修復系統採用多層策略：先使用 JSONRepair 函式庫進行快速、可靠的修復；再進行基礎模式匹配；若仍不足，再呼叫 AI 提供者（AI、OpenRouter、Groq）處理更複雜的問題。

我的資料安全嗎？

是的。所有本地修復（JSONRepair 函式庫與模式匹配）都在您的瀏覽器中完成，我們不會儲存任何資料。若您使用 AI 修復處理複雜問題，您的 JSON 只會被傳送至 AI 提供者（AI）用於處理，不會被儲存或用於訓練。

使用了哪些修復方法？

1）JSONRepair 函式庫：快速且精準地修復大多數常見問題。2）基礎修復：以規則為基礎，處理簡單語法錯誤。3）AI 修復：在需要時使用 AI 等 AI 提供者處理複雜結構問題。

能修復缺少引號或逗號的問題嗎？

可以。鍵名缺少引號、尾隨逗號、元素之間缺少逗號、括號不匹配等常見錯誤，都會由本地修復引擎自動處理。

AI 修復有大小限制嗎？

有。為了穩定性，AI 修復每次請求支援的輸入約為（~18000 個字元）。更大的 JSON 通常可以透過本地 JSONRepair/基礎修復處理，或先拆分為更小片段再使用 AI 修復。

需要 API Key 嗎？

不需要。您不必提供任何 API Key。對於複雜情況，我們會在本地修復基礎上，使用我們代管的 AI API 提升結果，開箱即用。

修復的準確度如何？

對於常見問題，JSONRepair 的準確度很高；基礎模式匹配可處理簡單語法錯誤；當需要時，AI 提供者會針對複雜結構問題進行智能分析與修復。

When should I fix JSON by hand?

Use manual fixes when key sections are missing, the recovered structure does not match the source intent, or the data needs domain-specific decisions that an automatic repair cannot make.