SQLite Viewer (Open .sqlite / .db Files)

Drop a .sqlite, .db or .sqlite3 file and explore it without installing anything. The viewer lists every table and view, shows each table's columns, types, primary keys and NOT NULL flags, and lets you run arbitrary SQL — SELECT, joins, aggregates, PRAGMA — against an in-memory copy of the database, then export the rows as CSV. It runs the real SQLite engine compiled to WebAssembly (sql.js) entirely in your browser, so your file is never modified and never uploaded.

Drop a .sqlite / .db file here, or click to choose

Opened locally in your browser — nothing is uploaded.

How to use the SQLite Viewer (Open .sqlite / .db Files)

Drag a .sqlite, .db or .sqlite3 file onto the box, or click it to pick one. On first use the SQLite WebAssembly engine (about 0.7 MB) loads once, then the file is read into memory. You'll see a row of buttons — one per table and view in the database. Click any of them to load a SELECT * FROM "table" LIMIT 100 into the query box, display that table's schema (column names, declared types, primary-key and NOT NULL markers) and run the preview immediately.

From there, edit the SQL to do whatever you need — filter with WHERE, JOIN across tables, group and aggregate, or run a PRAGMA — and press Run query (or Ctrl/Cmd+Enter). Results appear in a scrollable table; NULL values and BLOB columns are labelled so you can tell them apart from empty strings. Use Download result CSV to export exactly the rows returned. Every statement runs against an in-memory copy made when you opened the file, so even UPDATE or DELETE only affect that copy — your original file on disk is never touched, and nothing is uploaded. Reload the page to discard the copy.

SQLite database files & why an in-browser viewer helps

SQLite is the most widely deployed database engine in the world — it ships inside every phone, browser, and operating system, and is the default store for countless apps. Unlike a client/server database such as PostgreSQL or MySQL, a SQLite database is a single ordinary file: a .sqlite, .db, or .sqlite3 that holds all the tables, indexes and data in one place. That self-contained design is what makes it perfect for application data, local caches, analytics extracts and test fixtures — but it also means that to peek inside one you normally need the sqlite3 command-line tool, a desktop GUI, or a few lines of Python.

Internally the file is a series of fixed-size pages arranged as B-trees, with a header beginning with the string SQLite format 3 and a special sqlite_master table that catalogues every table, index, view and trigger along with the SQL that created it. Because the entire schema lives in that catalogue, a reader can enumerate the structure of a database immediately on opening it — which is exactly what this viewer does before you run a single query. The data itself is read on demand as you query, so the engine only decodes the pages your query actually touches.

This viewer exists so you can answer everyday questions — what tables are in here, what's the schema, what do the rows look like, how many match this condition — without leaving the browser or installing anything. It runs sql.js, the real SQLite C library compiled to WebAssembly, so it speaks genuine SQL with the same semantics as the command-line tool, not an approximation. Your file is loaded into an in-memory copy and never uploaded, which keeps private or production data on your own machine. For heavy, repeated analytical work you'll still want a local install or DuckDB, but for inspecting a file someone handed you, a browser viewer is the fastest and safest path.

Common use cases

  • Inspect an app's database. Open the SQLite file behind a mobile app, browser profile or desktop tool to see exactly what it stores and how.
  • Explore an unfamiliar file. List the tables and schema of a .db someone sent you, then query it — no sqlite3 install or Python needed.
  • Run ad-hoc SQL. Join tables, aggregate and filter to answer a question, then export the result set as CSV for a ticket or spreadsheet.
  • Check sensitive data privately. Read a production or personal database locally in the browser instead of uploading it to an online converter.

Frequently asked questions

Is my database uploaded anywhere?
No. The file is read entirely in your browser using sql.js — the SQLite engine compiled to WebAssembly — from a local File object. No bytes are sent to any server, which you can confirm in your browser's Network tab. That makes it safe for confidential or production data.

Can I modify the database with UPDATE or DELETE?
You can run those statements, but they only affect an in-memory copy made when you opened the file. Your original file on disk is never changed, and there is no way to write back to it from here. Reload the page to discard the in-memory copy and start fresh.

What file types does it accept?
Any SQLite 3 database, regardless of extension — .sqlite, .sqlite3, .db, .db3 and others all work, because the format is identified by the file's internal header rather than its name. It will not open a .sql text dump, though: that is a script of SQL statements, not a database file. Run a .sql dump through the sqlite3 tool first to create a database.

Will it handle large databases?
The whole file is loaded into memory, so practical limits depend on your device's available RAM — databases up to a few hundred megabytes are usually fine, while multi-gigabyte files are better explored with a native SQLite install or DuckDB. Adding LIMIT to your queries keeps result rendering fast regardless of database size.

Does it support full SQL, including joins and PRAGMA?
Yes. Because it runs the genuine SQLite engine, you get the same SQL dialect as the command-line tool: SELECT with JOINs, GROUP BY and window functions, common table expressions, and PRAGMA statements such as PRAGMA table_info. Queries that return a result set are displayed and can be exported as CSV.
Embed this tool on your site

Free to embed, no attribution required (but appreciated). Paste this where you want the tool to appear: