Convert SQL dump file to Excel
Upload a .sql 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 SQL dump file
A dump is a schema and its data written out by a database's own export tool, in that tool's own flavour of SQL. Which flavour it is has to be established before a single line of it can be parsed correctly.
- →The dialect is decided by scanning the first 5,000 characters for tell-tale syntax: AUTO_INCREMENT or ENGINE= means MySQL, SERIAL means PostgreSQL, IDENTITY( or NVARCHAR means SQL Server.
- →If your dump opens with thousands of characters of comments and SET statements before the first CREATE TABLE, that scan has nothing to go on and falls back to MySQL. Trimming the preamble fixes it.
- →Dump tools often gzip their output. A .sql.gz is not a recognised extension, so decompress it before uploading.
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 SQL dump file
- →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 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 SQL dump file 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 SQL dump file 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.