How to inspect a 10-million-row CSV file locally

A large CSV file can be hard to check in a regular spreadsheet app. It may take a long time to open, freeze while you scroll, or be too large for the app to handle. If you only need to inspect the data, you may not need to import it into an online service.

The CSV Editor opens CSV files with up to 10 million rows in your browser. You can look through the data, search for values and sort rows. The file stays on your device.

Inspect the CSV file

1. Open the CSV Editor on a computer. A 10-million-row file can be demanding, so a desktop or laptop is a better choice than a phone.
2. Choose your CSV file in the file picker. Wait for the editor to load it. A large file may take a while, depending on its size, number of columns and your computer.
3. Check the column headers and several rows. Confirm that values appear in the columns you expect, and that dates, numbers and text are readable.
4. Use the find feature to search for a value you expect to be in the file. Try a distinctive name, ID or phrase rather than a common word.
5. If you need to check the order of the data, sort by a relevant column. Sorting millions of records can take longer than searching, so give the browser time to finish.

For a closer look at sorting a large file, see How to sort a large CSV file in your browser. If you plan to correct values, keep an untouched copy of the original first.

What the result means

The file opens and the columns look right

The editor can read the file, and the basic structure looks as expected. Check records near the beginning, middle and end if you are verifying the whole dataset. A few matching rows do not prove that every row is complete or correct.

Your search finds the expected value

The value is present in the data the editor can search. Check the other cells in that row to confirm it belongs to the record you had in mind. If the value appears several times, compare an ID or another unique field as well.

Your search finds nothing

The value may not be in the file, or it may be written differently. Check for extra spaces, punctuation, different capitalization or a shortened version of the value. Make sure you are searching the right field if the editor lets you choose where to look.

The browser becomes very slow or the file will not open

This does not automatically mean the CSV is damaged. A file with millions of records can use a lot of memory when the browser turns its text into rows and cells. A wide file with many columns may be harder to handle than a narrower file with the same row count.

How to handle a slow or unreadable file

1. Give the file time to load. Avoid repeatedly refreshing the page while it is processing. If the browser remains unresponsive for several minutes, close the tab and try the next steps.
2. Close other demanding apps and tabs. Browsers need memory to parse and display a large dataset. Close video calls, games and other large files before opening the CSV again.
3. Check that you selected the right file. Confirm the file is the CSV you meant to inspect, especially if you have several similarly named copies. Work from a copy if you are unsure.
4. Try a smaller portion of the data. If the full file still will not load, split it into smaller CSV files using a local tool that supports large files, then inspect the part you need. Keep the header row in each part so the columns remain identifiable.
5. Check the CSV formatting. A comma inside a quoted field is valid, but broken or unmatched quotes can make rows appear to have the wrong number of columns. If the columns do not line up, check how the file was exported before editing it.
6. Use a computer with more available memory. If a smaller file works but the full one repeatedly stalls, the device may not have enough memory for the whole dataset in the browser. A more capable computer or smaller file parts may be necessary.

Why the file can use more memory than expected

A CSV is stored as text, but the browser has to interpret that text and organize it into cells before you can search or sort it. The opened data can take much more memory than the file size shown on disk. The number of columns, the length of cell contents and the way the file is structured all affect how much work the browser has to do.

Also, a line break inside a quoted CSV value can be part of a cell rather than the start of a new record. That means counting visible line breaks in a text editor may not give you the true number of data rows.

The CSV Editor processes the file in your browser. Your CSV is not uploaded to TooLab.