Excel Won't Open My Large CSV (1M+ Rows) - What to Do

Double-click a 2-million-row export and Excel either truncates it at 1,048,576 rows, freezes, or “helpfully” reformats your IDs and dates. The file is fine - the tool is wrong for the job. Google Sheets is not much better with its cell-count caps.

Preview the shape, export smaller batches from the source, filter to the rows you need, and convert only the slice Excel can handle. RividTech can preview, filter, and convert manageable files locally. For format-loss details, see Excel to CSV (and Back) Without Losing Data.

Step 1: diagnose the size and shape

Check row counts in the source application before exporting. Open a manageable slice in CSV Preview to inspect headers and check whether the first rows are real data or export junk.

• Over 1,048,576 data rows - must split or filter; Excel physically cannot hold it.

• Under the limit but slow - wide files (50+ columns) or long text fields freeze Excel; drop columns first.

• One column of commas - delimiter problem, not a size problem. Match the export separator to the importer.

Check for ragged rows and empty headers with a CSV-aware parser before importing.

Step 2: split into openable parts

Export smaller batches from the source application, or split the file locally using the options in Tools to Process CSV Files in the Terminal:

• By row count - e.g. 500k rows per part keeps every chunk safely under the Excel cap with headroom.

• By column value - e.g. one file per region, month, or status, so each part is meaningful on its own.

Keep headers in every part, name parts clearly (orders_2026-01.csv), and avoid re-saving a part in Excel before converting - Excel may change dates and leading zeros.

Step 3: sample when you only need a look

Often you do not need all 3 million rows - you need to check a mapping, debug an import, or build a pivot template. Request a sample from the source or use a local script to select:

• Head (first N) - best for schema checks and building formulas.

• Tail (last N) - best for recent data in append-ordered exports.

• Random - best for representative testing before a full run.

Step 4: shrink columns and filter rows

A 40-column export where you need 6 columns is 85% waste. Drop the rest with Column Tools (rename, drop, reorder), then filter in Data Process - e.g. only status = paid in 2026. A smaller, narrower file opens fast and converts cleanly.

Dedupe before counting: Remove Duplicates on the right key (order ID, email), and normalize labels with Find & Replace .

Step 5: convert only the slice Excel can open

Once a part is under the limit and clean, convert it:

• CSV to Excel - CSV slice to .xlsx for Excel users.

• Excel to CSV - back to CSV after edits, without Excel's save quirks.

• CSV to JSON - when the destination is an app or API, not a sheet.

Converting a file that still has delimiter or encoding issues bakes the damage into the workbook - clean first using How to Clean Messy CSV Files .

What about TSV, JSON, and SQL exports?

The same playbook applies: preview TSV with CSV Preview, which also reads tab-separated files, flatten API JSON with Flatten JSON , and generate load scripts with CSV to SQL when the data belongs in a database instead of a sheet.

Getting started

Start with a manageable export, inspect it in CSV Preview, filter in Data Process, and convert with CSV to Excel. Browser processing stays on your device - see our Privacy Policy.