SQLite is the world's most deployed database — it's inside phone apps, browsers, IoT devices, and countless tools. Which is why mystery .db, .sqlite, and .db3 files keep turning up. Opening one normally means installing the sqlite3 command line tool or a database browser app.
There's a faster way: SQLite itself, compiled to WebAssembly, running in your browser tab. Real SQLite, zero installation, and the file never leaves your machine.
See What's Inside
Drop the file into the SQLite viewer and you get the full schema — every table with its complete CREATE TABLE definition, columns, types, and constraints. That's usually all you need to know whether a file is worth digging into.
Export the Data
To a spreadsheet
The SQLite to CSV converter exports table data ready for Excel or Google Sheets. One table gives you a single .csv; a multi-table database downloads as a ZIP with one CSV per table, so nothing gets mashed together.
To code
The SQLite to JSON converter produces one JSON file keyed by table name:
{
"users": [ { "id": 1, "name": "Ada" }, ... ],
"orders": [ { "id": 100, "user_id": 1 }, ... ]
}Perfect for scripts, notebooks, or feeding into another system.
Why In-Browser Matters for Databases
Databases are exactly the kind of file you shouldn't paste into a random website: they contain application data, user records, sometimes credentials. These tools run SQLite via WebAssembly on your own device — there's no server-side processing and no upload. You can verify it: the page works even offline once loaded.
Practical Notes
- Supported extensions: .sqlite, .sqlite3, .db, .db3 (any SQLite 3 file)
- Exports include tables only — views, indexes, and triggers are schema-level and show up in the viewer instead
- Processing uses your browser's memory; typical app databases convert in seconds, multi-hundred-MB files depend on your hardware