SQLite Viewer

Open a SQLite database right in your browser — browse its tables and views, run SQL and export the results to CSV. Your file never leaves your device.

Input

.sqlite, .db, .sqlite3, .db3 · SQLite 3 only

Result

Open a database to see its rows here. Results show 200 rows per page; CSV export includes every result row.

Files and results stay on this page only. Writes run on an in-memory copy — your original file is never changed. Close the page to discard everything.

Processed on this device ·

How to use SQLite Viewer

  1. Drop a SQLite 3 file (.sqlite, .db, .sqlite3 or .db3) onto the page, or click the drop area to choose one.
  2. Pick a table or view — the editor fills in SELECT * … LIMIT 1000 — then edit the SQL and click “Run SQL”.
  3. Page through the results 200 rows at a time, or click “Export CSV” to download every result row.

About this tool

SQLite Viewer runs sql.js 1.13.0 — SQLite compiled to WebAssembly — entirely in your browser, inside a Web Worker. Your database file is read into memory on this device and never uploaded. Writes (INSERT, UPDATE, DELETE) run only on the in-memory copy, so the original file is never changed; close the page and everything is discarded. Tables and views are listed from sqlite_schema, and results are shown 200 rows per page.

Frequently asked questions

Are my files uploaded anywhere?

No. Your database file is read into memory in your browser and processed by sql.js 1.13.0, the WebAssembly build of SQLite, running in a Web Worker. Nothing is sent to a server, and this page makes no requests to any outside site.

Which database files can I open?

SQLite 3 main database files with a .sqlite, .db, .sqlite3 or .db3 extension. The file must start with the “SQLite format 3” header — other formats are rejected. This tool reads only the main database file, not the -wal or -shm sidecar files.

My database uses WAL mode. How do I open it?

Export a consistent copy first, then open the copy. For example, with the sqlite3 command-line tool, run VACUUM INTO 'copy.db' on the database, or checkpoint the WAL before copying the file. Opening the main file alone can miss recent changes that still live only in the -wal file.

Can I change the database? Will my edits be saved?

You can run INSERT, UPDATE and DELETE statements, but they only change the in-memory copy — the original file on your device is never modified, and there is no save button. Close the page and all changes are discarded. To keep results, use “Export CSV”.

What are the limits, and what does CSV export contain?

The whole file is loaded into memory, so very large databases are limited by your browser’s available memory and may load slowly or fail. Browsing a table uses SELECT * … LIMIT 1000 by default and results page 200 rows at a time, but “Export CSV” downloads every row of the last query — UTF-8 with a byte-order mark, values quoted, BLOBs shown as hex (X'…') and NULL cells left empty.

Like this tool?

Get Very Useful Tools Pro — one $6/month subscription for all tools: ad-free once ads launch, plus bigger batches and higher limits.

Go Pro — from $6