Convert DB file to CSV
Upload a .sqlite or .db or .sqlite3 file and get back a CSV 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 CSV
Generated from the converter's own CSV type mapping — this is what it actually emits, not an example.
| Your data | CSV type |
|---|---|
| Whole number | text (CSV has no types) |
| Decimal (money) | text (CSV has no types) |
| Floating point | text (CSV has no types) |
| True / false | text (CSV has no types) |
| Date | text (CSV has no types) |
| Date and time | text (CSV has no types) |
| Short text | text (CSV has no types) |
| Long text | text (CSV has no types) |
| Binary data | text (CSV has no types) |
Working from a .db file
A .db extension is a habit rather than a format. SQLite uses it, but so do Berkeley DB, thumbnail caches and any desktop application that wanted a generic name, so the first question is what is actually inside yours.
- →A .db is routed to the SQLite reader on its extension alone, so one that is not a SQLite database fails to open rather than converting into something wrong.
- →You can check first: a SQLite file begins with the text "SQLite format 3" in its first 16 bytes, which head -c 16 yourfile.db will show you.
- →DuckDB databases are often saved as .db too, and that one will not open here - rename it to .duckdb or .ddb so it reaches the DuckDB reader instead.
The shape of the CSV files you get
CSV is where the type information stops, so what is left to describe is the file itself: how a row is terminated, which fields are quoted, and how a value that used to have a type is spelled out as characters.
- →Rows end with a carriage return and a line feed, the RFC 4180 ending, while a newline inside a quoted field stays the single character it always was. The encoding is UTF-8 with no byte-order mark in front of it.
- →Quotes go on only where they are needed - a field holding a comma, a double quote or a newline - and a quote inside a field is doubled rather than escaped with a backslash. Every other field is written bare.
- →Decimal values are written digit for digit and never through a floating-point number, so a money column that was exact in the source is still exact in the file. Booleans are written lower case, as true and false, which is the spelling this converter's own reader takes back as a boolean.
Reading DB file
- →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 CSV
- →One file per table, with a header row.
- →NULL is written as an empty field, never the word "None".
- →Binary data is written as hex, which is reversible.
What you get
A ZIP containing <table>.csv. If anything about your data needed a judgement call, a _warnings.txt explains it.
Questions
- Is converting DB file to CSV 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 DB file data keep its types in CSV?
- Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real CSV 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.