Converter
Excel cannot open a .parquet file by double-clicking — it is a compressed, columnar format Excel does not read natively. If a colleague or a pipeline just handed you one, you have two practical options.
The fastest: convert it in your browser. Open the file in viewparquet (processed locally, never uploaded), export to CSV, and open that CSV in Excel — under a minute, no install, works on locked-down corporate Windows machines. Direct .xlsx export from viewparquet is planned.
The built-in alternative: recent Microsoft 365 versions can import Parquet via Power Query (Data → Get Data → From File → From Parquet). It works, but it is a heavier import flow, and older Excel versions do not have it.
Drag the .parquet file in. It parses locally with DuckDB-WASM — nothing is uploaded.
An Excel sheet holds at most 1,048,576 rows. If your file is bigger, run a quick SQL query first — filter with WHERE, or aggregate — and export the result instead of the raw file.
Click Export → CSV, then open the downloaded file in Excel. Format date and number columns once it is loaded.
Not by double-clicking. Microsoft 365 Excel can import Parquet through Power Query (Data → Get Data → From File → From Parquet), but there is no native open. For older Excel versions, convert the file to CSV first.
Convert it to CSV in your browser: open the .parquet file in viewparquet, click Export → CSV, and open the CSV in Excel. No install or upload — the conversion runs locally with DuckDB-WASM.
Excel caps a sheet at 1,048,576 rows. Filter or aggregate in viewparquet’s SQL editor first — for example SELECT * FROM data WHERE year = 2026, or a GROUP BY summary — and export that result. You keep the analysis and Excel gets a file it can open.
No. viewparquet runs entirely in your browser with DuckDB-WASM, so reading the Parquet file and writing the CSV both happen on your machine. Safe for confidential company data.
The values do; the formatting does not. CSV stores everything as text, so after opening it apply Excel column formats (Date, Number, Currency) as needed. Watch out for Excel auto-converting things like long IDs to scientific notation — import via Data → From Text/CSV to control column types.
Not yet — CSV, JSON, and Parquet exports are available today, and CSV is the reliable bridge into Excel. Direct .xlsx export is planned.
Drop a Parquet, GeoParquet, CSV, or JSON file into viewparquet — browse rows, run DuckDB SQL, and export results, all locally in your browser. Nothing is uploaded.