Check whether text is valid JSON. The page parses it the way a JSON parser in your code would, as strictly as the JSON standard. An error comes with its line, its column and what the parser expected there. Most mistakes can be fixed with "Repair", here or in JSON Repair.
How to use it
- Paste JSON or open a file.
- The result updates as you type: "Valid JSON" with a summary, or the first error and where it is.
- Use "Repair" to fix common mistakes, then copy or download the corrected JSON.
Read more: A JSONLint alternative for large JSON files · 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. JSON and XML input can be up to 1 GB, depending on available memory. Processing runs in a background worker; large analyses can take a minute or more. 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.
Read an error message
This object is missing a comma after 149:
{
"id": "ord_002",
"total": 149
"status": "pending"
}The validator reports Invalid JSON at line 4, column 3: Expected ',' or '}', found '"'. Line 4 is where the parser noticed the problem, at the quote that starts "status". The missing comma belongs at the end of the line before it. That's typical: look at the reported position first, then at the end of the previous line.
Other messages you're likely to see, for the same object written differently:
| Input | Message | Fix |
|---|---|---|
"tags": ["new", "gift",] | Trailing comma | Remove the comma before ] or } |
id: "ord_002" | Expected a "quoted" key, found 'i' | Put the key in double quotes |
"note": 'gift' | Unexpected ''' | Use double quotes for strings |
When the text is valid, the result says what it holds, such as Valid JSON: an object with 5 keys or a list of 120 items, so you can check that a file has the shape you expect. To fix these errors automatically, use JSON Repair; it lists every change it makes.
Questions
What makes JSON invalid?
Usually single quotes instead of double quotes, keys without quotes, trailing commas, comments, a missing comma or bracket, or values like NaN, undefined or Python's True and None.
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.
How large a file can it handle?
JSON, XML and CSV input can be up to 1 GB, depending on memory. YAML input and JSON repair are limited to 128 MB. Validation runs in a background worker. jq, text editing and text-based exports have separate limits, shown when you use them.
Does it validate against a JSON Schema?
This page checks syntax only. To check data against a schema, open it in GigaJSON and use Types, then Validate.
Why does the error point at the line after my mistake?
The parser reports where it noticed the problem. A missing comma is only noticed at the start of the next value, so the error points at the following line. Check the end of the line before the reported one too.
Is JSON with comments valid?
No. Standard JSON has no comments. Files such as tsconfig.json allow them because their tools read a looser format (JSONC). To use one as plain JSON, JSON Repair removes the comments.
Is this a JSONLint alternative?
For large files, yes. JSONLint works well for a pasted snippet. This validator also opens files of hundreds of MB, up to 1 GB, and shows the line and column of the first error.
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