Convert Apache Parquet files (.parquet) to a CSV table locally - columnar data made readable, no upload, right in your browser.
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
Apache Parquet is a compact, column-oriented binary format from the data and analytics world (Spark, pandas, DuckDB, data lakes). A .parquet file stores its schema inline, packs each column compressed (usually Snappy) and is therefore very space-efficient - but unreadable in a text editor. This tool reads the Parquet content and outputs a flat CSV table you can open in Excel, LibreOffice, Google Sheets or any text editor.
Everything runs entirely locally in your browser (hyparquet, pure JavaScript, no upload, even offline). The tool evaluates the Parquet footer and column pages and supports the common page codecs Snappy, Gzip, Zstd, Brotli and LZ4. So no data is distorted, we emit 64-bit integers beyond the safe JavaScript range as a string, timestamps as ISO 8601 text and raw binary values as base64. Nested fields (lists, structs) appear in a CSV cell as compact JSON.
This is handy when a data pipeline, an export or an analytics job hands you a .parquet file and you just want to peek inside, check it in a spreadsheet or pass it to a tool that speaks CSV. CSV is universal and immediately human-readable. Note: the conversion is one-way (Parquet to CSV); it does not write back to Parquet, and Parquet column compression is lost in flat CSV.
| Input formats | PARQUET |
|---|---|
| Output format | CSV |
| Batch processing | Yes |
| Processing | Locally in your browser (WebAssembly) |
| File upload | None |
Limitations: Parquet files with the codecs Snappy, Gzip, Zstd, Brotli and LZ4 are supported. Encrypted Parquet files are not read. Nested columns (lists/structs) are shown in the cell as JSON. Large 64-bit integers appear as a string (precision), timestamps as ISO 8601, binary values as base64. The conversion is one-way (no CSV back to Parquet). Very large files need memory accordingly.
A compact, column-oriented binary format from the analytics world (Spark, pandas, DuckDB). The schema and compression live inside the file.
No. The conversion happens entirely locally in the browser - even offline.
Snappy (the default), Gzip, Zstd, Brotli and LZ4. Encrypted Parquet files are not read.
64-bit integers beyond the safe JS range are output as a string, timestamps as ISO 8601, binary values as base64.
Not here - this tool is one-way (Parquet to CSV) for inspecting and reusing the data.