Convert SQLite3 to Excel
Upload a .sqlite or .db or .sqlite3 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 .sqlite3 file
The 3 in .sqlite3 is the version of the file format, not of your file, and it has not changed since 2004. A .sqlite3 and a .sqlite are the same kind of thing under two naming habits, and both are read the same way.
- →db.sqlite3 is Django's default database name, and a Django database converts whole: django_migrations, auth_user and django_session are ordinary tables here and come across with everything else.
- →Nothing is filtered on the way through, so if you only want the application tables it is easier to drop the framework ones in the target database after loading.
- →The extension does not change how the file is read - it only has to be one the uploader recognises, and .sqlite, .sqlite3 and .db all are.
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 SQLite3
- →Declared types, primary keys, NOT NULL constraints and blobs all carry through.
- →SQLite reports INTEGER PRIMARY KEY as nullable because it aliases the rowid; the conversion corrects that.
- →SQLite type affinity is loose, so a NUMERIC column with no declared scale is given room for decimals rather than being rounded to whole numbers.
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 SQLite3 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 SQLite3 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.