Convert SQL dump to XLSX
Upload a .sql 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 .sql file
A .sql file is only text containing statements, so what you get out depends entirely on which statements are in it. Schema and data both have to be present for the result to be a database rather than an empty shell.
- →Four things are used: CREATE TABLE, ALTER TABLE ... PRIMARY KEY, INSERT and COPY. Views, triggers, stored procedures, indexes and GRANT statements are read past rather than converted.
- →A file with INSERTs but no CREATE TABLE still produces its rows, with a warning that the columns are unnamed - the file never said what they were called.
- →A file with neither comes back with "No CREATE TABLE or INSERT statements were found", which usually means the schema lives in a second file.
- →psql meta-commands - the lines beginning with a backslash, like \connect - are client directives rather than SQL, and are skipped before parsing.
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 SQL dump
- →Parsed with a real SQL parser, not regular expressions, so a value containing a closing parenthesis or a semicolon cannot split a row in half.
- →CREATE TABLE types, primary keys, NOT NULL and AUTO_INCREMENT are all read from the dump.
- →The source dialect is detected from the dump itself — MySQL, PostgreSQL and SQL Server dumps all parse.
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 SQL dump 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 SQL dump 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.