One-Click SQLite Table & Query Export in WebAssembly
Extracting a single table or joined report from an application .sqlite database shouldn’t require shipping production backups to an untrusted web server or setting up desktop database drivers. Using self-hosted sql.js WebAssembly, this exporter enumerates every user table and view via sqlite_master, displays exact row counts, and builds downloadable RFC-4180 CSV files straight inside your browser tab.
Workflow & Workstation sqlite3 CLI
- Drop a
.sqlite,.db, or.sqlite3file above, or click Try sample .sqlite (3 tables). - Click any one-click Export <table>.csv button for a full table dump, or customize the SQL query (for example joining
issueswithreleases) and click Export Query CSV.
For multi-gigabyte databases on Linux or macOS terminals, run the official CLI directly on disk:
# Export an entire SQLite table with headers via sqlite3 CLI
sqlite3 -header -csv app.db "SELECT * FROM issues;" > issues.csv
# Export joined rows cleanly
sqlite3 -header -csv app.db "SELECT r.version, i.severity, i.title FROM issues i JOIN releases r ON r.id = i.release_id;" > joined.csvTroubleshooting Common Export Issues
- Binary BLOB columns: Non-text BLOB fields are formatted cleanly as
[Uint8Array NB]placeholders so raw binary bytes do not corrupt spreadsheet encoding. - SQLCipher encryption: Encrypted databases will return file is not a database; decrypt first with SQLCipher before loading standard SQLite files here.
Frequently Asked Questions
Can I export a whole SQLite table or only a filtered SQL query?
Both. Click any one-click Export .csv button at the top to dump an entire table immediately, or write a custom SELECT / JOIN query and click Export Query CSV.
Does exporting touch or lock my original SQLite file on disk?
No. Browser export reads a byte copy inside WebAssembly memory and never acquires file locks or writes anything back to disk.
What if recent edits are missing from an exported CSV?
If the source database uses WAL journal mode (.db-wal / .db-shm companion files), copy or checkpoint the database after running PRAGMA wal_checkpoint(TRUNCATE); locally before opening the .db file alone.