Paste broken JSON and get valid JSON back. Repair handles missing or single quotes, missing commas and brackets, trailing commas, comments, cut-off documents, Python's True/False/None, JSONP, and JSON copied out of an AI chat with text around it. Each line it changed is listed. To only check whether JSON is valid, use the JSON Validator.
How to use it
- Paste the broken JSON or open a file.
- The repaired JSON appears, with a list of the lines that changed.
- Copy or download it, or open it in GigaJSON to keep working on it.
Read more: A JSONLint alternative for large JSON files · Unescape JSON: fix strings full of backslashes · n8n $json expressions explained: paths, items and $jmespath · How to open a JSON file on Windows, Mac, a phone or in Excel · How to fix invalid JSON: the 10 most common errors
Private, and made for big files
This tool runs in your browser, in a background worker: nothing you paste or open is uploaded, and nothing is kept after you leave. Input is limited to 128 MB. Processing runs in a background worker. Already loaded features keep working if your connection drops. Loading another tool or jq for the first time needs a connection. When one tool isn't enough, GigaJSON opens your data with a tree, a table, JSONPath/JMESPath/jq queries, transforms, diff and history.
Repair a trailing comma, then check the result
Input: {"id":"ord_002","status":"pending",}. JSON does not allow the comma before the closing brace. Repair produces {"id":"ord_002","status":"pending"}.
A successful parse only proves the result is valid JSON. It does not prove that missing values were recovered correctly. Compare important fields before using a repaired response. See ten common JSON errors for examples you can identify and fix yourself.


Questions
What can it repair?
Keys without quotes, single or curly quotes, missing commas, missing closing brackets (cut-off JSON), trailing commas, // and /* */ comments, Python constants, MongoDB types like NumberLong(), JSONP, string concatenation, newline-delimited JSON and Markdown code fences.
How do I fix invalid JSON?
Paste it above. Repair rewrites it as valid JSON and lists every line it changed, so you can check the result. To find the error yourself instead, the JSON Validator shows its line and column.
What can't it repair?
Anything ambiguous, such as a doubled comma between values. Instead of guessing, it tells you the line and column.
Can it fix JSON copied from ChatGPT or another AI?
Yes. When the answer has the JSON in a Markdown code block, Repair uses the block and drops the text around it, then fixes trailing commas, comments or a cut-off end. Check the result: Repair makes the text valid, but it can't tell whether the AI left data out.
Is my data uploaded?
No. The tool runs in your browser, in a background worker. Nothing you paste or open goes to a server, and nothing is kept after you leave the page.
All tools
- JSON FormatterIndent with 2 or 4 spaces, sort keys
- JSON ValidatorLine and column of the first error
- JSON MinifierRemove whitespace, see the bytes saved
- JSON RepairFixes quotes, commas, comments, AI output
- JSON Schema GeneratorA JSON Schema from examples
- JSON Schema ValidatorCheck JSON against a schema
- JSON Token CounterCount tokens, select data, compare JSON and TOON
- JSON EditorTree and code editing, undo and history
- Large JSON ViewerTree, table and search for huge files
- JSON Lines ViewerJSONL and NDJSON logs as a table
- JSON Log ViewerCount and filter JSON Lines logs
- Large CSV ViewerCSV files too big for Excel, up to 1 GB
- JSON VisualizerThe data as a graph, PNG and SVG export
- JSON DiffChanges between two documents
- JSON Path FinderClick a value, copy its path
- JSONPath TesterJSONPath, JMESPath and jq, live
- JMESPath PlaygroundJMESPath, for AWS CLI queries too
- jq PlaygroundReal jq in your browser
- JSON to CSVNested objects become dotted columns
- JSON to ExcelAn .xlsx sheet, numbers kept as numbers
- CSV to JSONDelimiters detected, 007 stays 007
- JSON to XML@keys become attributes
- XML to JSONRSS feeds, sitemaps, SOAP responses
- JSON to YAMLReadable YAML, ambiguous strings quoted
- YAML to JSONAnchors and multiple documents
- JSON Lines to JSONNDJSON or JSONL into one array
- JSON to JSON LinesA JSON array as one record per line
- JSON to TOONConvert JSON to TOON, with token counts
- JSON to MermaidA flowchart or class diagram, drawn
- JSON SplitterCut a big file into parts, or sample it
- JSON to TypeScriptInterfaces inferred from your data
- JSON to GoGo structs with json tags
- JSON to RustRust structs that derive serde's Serialize and Deserialize
- JSON to PythonPython dataclasses with type hints
- JSON to JavaJava classes with getters and setters
- JSON to C#C# classes with System.Text.Json attributes
- JSON to KotlinKotlin data classes
- JSON to SwiftSwift structs that conform to Codable, with CodingKeys
- JSON to DartDart classes with fromJson and toJson
- JSON to ZodZod schemas with TypeScript types inferred from them
- JWT DecoderHeader, payload and expiry, locally
- JSON EscapeText to a JSON string and back
- Sample JSON FilesDownload test JSON, 100 KB to 1 GB
- Sample JSON Lines FilesDownload test NDJSON, one record per line
- Sample CSV FilesDownload test CSV, 100 KB to 1 GB
- Sample XML FilesDownload test XML, 100 KB to 1 GB
- Sample GeoJSON FilesPoints, lines and polygons, up to 1 GB
- Sample Nested JSONRecords 8 levels deep, up to 1 GB
- Sample Unicode JSON13 scripts, emoji and escapes
- Sample API ResponsesJSON:API, HAL, GraphQL, pages, errors
- Large JSON File GeneratorTest data from 100 KB to 1 GB