SQLite Viewer: Browse .sqlite and .db Files in Your Browser
Open SQLite database files, browse tables, and run SQL queries entirely in your browser.
Drop a .sqlite, .db, or .sqlite3 file into the viewer and inspect every table without installing a client. The page loads SQLite compiled to WebAssembly, opens the file from memory, lists every table from sqlite_master, and lets you page through rows or run custom SELECT statements. Files never leave your machine.
SQLite stores each database as a single file. That file packs the schema, the rows, indexes, and even pragma settings into one self-contained blob. Opening it normally means installing the SQLite CLI or a desktop GUI. This viewer skips that step: it loads SQLite compiled to WebAssembly on first use, then opens your file in the same browser tab.
Once a file is open you get the table list from sqlite_master on the left and a paginated grid on the right. Pagination uses LIMIT/OFFSET so even multi-million-row tables stay responsive. The query box accepts any SQLite SQL the engine understands, including CTEs, JSON1 functions, and window functions. Errors come back from the engine verbatim, which makes typo-hunting straightforward.
The WebAssembly runtime is about 1.5 MB and is cached after the first visit. Subsequent uses are instant. Because the database lives in browser memory, your file is never uploaded and the tab can be closed at any time to discard it.
- 1
Open the file
Pick a .sqlite, .db, or .sqlite3 file. The page loads the SQLite WebAssembly engine and reads the bytes locally.
- 2
Browse tables
Click any table in the left panel to view the first 100 rows. Use Prev and Next to page through the rest.
- 3
Run queries
Type SQL in the custom query box and press Run. The result renders as a sortable, scrollable grid below.
Inspect an iPhone or Chrome database
Mobile apps and browsers ship history, contacts, and cache as .sqlite files. Open one and grep through the rows visually.
Debug a local app's database
Local-first apps often write a SQLite file. Open the file straight from a backup folder without leaving the browser.
Audit a database dump
When someone shares a SQLite extract, peek at it without installing anything to verify what is inside.
Test a query before deploying
Run a candidate SELECT against a snapshot of production data to check correctness and rowcount.
Does my database leave the browser?
No. The file is read with the standard File API and passed directly to a WebAssembly build of SQLite running inside the page. There is no upload step and no backend.
How large a database can it handle?
Practical ceiling is roughly a few hundred megabytes, limited by browser memory. Beyond that the tab may run out of memory because the whole file is loaded at once.
Can I run UPDATE or INSERT?
Statements run in memory and the result is shown, but nothing is written back to the original file. If you need to persist changes, export the data with a SELECT and rebuild the file yourself.
Which SQL dialect is supported?
The standard SQLite syntax. JSON1, window functions, CTEs, and FTS5 are all available because the build is sqlite3 compiled to WebAssembly.
Is the WASM file downloaded every visit?
No. The browser caches it after the first download. Subsequent visits load the engine instantly.