SQLite Viewer

Open SQLite .db and .sqlite files in your browser. Browse tables, schema and indexes, run SQL, and export results to CSV. The tool does not upload the database.

  • Runs in your browser
  • Tool input is not uploaded to ZeroTool servers
  • Free · No Sign-Up
Open one SQLite 3 file up to 100 MB (100 × 1024 × 1024 bytes). Only the main file is read: encrypted databases and -wal or -journal sidecars are not opened. The first 100 bytes are checked before the engine loads.

The SQLite engine loads from this site after the file header check. Database files stay on your device.

Drop a SQLite file here

.db · .sqlite · .sqlite3 — up to 100 MB · or click to choose · never uploaded

Examples, details and FAQ Worked examples, how it compares with other tools, and answers to common questions.

When a browser SQLite viewer is the right tool

  • Checking what an agent or script wrote. A coding agent ran a migration or seeded test data. Open the file and look at the rows before you trust it.
  • Reading app data. Browsers, mobile apps, Electron apps and many CLIs keep their state in SQLite. Pull the file and read it without installing a desktop client.
  • Handing data to someone else. Run a query, export the result as CSV, and send the CSV — the database itself stays with you.

What the viewer shows

ValueHow it appearsIn CSV
NULLA muted NULL marker, so it cannot be confused with an empty stringEmpty field
BLOBByte length and the first 16 bytes in hexFull content as uppercase hex
Long textTruncated in the cell; hover to see moreFull value, quoted per RFC 4180
NumbersRight-alignedAs stored

Query results render the first 1,000 rows so the page stays responsive. The CSV export always contains every row.

Examples

A column that holds two types. SQLite stores the type with each value, not with the column, so a DATETIME column can hold ISO text in one row and a Unix timestamp in another (Datatypes In SQLite). Ask SQLite directly:

SELECT typeof(created_at) AS storage_class, COUNT(*)
FROM orders GROUP BY 1;

On a table with the rows '2026-09-01T10:00:00Z', 1759312800 and '2026-09-02', the result grid shows integer | 1 and text | 2: two code paths write the column in different formats. A table whose CREATE statement ends in STRICT (SQLite 3.37.0 and later) rejects such writes with cannot store TEXT value in INT column.

Trying a cleanup before running it for real. Statements run on the in-memory copy, so you can see what a delete leaves behind:

DELETE FROM sessions WHERE expires_at < unixepoch();
SELECT COUNT(*) AS remaining FROM sessions;

The grid shows the last statement that returns columns. Foreign key enforcement is off on a new connection (PRAGMA foreign_keys returns 0), so run PRAGMA foreign_keys = ON; first if you want ON DELETE CASCADE to fire.

Errors come from SQLite itself. A typo shows SQL error: near "SELEC": syntax error. A full-text table shows no such module: fts5, because the sql.js 1.14.2 build (SQLite 3.49.1) does not include the FTS5 or R-Tree modules; its row count shows — and the rest of the database stays browsable. FTS5 keeps its text in ordinary shadow tables such as notes_fts_content, which you can read.

CSV keeps text valid. A BLOB holding a PNG signature shows as BLOB · 8 B · 89504E470D0A1A0A in the grid and exports as 89504E470D0A1A0A. NULL and the empty string both export as an empty field; select COALESCE(col, '<null>') before exporting if the difference matters.

When the file does not show what you expect

  • Recent rows are missing. In WAL mode, committed changes sit in app.db-wal until a checkpoint moves them into the main file. Header bytes 18 and 19 are both 2 for a WAL database (file format). Close the app that writes to it and run sqlite3 app.db "PRAGMA wal_checkpoint(TRUNCATE);".
  • "Not a SQLite 3 database". The first 16 bytes must be SQLite format 3 followed by a nul byte. Check with head -c 16 app.db | xxd. SQLCipher stores a random salt there, so encrypted files fail this check.
  • The file is over 100 MB. Take a smaller extract first: sqlite3 big.db "ATTACH 'small.db' AS s; CREATE TABLE s.orders AS SELECT * FROM orders WHERE created_at >= '2026-09-01';", then open small.db.
  • Copying a database that is in use. cp can catch a half-written file. sqlite3 app.db "VACUUM INTO 'snapshot.db'" (SQLite 3.27.0 and later, VACUUM) writes a consistent single-file copy that includes committed WAL content.

How it works

The page first reads only the first 100 bytes of the file and checks the SQLite header. The SQLite engine — sql.js, about 340 KB compressed — is fetched only after that check passes, so opening the page costs nothing extra and a wrong file never triggers the download. The full file is then passed to SQLite as an in-memory database. Table structure comes from pragma_table_info and pragma_index_list, and every table and column name is quoted, so names with spaces, quotes or non-Latin characters work.

Scope

This tool opens one SQLite 3 file up to 100 MB and reads it. It does not save changes back to the file, does not read -wal or -journal sidecar files, and does not open encrypted databases. Extension-backed virtual tables such as SpatiaLite geometry tables, FTS5 full-text indexes and R-Tree indexes show their SQLite error instead of rows. For any of those cases, the sqlite3 command-line shell or DB Browser for SQLite on your own machine is the right tool.

FAQ

Is my database file uploaded?

No. The file is read with the browser File API and opened by SQLite compiled to WebAssembly (sql.js) inside the page. It is not uploaded, and the tool does not save the file or your queries; stored values for this page are deleted each time it loads. A database is usually full of user records, tokens or production data that should not end up in a chat window or on someone else's server, so this page loads no analytics or ad scripts.

If I run UPDATE or DELETE, does it change my file?

No. The browser has no write access to the file you picked. SQLite runs on an in-memory copy, so INSERT, UPDATE, DELETE and CREATE work and the table list refreshes, but the changes disappear when you reload or open another file. The tool does not offer a download of the edited copy. To change a file on disk, use the sqlite3 command-line shell or DB Browser for SQLite.

How large a database can I open?

Up to 100 MB. The whole file is held in memory twice while it is open — once as the file buffer and once inside the SQLite engine — so larger files make browser tabs unstable. For bigger databases run sqlite3 app.db locally.

Why does it say my file is not a SQLite database?

Every SQLite 3 file starts with the 16-byte header SQLite format 3. If that header is missing, the file is something else — or it is encrypted. SQLCipher and the SQLite Encryption Extension encrypt the header too, so encrypted databases cannot be opened here. Decrypt them with sqlcipher or open them in DB Browser for SQLite, which supports SQLCipher.

Recent rows are missing. Why?

The database is probably in WAL mode and the newest writes still sit in the app.db-wal file next to it. Only the main file is read. Close the application that writes to it, or run sqlite3 app.db "PRAGMA wal_checkpoint(TRUNCATE);", and open the file again.