SQLite Viewer
Open SQLite database files (.db, .sqlite, .sqlite3) online, browse tables and views, inspect the schema and run SQL queries, right in your browser. See columns, indexes, foreign keys and CREATE statements, export query results to CSV or JSON, edit data with SQL and download the changed database. Files are never uploaded.
What does SQLite Viewer do?
SQLite is the database inside countless apps: mobile apps, browsers (history and cookies), desktop software, IoT devices and many web services. Its data lives in a single file, usually named .db, .sqlite or .sqlite3, but you need a database program to look inside. This tool runs the real SQLite engine in your browser with WebAssembly (sql.js), so you can open a database file on any computer without installing anything.
The file is read into your browser and is not uploaded anywhere. Only the SQLite engine (about 650 KB) is downloaded from the jsDelivr CDN the first time.
How to open a SQLite file
- Drop a
.db,.sqlite,.sqlite3,.db3or.s3dbfile onto the drop area, or click it to select the file. Files without an extension work too: the tool checks the SQLite file header. Click Try sample database to see how it works. - Tables, views, indexes and triggers are listed with the row count of each table. The first table is shown automatically.
- Click a table or view to select it, then use Browse rows, Columns, Indexes and Foreign keys, or open CREATE statement to see how it was defined.
- Write your own SQL in the editor and press Run (or Ctrl+Enter / Cmd+Enter). Table and column names are suggested as you type.
Browse the schema
| Button | What it shows |
|---|---|
| Browse rows | The rows of the table or view (SELECT * FROM table) |
| Columns | Column name, declared type, NOT NULL, default value, primary key position and hidden (generated) columns |
| Indexes | Index name, whether it is unique, how it was created (CREATE INDEX, UNIQUE or PRIMARY KEY), partial indexes and indexed columns |
| Foreign keys | Referenced table and columns, and the ON UPDATE / ON DELETE actions |
| CREATE statement | The original SQL that created the table, view, index or trigger |
| All objects | Every entry of sqlite_schema with its SQL |
| Database info | SQLite version, page size and count, free pages, text encoding, user_version, application_id, journal mode and auto-vacuum |
| Integrity check | Runs PRAGMA integrity_check to find corruption |
Run SQL queries
The editor accepts any SQLite SQL, including several statements separated by semicolons; the result of the last statement is shown. Joins, window functions, common table expressions, JSON functions (json_extract, ->>), PRAGMA statements and date functions all work.
Up to 1,000 rows are shown by default; change Rows shown to see up to 10,000.
Export and edit
- Export the result of a query as CSV, TSV or JSON. All rows of the query are written, not only the rows shown.
- Edit the database with
INSERT,UPDATE,DELETE,CREATE TABLE,ALTER TABLEand so on. Changes are applied to the copy in your browser; click Download database to save the changed.sqlitefile. The original file on your disk is never modified. - Values are shown exactly: large integers keep every digit,
NULLis marked, and BLOBs are shown as hex literals (x'89504e47…').
FAQ
Is my database uploaded?
No. The file is opened by the SQLite engine running in your browser. Nothing is sent to a server.
Which files can I open?
Any SQLite 3 database file, whatever its extension: for example app databases from Android or iOS backups, browser history files, Django and Rails development databases (db.sqlite3), and files created by DB Browser for SQLite. Files that are encrypted (SQLCipher) cannot be opened.
Is there a size limit?
The whole file is loaded into memory, so it depends on your browser and device. Files of a few hundred MB usually work on a desktop computer. Very long queries block the page until they finish.
My file has -wal and -shm files next to it. Does that matter?
Yes. In WAL mode, recent changes may still be in the -wal file and are not visible when you open only the main file. Close the app that uses the database (or run PRAGMA wal_checkpoint) so the changes are written into the main file before opening it.
Are my edits saved?
Changes are kept with the tool (for databases up to 20 MB), so they are still there after a reload, but they are not written back to your original file. Use Download database to save a copy.
How is this different from DB Browser for SQLite?
It needs no installation and works on any computer, including Chromebooks and locked-down work PCs. For heavy editing with forms and a schema designer, a desktop tool is more convenient; for quickly looking inside a file and running queries, this is faster.