ByteScope

SQLite Viewer

Browse tables, run queries, build them visually — your database stays on your machine.

Your files never leave your browser — all processing is local.

Drop a SQLite database

or click to browse — .db / .sqlite / .sqlite3 / .db3 · opened in your browser, never uploaded

About this tool

Drop a .db, .sqlite or .sqlite3 file and browse it immediately: every table with its row count, views and indexes, the full schema DDL per table, and a paginated data grid with column sorting and quick filters. A database is about the most sensitive file there is — this viewer runs SQLite compiled to WebAssembly inside your browser, so the file is never uploaded anywhere. Pull a database off a phone backup, an app's data folder or a server and inspect it without it touching the network.

Query it two ways. The SQL editor gives you the real thing — syntax highlighting, friendly error messages, query history, read-only by default with an explicit switch to enable writes and export the modified database. The visual query builder needs no SQL at all: pick a table, tick columns, stack filter conditions from dropdowns, choose sorting and a row limit — and watch the generated SQL update live as you build, which doubles as a gentle SQL tutorial. One click moves the built query into the editor for hand-tuning.

Queries you build can be saved (named, stored only in your browser, keyed to the database's schema so they reappear next time you open the same file), and a template library covers the everyday asks: first 100 rows, group-and-count top N, date-range filter, text search across a table, duplicate finder, NULL-ratio check. Results export to CSV or JSON; BLOB columns are type-sniffed and image blobs render as thumbnails. WAL sidecar files, SQLCipher-encrypted databases and corrupt files each get an honest, specific message instead of a crash.

Frequently asked questions

Is my database uploaded anywhere?
No — and for databases that matters more than for any other file type. SQLite runs as WebAssembly inside your browser; the file is opened in memory on your machine, queries execute locally, and nothing is transmitted. You can disconnect from the internet after loading the page and everything keeps working.
I don't know SQL — can I still use it?
Yes. The visual query builder works entirely with dropdowns and checkboxes: choose a table, pick columns, add filters like status = active, sort, limit — done. The generated SQL is shown live as you click, so you learn the syntax as a side effect, and templates handle common jobs like finding duplicates with two clicks.
Can I edit data and save the changes?
The viewer opens read-only by default so you can't damage anything by accident. Flip the "allow writes" switch and you can run UPDATE/INSERT/DELETE, then download the modified database as a new .db file — the original on your disk is never touched in place.
Why does it say my database is encrypted or missing recent data?
SQLCipher-encrypted databases can't be opened (the encryption isn't part of standard SQLite) — the viewer detects and says so. A -wal sidecar file next to your .db holds recent un-merged writes; if it exists, the viewer warns that the newest rows may be missing and suggests checkpointing the database first.
How big a database can it handle?
The MVP loads the file into memory, so a few hundred MB is comfortable on a typical machine — a warning appears above 300 MB. The grid uses virtual scrolling and paginated queries, so large tables browse smoothly either way.