SQLite Viewer
Open a .sqlite, .db or .sqlite3 file and look inside it. Browse tables, read the schema, run SELECT queries. Your database never leaves your browser.
By Kevin Piacentini, Software Engineer & Founder of FluentDB.sqlite, .db, .sqlite3, or no extension at all. Your file stays in your browser and is never uploaded.
Runs SQLite itself in your browser via WebAssembly. No upload, no account, and read-only by design.
How to open a SQLite file
- 1Drag a SQLite file onto the box above, or click Choose a file. Any .sqlite, .db, .sqlite3, or extensionless SQLite file works.
- 2Pick a table from the list on the left to browse its rows, page through them, and export the whole table to CSV.
- 3Switch to Schema to read the CREATE statement, or Query to run your own SELECT. Everything happens in your browser, so the file is never uploaded.
.db, .sqlite, .sqlite3: what is the difference?
None of them, in practice. SQLite has no required file extension, so the same database can be named any of these and behave identically. This is the single most common reason people think they cannot open a file.
The most explicit naming, common in tooling that wants the format to be obvious. Nothing about the file differs from the others.
The most common extension in the wild, used by iOS and Android apps, Electron apps, and plenty of desktop software. A .db file is usually SQLite, but not always: the extension is generic, so some programs use it for their own formats.
Perfectly normal. SQLite does not care what a file is called. If the first 16 bytes read "SQLite format 3", it is a SQLite database.
If a file will not open here, it is most likely not a SQLite database at all. Some applications use .db for their own private format, and no SQLite tool will read those.
Making sense of a database you did not build
Most people open a SQLite file because they want to understand something inside an app they did not write. A few things make that much faster.
The Schema tab shows the exact CREATE TABLE statement, including primary keys, foreign keys, and CHECK constraints. It tells you how the tables relate before you start guessing from column names.
SQLite stores its own catalogue in a table called sqlite_master. Every table, view, index, and trigger is a row in it. The table list on the left is simply a query against it, filtered to skip SQLite's internal objects.
SQLite uses dynamic typing, so a column declared INTEGER can hold text. If a value looks wrong for its column, that is not a bug in the viewer. It is what is actually stored.
Empty cells are shown as a greyed NULL so you can tell a genuine NULL apart from an empty string. The difference matters as soon as you write a WHERE clause.
Two things come up often enough to have their own guides: listing tables and describing a schema (SHOW TABLES and DESCRIBE do not exist in SQLite), and working with JSON in SQLite, which has no dedicated column type.
Why in-browser matters here
A SQLite file is not a query, it is the whole database. Uploading one to a website means handing over every row in it, which is a different proposition from pasting a snippet of SQL somewhere. Plenty of online SQLite viewers do exactly that, because running SQLite on a server is the easy way to build one.
This tool compiles SQLite to WebAssembly and runs it inside your browser tab instead. The file is read from your disk into memory on your own machine. There is no upload endpoint, and after the page loads you can disconnect from the network entirely and it will keep working.
If you want to talk to your database, use FluentDB
This viewer reads. FluentDB is the native Mac app that edits rows, opens encrypted SQLite, connects to PostgreSQL, MySQL and SQL Server too, and has an AI co-pilot that writes the SQL against your real schema when you ask in plain English.
Download FluentDB for MacOr read how it compares as a SQLite browser for Mac, against DB Browser for SQLite, and against SQLiteStudio, now called Letos.
SQLite viewer FAQ
Is this SQLite viewer private? Is my database uploaded?
No, nothing is uploaded. The viewer runs SQLite itself inside your browser using WebAssembly, so your file is read locally and never sent to a server. Most online SQLite viewers upload your database to process it, which is a real problem if it contains customer data. This one does not.
How do I open a .db file?
Drag it onto the box at the top of this page, or click Choose a file. A .db file is usually a SQLite database, and the .sqlite, .db, and .sqlite3 extensions are all the same format, so there is no need to rename anything.
Can I edit data with this tool?
No. This viewer is deliberately read-only: it runs SELECT queries and refuses anything that writes. That keeps it safe to point at a copy of a production database. If you want to edit rows, use a desktop client such as FluentDB, DB Browser for SQLite, or Letos.
Is there a file size limit?
There is no hard limit, but the database is loaded into your browser's memory, so very large files will be slow or will fail. Anything up to a few hundred megabytes is usually fine on a modern machine. Files above roughly 300MB are rejected with a message rather than crashing your tab.
How is this different from DB Browser for SQLite?
DB Browser for SQLite is a free desktop application that you install, and it can edit data as well as read it. This is a browser tool with nothing to install, which is useful when you just want to look inside a file quickly. They serve different moments, and DB Browser for SQLite is the more capable of the two.
Does it work offline?
Yes, once the page has loaded. The SQLite engine is downloaded to your browser the first time you open a file, and after that no network connection is needed to browse a database.
Is it free?
Yes, free with no account and no limits. It is made by FluentDB, a native macOS database client. If you want to edit data, work across PostgreSQL, MySQL, and SQL Server, or have an AI write your SQL, that is the paid app.