Skip to content
JSONRow
Colour theme

Convert large JSON files to CSV

For exports that other online converters can’t open: hundreds of megabytes and millions of records. Your file is processed on this device. Nothing is uploaded.

Choose a JSON file, or drop it here

JSON and JSON Lines (.json, .jsonl, .ndjson). Large files are fine; very large ones depend on your device’s memory.

Your file is processed on this device. Nothing is uploaded.

Why large JSON files fail elsewhere

Most converters read the whole file into memory as text, then build every record as an object before they write anything. Done that way, a 500 MB file can need several gigabytes, and the browser tab freezes or crashes. Converters that upload your file usually cap it at a few megabytes.

How this converter handles them

  • It reads the file in 4 MB pieces, in a background thread, so the page stays responsive.
  • The first pass checks the JSON and records the shape of the data rather than the data itself: field names, types and how often each appears. That’s how a field that first appears near the end of the file still gets a column.
  • The second pass cuts each record out of the file, converts it and writes the CSV to your browser’s storage on disk. Only a few megabytes are held in memory at any time.

Measured on a real file

A generated 500 MB JSON file with 1,423,751 records, each with nested objects and arrays, converted to 13 columns:

StepResult
Reading and checking the file13 seconds
Converting and writing the CSV (338 MB)35 seconds
Most memory the converter usedAbout 70 MB

Measured in Chrome 157 on a Windows laptop with an Intel Core i5-1334U processor and 16 GB of memory. Your times depend on your device. Phones and older computers are slower.

Tips for very large files

  • Use a computer rather than a phone. Phones limit how much memory a tab can use.
  • Close other heavy tabs before you start.
  • Check your free disk space. The CSV is written to your browser’s storage first and then saved to your downloads, so for a moment it takes up space twice.
  • If the file stops with an error near the end, it was probably cut off while downloading. The error message gives the line and column.

Limits

Time grows in proportion to file size, because every byte is read twice. A single record larger than 256 MB can’t be converted. Excel opens at most 1,048,576 rows, so a CSV with more rows than that opens only partly in Excel, although databases, Python and most data tools read all of it.

Questions

How large a file can it handle?

Files of 500 MB have been tested. There is no fixed limit: memory use stays about the same as files get bigger, so the practical limits are time and free disk space. A single record larger than 256 MB can’t be converted.

Why is the file read twice?

The first read checks that the JSON is valid and finds every field before anything is written, so a problem near the end of the file doesn’t leave you with a half-written CSV. The second read does the conversion.

Will the page freeze while it works?

No. The work happens in a background thread, so the page stays responsive and you can cancel at any time.

Does it work with large JSON Lines files?

Yes. Large .jsonl and .ndjson files are read the same way, one record after another.

To see exactly what happens to your file, read how the converter works, including how to check that nothing is uploaded.

  • JSON to CSV: Turn an API response or export into a spreadsheet, with nested fields as columns.
  • JSON Lines to CSV: Convert NDJSON logs and exports, where each line is one record.