Guide · Large CSV on Mac
How to open a large CSV file
on a Mac
You double-click a CSV export and Numbers spins, or Excel opens it and quietly cuts off the rows past its limit. The file isn't broken — it's just bigger than a spreadsheet wants to handle. You only needed to check a few columns, run one filter, and export a clean slice, but now you're stuck.
Why spreadsheets choke on big CSV files
Numbers and Excel load the whole file into memory and cap out around a million rows — and they slow to a crawl long before that. They're built for editing a grid you can see, not for scanning a multi-million-row export. A CSV that came out of a database, an analytics tool, or an API dump is often well past that line, so the spreadsheet either freezes, truncates rows, or mangles your dtypes (leading zeros, dates, long IDs).
First, free ways to peek — no app
Your Mac already has tools to look at a big file without opening the whole thing.
- 1Count the rows from Terminal. Run wc -l file.csv to see how many rows you're dealing with before you try to open it.
- 2Look at the first lines. head -100 file.csv prints the header and first rows so you can check columns and delimiters without loading everything.
- 3Split the file into chunks. split -l 500000 file.csv part_ breaks it into smaller pieces a spreadsheet can open one at a time.
- 4Filter before you open. grep or awk can pull just the rows you need into a smaller file you can then open normally.
But doing this for every export is the problem
Terminal one-liners work, but they're clunky for a quick look: no schema view, no row-count summary, no SQL, no editing, and you still have to reassemble and export a clean result by hand. For a file that's too big for a spreadsheet but too small to deserve a database project, that's a lot of friction every time.
Open it locally: Mac CSV Power Editor
Mac CSV Power Editor opens large CSV, TSV, and Parquet files locally on your Mac. Drop the file, see the schema and row count, run DuckDB SQL right there, build a pivot, catch dtype problems, and export a clean result — without turning one file into a full database project.
- ✓ Millions of rows open in seconds. Local DuckDB engine, native AppKit grid, no Electron, Apple Silicon native.
- ✓ Query with SQL, build pivots, and validate dtypes; export to CSV, TSV, Parquet, or JSONL for the next tool.
- ✓ Local files stay local. No analytics or ad SDK; your API keys live in the Keychain.
- ✓ $14.99 lifetime, 14-day trial, 7-day refund, no subscription. Signed, notarized, macOS 13+.
FAQ
Why won't my large CSV open in Numbers or Excel?
Both load the entire file into memory and cap out around a million rows, slowing down well before that. A database or analytics export is often larger, so the spreadsheet freezes or truncates rows.
How do I open a big CSV without a spreadsheet?
On a Mac you can use wc -l to count rows, head to preview, split to break the file into chunks, and grep/awk to filter — or open the whole file in a tool built for large local files.
Can I query a CSV with SQL on a Mac?
Yes. Mac CSV Power Editor runs DuckDB SQL directly on local CSV, TSV, and Parquet files, with no database server to set up.
Do my files get uploaded anywhere?
No. Files are opened locally on your Mac. There is no analytics or ad SDK, and API keys for the optional LLM batch feature stay in the Keychain.