What This Browser SQLite Workbench Covers
Desktop applications, Electron caches, mobile backups, Playwright trace artifacts, and embedded analytics jobs all package structured state inside single-file SQLite 3 databases (.sqlite, .sqlite3,.db). Inspecting a database handed over in a bug report normally requires installing a native GUI client or opening a shell.
This page compiles standard SQLite 3 to self-hosted WebAssembly (sql-wasm.wasm) and executes entirely inside your browser memory. As soon as you pick a database or click Try sample .sqlite (3 tables), it enumerates user tables and views from sqlite_master, counts rows, inspects declared column types and primary keys via PRAGMA table_info, and lets you execute arbitrary read queries—including multi-tableJOINs, CTEs, and window functions—with one-click CSV or JSON export.
Step-by-Step Usage & Workstation CLI Equivalents
- Load a database: Drop any unencrypted
.sqlite,.db, or.sqlite3file above. Row counts and the first table populate automatically. - Switch tables or write custom SQL: Click any table chip to preview its schema and first 50 rows, or write a join across tables (for example joining
issueswithreleasesin the QA sample database). - Export clean slices: Click Export CSV or Export JSON to save the current query result directly from browser memory.
When working inside a terminal over SSH or inspecting multi-gigabyte databases larger than browser RAM, the official sqlite3 command-line tool remains indispensable:
# List tables and print schema definitions in terminal
sqlite3 app.db ".tables" ".schema"
# Export one query straight to CSV from disk
sqlite3 -header -csv app.db "SELECT * FROM issues WHERE status = 'open';" > open_issues.csvCommon Pitfalls & Troubleshooting
- Write-Ahead Logging (
-wal/-shm) files: Modern apps often enablePRAGMA journal_mode=WAL;. If you copy onlyapp.dbwhile the writer is still open, recent writes sitting inapp.db-walwill not appear in a single-file browser viewer until a checkpoint completes. file is not a databaseerror: Verify the file is not SQLCipher-encrypted, gzipped, or an HTML error page saved with a.dbextension. Every valid SQLite 3 file starts with the ASCII stringSQLite format 3.- Large BLOB columns: Embedded binaries stored as
Uint8ArrayBLOBs are rendered as a compact byte-length marker ([Uint8Array NB]) so binary payloads never flood or lock up the DOM table.
Frequently Asked Questions
Which SQLite file extensions can I open here?
You can drop .sqlite, .sqlite3, .db, or .s3db files. SQLite identifies databases by their internal 16-byte "SQLite format 3" file header regardless of extension.
Does running DELETE or UPDATE SQL modify my original file on disk?
No. Your browser loads a read-only byte copy into WebAssembly heap memory. Even if you execute temporary DDL or UPDATE queries inside the editor, your original local file on disk remains untouched.
Why are some recent rows missing when opening a WAL-mode database?
If an application uses Write-Ahead Logging (WAL) and has not yet checkpointed, recent transactions still live in the sibling .db-wal file rather than the main .db file. Run PRAGMA wal_checkpoint(TRUNCATE); locally before copying a single .db file.
Are encrypted SQLCipher databases supported?
No. Standard unencrypted SQLite 3 databases open immediately, whereas SQLCipher-encrypted files will report "file is not a database" because the header bytes are ciphered.