Solution / Large CSV

A large CSV viewer that keeps the file on your machine.

Open, search, sort, edit, calculate, and export oversized CSV files in a browser tab. Jason pages the working project through local storage; your spreadsheet content is not uploaded to Jason.

Open a large CSV free Inspect the 20.97 GB run
reconciliation-2026.jason1,000,000,000 cellsD4:D999999999=SUM(D:D)
ABCDEF
1txn_idposted_ataccountamountfeebalance
24180029982026-07-02ACC-103719.730.37814.47
34180030052026-07-03ACC-107427.060.511117.06
44180030122026-07-04ACC-111134.390.651419.65
54180030192026-07-05ACC-114841.720.791722.24
64180030262026-07-06ACC-118549.050.932024.83
74180030332026-07-07ACC-122256.381.072327.42
84180030402026-07-08ACC-125963.711.212630.01
94180030472026-07-09ACC-129671.041.352932.60
104180030542026-07-10ACC-133378.371.493235.19
114180030612026-07-11ACC-137085.701.633537.78
124180030682026-07-12ACC-140793.031.773840.37
134180030752026-07-13ACC-1444100.361.914142.96
144180030822026-07-14ACC-148117.690.34730.26
154180030892026-07-15ACC-151825.020.481032.85
SUM 41,882,004.19ROWS 166,666,666LOCAL PROJECT — NOT UPLOADED
Largest measured file20.97 GB888 million cells
Measured first import3.9 min20.97 GB CSV
Measured cold open111 msmedian after import
Local project size0.795 GiB24.6× smaller than source
From file to working project

Opening the file is only the first step.

01

Open

Import CSV for free. Pro adds structured-data and document sources through the Local Data Suite. Nothing is uploaded to Jason.

02

Work

Search, sort, edit, calculate, and navigate the full dataset through a responsive canvas grid.

03

Return

Reopen the local project without paying the original import cost again.

04

Export

Write the result to CSV, or export the current view to Parquet with Pro.

Measured comparison

The difference is keeping the CSV workable.

The comparison below separates streaming a query across a file from opening the data as a spreadsheet project. Same machine, same pinned desktop Chrome, OPFS database, cross-origin isolation, spilling configured and confirmed accepted.

WorkloadDuckDB-WASM 1.33.1Jason
Run a query across the fileNever materialised — streaming scanCompleted14.05 GB in 76 sNot the workload Jason optimises for
Open the file and keep it workableMaterialised — what a spreadsheet actually isFailedOut of memory at 1.76 GB, after 87 s11.78 GB held open, 1B cells

Desktop Chrome. Edge, Firefox, and Chrome on Android are not measured. Hardware, storage speed, column shape, and data types can change the result. Use the benchmark as evidence, not as a guarantee for an untested machine.

Limits and data boundary

Know exactly what happens before choosing a file.

Browser-local
Spreadsheet content is imported, queried, edited, and exported on your device instead of being uploaded to Jason.
Free source-file limit
1,000,000,000 bytes, exactly.
Pro source-file limit
No Jason-enforced limit; the device, browser, and available local storage still set practical limits.
Measured scope
The published large-file results were observed on Jason's development machine in desktop Chrome, not promised for every device.

Can a browser open a 20 GB CSV?

Jason measured one 20.97 GB CSV import in 3.9 minutes and a 111 ms median cold open after the local project existed. That is one documented machine and workload, not a promise that every 20 GB file opens everywhere.

Does Jason upload the CSV?

No. Spreadsheet rows stay in the browser-local data plane. Jason's separate commercial services handle account, payment, and signed licence state, not the source file.

Try the file before changing the workflow.

CSV starts free up to exactly 1,000,000,000 source bytes. If the measured method matters to your decision, inspect the benchmark before opening the file.

Open Jason free Inspect the benchmarks