Convert Parquet to XLSX
Upload a .parquet file and get back a XLSX 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 XLSX
Generated from the converter's own XLSX type mapping — this is what it actually emits, not an example.
| Your data | XLSX 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.
Sheet names and cell types
The workbook is generated rather than exported out of Excel, so every choice in it is one the converter made. The two that show up the moment you open the file are what the sheet is called and what type each cell turned out to be.
- →The sheet takes the table's name cut to 31 characters, which is Excel's own limit for a tab, while the workbook file keeps the name in full - so a long table name is complete in the file name and shortened on the tab inside it.
- →Dates and timestamps become genuine date cells, formatted yyyy-mm-dd and yyyy-mm-dd h:mm:ss, rather than strings that merely look like dates. Sorting and date arithmetic work on them with no conversion step first.
- →A text column of digits stays text: a value like 01234 is written into a string cell, and Excel shows it as it was stored instead of dropping the zeros the way it does when the same data is opened from a CSV.
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 XLSX
- →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 XLSX 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 XLSX?
- Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real XLSX 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.