How to View SQLite Databases Online
- Drop your file — Drag and drop a
.db, .sqlite, .sqlite3, or .db3 file into the upload area, or click to browse.
- Browse tables — The sidebar shows every table and view in your database. Click one to see its rows, 1,000 at a time.
- Run SQL queries — Use the built-in SQL editor to write and run any query. Results appear instantly.
- Edit if you need to — Run
UPDATE, INSERT, DELETE, or ALTER TABLE, then click "Download Database" to save a copy with your changes. Your original file is never altered.
- Export results — Click "Export CSV" to download every row of a table or query result as a CSV file for use in spreadsheets or other tools.
Features
- Instant Table Browsing — Click any table or view to page through its rows, with column types and row counts shown.
- SQL Query Editor — Full SQL support via sql.js (SQLite compiled to WebAssembly). Run
SELECT, PRAGMA, joins, and multi-statement scripts.
- Edit and Save a Copy — Change data or structure with SQL, then download the updated database. Edits happen on a copy in your browser, so the original file stays as it was.
- CSV Export — Export a whole table or query result to CSV with proper quoting and escaping. Ready for Excel, Google Sheets, or other tools.
- Exact Large Numbers — 64-bit integers such as IDs and microsecond timestamps are shown and exported digit for digit, not rounded.
- Large File Support — Handles databases up to 100MB+ depending on your device. Results are shown 1,000 rows per page, so big tables stay fast.
- 100% Client-Side — Powered by sql.js (SQLite in WebAssembly). Your database is never uploaded anywhere.
When Would You Use a SQLite File Viewer?
SQLite databases turn up in more places than most people expect. Here are the most common reasons developers and power users reach for an online viewer:
- Inspecting an app database — iOS and Android apps store local data in SQLite. If you're debugging or auditing an app, dropping the
.db file here lets you see exactly what's stored without firing up Xcode or Android Studio.
- Reading iMessage or WhatsApp exports — Backup tools like iMazing export iMessage history as a
.db file. This viewer lets you browse your messages without installing anything.
- Browsing browser history — Chrome, Firefox, and Safari all store browsing history and bookmarks in SQLite databases. Open
History or places.sqlite to query your own browsing data.
- Checking a development database — Quick sanity-check on a local
.sqlite dev database without leaving your browser or opening a GUI tool.
- Exploring a dataset — Many open datasets, scientific archives, and data exports ship as SQLite files. Drag and drop to explore the schema and run ad-hoc queries before writing any code.
- Auditing a backup — Password managers, note apps, and todo apps often export to SQLite. View the contents before importing elsewhere.
What is SQLite?
SQLite is the world's most widely deployed database engine. It's used by every smartphone, most web browsers, and countless applications. Unlike traditional databases that run as a server, SQLite stores an entire database in a single file — making it perfect for local storage, embedded systems, and data exchange.
The file extensions vary by convention: .db, .sqlite, .sqlite3, and .db3 are all valid SQLite database files. Many apps use their own extension or none at all (Chrome's History file, for example). This viewer checks the file itself, not the name, so it opens any of them.
Privacy & Security
Your database file is loaded directly into your browser's memory using the FileReader API and processed by sql.js, a WebAssembly port of SQLite. No data is ever transmitted to any server. This matters especially when the database contains sensitive information — user records, message history, credentials, or personal data.
Frequently Asked Questions
Is this SQLite viewer free?
Yes, completely free. No sign-up, no hidden fees. Open and browse as many SQLite databases as you need.
Is my database uploaded to a server?
No. Your database is processed entirely in your browser using sql.js (SQLite compiled to WebAssembly). Your data never leaves your device — we never see, store, or have access to your files.
What file types are supported?
Any SQLite database, whatever it is called: .db, .sqlite, .sqlite3, .db3, or a file with another extension or none. The viewer checks the file itself rather than its name. Encrypted databases (such as SQLCipher) cannot be opened.
Can I run custom SQL queries?
Yes. The built-in SQL editor runs any SQLite statement against your database: SELECT, PRAGMA, joins, and also UPDATE, INSERT, and DELETE. Results are displayed in a scrollable table and can be exported to CSV.
Is there a file size limit?
There is no hard limit. The tool runs in your browser, so performance depends on your device's available memory. It comfortably handles databases up to 100MB. Larger files may take longer to load.
Can I modify the database?
Yes. Run UPDATE, INSERT, DELETE, or ALTER TABLE in the SQL editor, then click Download Database to save a copy with your edits. The changes are made to a copy inside your browser, so the original file on your device is never altered. If you close the page without downloading, the edits are discarded.
Why are my newest rows missing?
Some apps keep recent changes in a separate file next to the database, with the same name ending in -wal. Until the app merges that file back in, the main database file does not contain those rows. Close the app (or let it finish saving) and copy the database again.
How do I open a .db file without installing software?
Drop your .db file into the viewer above. It opens directly in your browser using WebAssembly — no software install, no account, no upload. Works in any modern browser on Windows, Mac, Linux, iPhone, or Android.
Is this a free alternative to DB Browser for SQLite?
Yes, for quick jobs. DB Browser for SQLite (DB4S) is a powerful desktop app for designing and editing databases. This tool covers the other side: inspecting an existing SQLite file, running queries, or making a few edits with SQL, without installing anything. If you just need to look inside a .db or .sqlite file or fix a few rows, this is faster.