Drop a Parquet file and I'll read its schema and rows — nothing is uploaded.
Parquet Viewer
Open an Apache Parquet file in your browser — the schema, the row count, the compression it was written with, and the rows themselves in a searchable table. No pandas, no notebook, and the file stays on your machine.
Good to know
- Snappy, Gzip, Zstd, Brotli and LZ4 are all read; the file's own schema and writer are shown beside the data.
- Only the rows you are shown are decoded, so a large file opens without reading all of it.
- Nested columns — structs, lists and maps — are shown as JSON in the cell, since a grid has nowhere else to put them.
Your files stay on your machine
This tool runs entirely inside your browser tab. Nothing is uploaded, stored, or sent to a server — close the tab and every trace is gone.
These are the free ones — see the full suiteHow big a file can it take?
There is no upload, so there is no upload limit — but the work happens in this tab, which means your browser’s memory is the budget. Nothing here will refuse a file for being large; a big enough one simply gets slow and, eventually, reloads the tab. The figures below are rules of thumb on a desktop browser, not enforced caps. On a phone or tablet, expect a good deal less.
- Rows are read in a window rather than all at once, so file size matters far less here — the first 50,000 rows are read whatever the file weighs.
- Column count is what binds: a wide analytics table costs memory per column read, and very wide files are slower to open than long ones.
Password-protected PDFs are declined whatever their size — unlock the file first. If a run does die on a long document, splitting it into volumes and working through them one at a time is the reliable way round it.