Excel workflow
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 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.
The Microsoft alternative is Power Query. Supported Microsoft 365 and Power Query builds can expose a Parquet connector under Data → Get Data; availability and menu labels vary by Excel version and platform.
Drag the .parquet file in. DuckDB-WASM parses it locally; its contents are not uploaded to viewparquet.
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. Some supported Microsoft 365 and Power Query builds can import Parquet through Data → Get Data, but connector availability varies; when it is unavailable, export CSV and import the CSV instead.
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. 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.
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.
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.
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.