Convert Parquet to Excel
Upload a .parquet file and get back a Excel file. Types are preserved rather than flattened to text. Free, no registration, up to 10MB.
Click to upload or drag and drop
CSV, Excel, SQLite, SQL, DBF (max 10 MB)
How your data is typed in Excel
Generated from the converter's own Excel type mapping — this is what it actually emits, not an example.
| Your data | Excel type |
|---|---|
| Whole number | number |
| Decimal (money) | number |
| Floating point | number |
| True / false | boolean |
| Date | date |
| Date and time | date |
| Short text | text |
| Long text | text |
| Binary data | hex text |
Working from a .parquet file
Parquet is the one source here that arrives with a complete, machine-readable schema, so the conversion is a translation rather than an investigation. The interesting question is what Parquet can express that a SQL table cannot.
- →Lists, structs and maps have no scalar equivalent in a relational target, so those columns are carried across as JSON text instead of being exploded into invented columns.
- →Integer widths are kept rather than widened: int8 and int16 become a 16-bit column and int32 a 32-bit one, so the target schema stays as tight as the file was.
- →A Parquet dataset is usually a directory of part files with partition keys encoded in directory names like year=2024/. One file is read, and a column that exists only as a directory name is not inside it.
- →Rows are streamed in batches of 10,000, so a wide file never has to be held in memory all at once.
What opens the converted workbook
Choosing Excel as the target puts no copy of Excel anywhere in the process: the workbook is assembled on the server by a library and handed over finished. What that library writes is what decides how the result behaves when you open it.
- →The output is .xlsx, the OOXML format, and only that. There is no .xls option, so a machine that can open nothing newer than Excel 97-2003 needs the CSV target and a save from there instead.
- →Values are the only thing written. No formulas, no macros, no charts, no column widths, no frozen header row - which is why the first thing most people do with it is widen a column. If Excel opens it in Protected View, that is the mark of the web on a downloaded file rather than anything in the workbook.
- →A conversion is capped at a million rows across all of its tables, and a worksheet holds 1,048,576, so no table can ever arrive too tall for the sheet it is being written into.
Reading Parquet
- →Parquet carries a full schema, so nothing is guessed — types, decimal precision and nullability are read directly.
- →Decimal columns keep their exact precision and scale.
Writing Excel
- →One file per table. Booleans stay booleans and numbers stay numbers.
- →Excel has no fixed-point type, so decimals become numbers — use a database target if exactness matters.
What you get
A ZIP containing <table>.xlsx. If anything about your data needed a judgement call, a _warnings.txt explains it.
Questions
- Is converting Parquet to Excel free?
- Yes. Files up to 10MB convert free with no account. There is a limit of five conversions per day per IP address.
- Will my Parquet data keep its types in Excel?
- Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real Excel types rather than everything becoming text. The mapping table above shows exactly what you get.
- Do you store my file?
- No. The file is written to a temporary directory, converted, and the directory is deleted as soon as your download has been sent.