DevToolsmith

JSON Repair

Recover JSON copied from logs, APIs or generated responses. Repair missing quotes, single quotes, trailing commas and incomplete structures, then review the original and repaired result side by side.

Runs 100% in your browser — nothing is uploaded

Original input
Tip: drop a file here74 chars · 74 bytes · 1 line
Repaired JSON — review before using
0 chars · 0 bytes · 0 lines

Fix copied object literals

For example, {name: 'Ada', active: True,} can be recovered as strict JSON with quoted keys, JSON booleans and no trailing comma. The result is formatted without rounding large numeric literals.

Review before continuing

Input: copied object literal
{name: 'Ada', active: True, id: 9007199254740993,}
Output from the repair engine
{
  "name": "Ada",
  "active": true,
  "id": 9007199254740993
}

Notice that quotes and the boolean spelling change, while the large ID remains exactly 9007199254740993. A repair can also infer an ending for an incomplete structure, but it cannot tell you which missing record or value was originally intended.

The two panels keep the original text available for comparison. Mark the result as reviewed to send it to the JSON formatter, viewer, type generator or another compatible tool. Repair does not prove that the inferred content matches the intended message.

Processing limits

Inputs are limited to one million characters; output to two million characters. A disposable worker can be cancelled and has an eight-second timeout. For ordinary valid JSON, use the JSON Formatter directly.

Use JSON Formatter for valid JSON, JSON Diff to compare structure, or JSON Schema Validator to check reviewed output against your application’s contract. A syntactically valid repaired document can still fail that contract.

Powered by open-source software. Third-party licenses.

Documentation examples checked: . How these tools are checked.

Frequently asked questions

Can this recover every broken JSON document?

No. Repair infers a likely structure and may close incomplete arrays or strings. Missing values cannot be reconstructed reliably. Compare the original and repaired result before using it.

Are large numbers preserved?

Repair and formatting operate on JSON text. Numeric literals such as 9007199254740993 are not round-tripped through JavaScript numbers. Duplicate keys are flagged and remain in the output.

Is my input stored?

Processing uses a disposable local worker. Input is not saved automatically or put into a share URL. Sending the reviewed output to another tool uses temporary session storage.

Sources

Spotted a mistake? Email hello@devtoolsmith.com and we’ll fix it.