How do I convert Parquet to CSV without Python or pandas?
Use a browser-based converter. Open a local .parquet file in viewparquet and click Export → CSV — no Python, pandas, or install needed, and the file contents are not uploaded to viewparquet.
Converter
Convert Parquet to CSV
Parquet is great for storage and analytics, but sooner or later someone needs the data in CSV — for Excel, a legacy tool, or a colleague who just wants a spreadsheet-friendly file.
viewparquet converts Parquet to CSV in your browser. DuckDB-WASM reads a local file and generates the CSV on your device, without uploading the dataset to viewparquet. You can run SQL first to choose columns, filter rows, or aggregate the data, then export the result you need.
How to convert
Open the Parquet file
Drag your .parquet file into viewparquet, or open it from S3 or a URL.
Optionally shape the data with SQL
Skip this for a full-file export. Or write a query — SELECT the columns you need, add a WHERE clause, or LIMIT the rows — and export the result instead of the whole file.
Export to CSV
Click Export and choose CSV. The file is written locally by DuckDB and downloads straight from your browser.
Common questions
Is the Parquet file uploaded to a server during conversion?
No. For a local file, viewparquet runs DuckDB compiled to WebAssembly inside your browser tab, so reading the Parquet file and writing the CSV happen on your device rather than on a viewparquet server.
Can I convert only some columns or rows to CSV?
Yes. Run a SQL query first — for example SELECT id, name, amount FROM data WHERE amount > 0 — and export the query result. This produces a smaller, cleaner CSV than converting the whole file.
Will I lose data types when converting Parquet to CSV?
CSV is plain text with no type information, so types are represented as text: timestamps and decimals are written out as strings and must be re-parsed by whatever reads the CSV. If a downstream tool supports Parquet or JSON directly, prefer those to keep types intact.
How do I convert Parquet to CSV from the command line instead?
With the DuckDB CLI it is one statement: COPY (SELECT * FROM read_parquet('data.parquet')) TO 'data.csv' (FORMAT CSV, HEADER). A browser viewer can be convenient for one-off conversions; the CLI is better for scripts.
Is there a file size limit?
There is no fixed published cap. The practical limit depends on browser memory, the Parquet layout, column types, and export size; filtering or aggregating with SQL before export can substantially reduce the work.
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.