Use CSV for a small, shareable extract
Filter and select the needed fields in viewparquet, export CSV, then use Excel's text/CSV import so you can set sensitive column types. This is the route supported by viewparquet today.
Excel workflow
Open a Parquet file in Excel
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, the reliable cross-version route is to create a deliberate CSV extract.
The route available in viewparquet today is CSV: open a local file, optionally filter it with SQL, export CSV, and import that CSV into Excel. viewparquet does not currently create .xlsx files.
Microsoft documents a Parquet connector for supported Power BI, Fabric, Power Apps, and Dynamics hosts, but its current connector matrix marks Parquet as unsupported in Excel. Do not treat the broader Power Query connector guide as proof that an Excel build can import Parquet.
Updated August 21, 2026 · Reproducible checks, limitations, and primary references are included below.
Export CSV for ExcelParquet to Excel via CSV
Open the Parquet file in viewparquet
Drag the .parquet file in. DuckDB-WASM parses it locally; its contents are not uploaded to viewparquet.
Trim to fit Excel if needed
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.
Export to CSV and open in Excel
Click Export → CSV, then open the downloaded file in Excel. Format date and number columns once it is loaded.
Make the CSV-to-Excel handoff explicit
CSV is the available bridge from viewparquet to Excel, but it removes the typed schema Parquet carries. Define the extract, import settings, and verification checks instead of treating the conversion as lossless.
Set types during the Excel import
Use Data → From Text/CSV rather than opening the CSV and accepting every automatic guess. Set identifiers, decimals, dates, and timestamps deliberately, then compare a few sensitive values with the Parquet source.
Keep large analytical work outside the sheet
A worksheet is capped at 1,048,576 rows and 16,384 columns. Aggregate or split deliberately, and keep the Parquet source as the typed system of record instead of treating a truncated sheet as the full dataset.
Check whether the result fits one worksheet
Run this against the result you plan to export, not merely against the original file.
SELECT
count(*) AS rows,
count(*) <= 1048576 AS fits_one_sheet
FROM data;What to expect: The bundled flights sample returns 231,083 and true. Fitting the row limit does not validate cell length, precision, dates, or nested values; import a small sample and compare critical columns before distributing the workbook.
Primary references
These sources support the format and tool behavior described on this page. Product-specific boundaries are checked against the shipped viewer using the claim-verification method.
Common questions
Can Excel open Parquet files natively?
No. Microsoft's current Power Query connector matrix marks Parquet as unsupported in Excel. Convert the needed rows and columns to CSV, then use Excel's text/CSV import and set important column types explicitly.
What is the fastest way to get Parquet data into Excel?
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.
My Parquet file has more rows than Excel allows — what do I do?
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.
Is my data uploaded when I convert Parquet for Excel?
No. For a local file, viewparquet runs DuckDB-WASM in your browser, so reading the Parquet data and writing the CSV happen on your device rather than on a viewparquet server.
Will dates and numbers survive the trip into Excel?
CSV has no native type information, and Excel may reinterpret or lose fidelity in large integers, leading zeros, timezone-qualified timestamps, high-precision decimals, or nested values. Import via Data → From Text/CSV to choose column types, then validate sensitive columns against the Parquet source.
Can viewparquet export .xlsx directly?
No. viewparquet currently exports CSV, JSON Lines, and Parquet, so CSV is the available bridge into Excel; it does not generate a native .xlsx workbook.
Continue with a related task
Try it on your own file
Drop a Parquet, GeoParquet, CSV, or JSON file into viewparquet: browse rows, run DuckDB SQL, and export results in-browser without uploading the dataset to viewparquet. Optional AI sends messages and applicable context directly to the provider you choose; review Settings → AI before use.