How to Use SQLite Viewer
Open a database file
Click Upload Database or drag and drop a .sqlite, .db, .sqlite3, .db3, .s3db, or .sl3 file onto the input area. Files up to 200 MB are supported and loaded entirely in your browser.
Pick a table
Every table in the database is shown as a chip below the toolbar. Click a chip to load that table - the SQL Query box auto-fills with SELECT * FROM "table_name" so you can edit and run it.
Run your query
Edit the SQL Query box and click Run Query, or press Ctrl+Enter (Cmd+Enter on Mac). Any valid SQLite SQL works: SELECT, JOIN, WHERE, GROUP BY, aggregates, CTEs, even INSERT, UPDATE, and DELETE on the working copy.
Copy or export results
Click Copy Results to copy every row as TSV to your clipboard for Excel or Google Sheets. Click Export CSV to download every table you have queried as a single .csv file. Click Clear All to wipe everything.
Frequently Asked Questions
Is my SQLite database uploaded to a server?
▼
No. Your database file never leaves your device. It is opened locally in your browser and queried right there on your computer. Your data, your queries, and your results are never sent anywhere or stored outside this page.
What database file types are supported?
▼
Standard SQLite 3 databases with any of the common extensions: .sqlite, .db, .sqlite3, .db3, .s3db, and .sl3. The file format is the same regardless of extension - SQLite 3's binary format. Files exported by Android, iOS, Firefox, Chrome, Electron apps, Python sqlite3, and any other SQLite-based application all work.
Is there a file size limit?
▼
Yes, 200 MB. Larger files would slow down or crash the page on lower-end devices, so the 200 MB limit keeps performance reasonable across phones, tablets, and desktops. If you need to inspect a larger database, narrow it to a smaller subset on the source machine first and export that.
Can I run any SQL query, or only SELECT?
▼
Any valid SQLite SQL works: SELECT with JOIN, WHERE, GROUP BY, ORDER BY, HAVING, LIMIT, OFFSET, subqueries, CTEs (WITH), aggregate functions (COUNT, SUM, AVG, MIN, MAX), window functions, and even INSERT, UPDATE, DELETE, CREATE, DROP, and ALTER. Modifying queries only change the working copy inside this page - your original file on disk is never touched.
What is the keyboard shortcut for running queries?
▼
Press Ctrl+Enter (or Cmd+Enter on Mac) inside the SQL Query textarea to run the current query without reaching for the Run Query button. The cursor can be anywhere inside the textarea.
How do I see a table's schema or list all tables?
▼
Run SELECT name FROM sqlite_master WHERE type='table' to list every table, or SELECT sql FROM sqlite_master WHERE type='table' to see the full CREATE TABLE statements. For a single table's columns, run PRAGMA table_info('your_table_name').
Will my work be lost if I refresh the page?
▼
Your uploaded database file and the selected table are saved automatically, so after a refresh the database is reloaded and the same table is selected. The text in the SQL Query box, however, is reset to the default SELECT * FROM "table_name" - if you typed a custom query (a JOIN, a WHERE clause, an aggregate), copy it somewhere first if you want to keep it. Click Clear All to wipe the stored database immediately.
Why are only 500 rows displayed when my query returns more?
▼
The Output table preview is capped at 500 rows so a SELECT * against a large table does not freeze the page rendering tens of thousands of rows. The full result is still available - Copy Results copies every row as TSV to your clipboard, and Export CSV downloads every row as a .csv file.
Does Export CSV export all tables or just the current query?
▼
It depends on whether the page has been refreshed. In a fresh session, Export CSV writes whatever queries you have run so far in this session, each prefixed with === table_name === as a section header. After a page refresh, the tool re-reads every table in the database in the background to restore your work, so Export CSV in that case will dump every table in the database. Click Clear All first if you want a clean slate.
Browse SQLite Databases Online Free - No Upload Required
SQLite Viewer is a free online tool for opening and querying SQLite database files without installing any desktop client. Drop a .sqlite, .db, .sqlite3, .db3, .s3db, or .sl3 file in, click through the tables, run any SQL query you like - SELECT, JOIN, GROUP BY, window functions, CTEs - and copy or export the results.
Because every byte of work happens locally on your device, your database file is never uploaded to a server, never logged, and never seen by anyone but you. Refresh the page and your database, selected table, and last query come back automatically. Click Clear All to wipe everything in one click.
Features Explained
Full SQL support
▼
Every query you would write against a normal SQLite database works the same way here - including SELECT, JOIN, WHERE, GROUP BY, HAVING, ORDER BY, LIMIT, OFFSET, subqueries, CTEs (WITH), window functions, and aggregate functions like COUNT, SUM, AVG, MIN, MAX.
Six file extensions accepted
▼
The Upload picker and drag-and-drop both accept .sqlite, .db, .sqlite3, .db3, .s3db, and .sl3. They are all the same SQLite 3 file format - the different extensions just reflect conventions used by Android, iOS, Firefox, Chrome, desktop apps, and various other tools.
200 MB file size limit
▼
Databases up to 200 MB are supported. Larger files would slow down or crash the page on lower-end devices, so the 200 MB cap keeps the experience snappy on phones, tablets, and desktops alike.
One-click table chips
▼
Every table in the loaded database is rendered as a clickable chip below the toolbar. Click a chip to load that table - the SQL Query box is auto-filled with SELECT * FROM "table_name" so you can edit it (add WHERE, change LIMIT) before running.
Editable SQL Query box
▼
The SQL Query textarea accepts any SQL you type. Run Query and Ctrl+Enter both execute exactly what is in the textarea, not a hardcoded query - so you have full freedom to write whatever you need.
Ctrl+Enter to run
▼
Press Ctrl+Enter (Cmd+Enter on Mac) anywhere inside the SQL Query box to run the current query without reaching for the mouse. Ideal for fast iteration.
Modify queries supported
▼
INSERT, UPDATE, DELETE, CREATE, DROP, and ALTER all work - they only change the working copy inside this page. Your original file on disk is never touched. Use Export CSV after modifying if you want to save the new data.
500-row preview cap
▼
The Output table preview is limited to the first 500 rows even when your query returns more, so a SELECT * against a million-row table does not freeze the page. Copy Results and Export CSV always operate on the full untruncated result.
Inline row and column count
▼
When the preview is capped, an inline notice next to the Output heading shows the full row and column count of your query result so you always know what is really in the buffer.
Copy results as TSV
▼
Click Copy Results to copy every row of the current query as tab-separated values to your clipboard. Paste directly into Excel, Google Sheets, Numbers, or any spreadsheet - tabs become columns automatically.
Export CSV with section headers
▼
Click Export CSV to download every table you have queried in this session as a single .csv file, with each table prefixed by a === table_name === section header. The filename is derived from your original database file name.
Drag-and-drop upload
▼
Drag a SQLite database file from your file explorer (Windows Explorer, macOS Finder, Linux file manager) directly onto the input area. The drop zone highlights while you hover so you know it is going to land in the right place.
Persistent across refreshes
▼
Your uploaded database file and the selected table are saved automatically, so a page refresh reloads the same database and re-selects the same table. The SQL Query box is reset to the default SELECT * FROM "table_name" on restore - any custom query you typed is not kept, so copy it elsewhere first if you want to keep it. Only Clear All removes the stored database.
NULL values displayed clearly
▼
NULL values in query results are rendered as italic gray NULL text so you can distinguish them at a glance from empty strings, zero, or the literal text "NULL" stored in a column.
Who Is This Tool For?
Backend Developers
Inspect SQLite files used by Python, Node, Go, or Rust services without firing up sqlite3 CLI or DBeaver.
Mobile Developers
Pull a .db file from an Android emulator or iOS simulator and browse its tables in seconds.
Electron / Desktop App Devs
Debug the local SQLite cache or settings store that ships inside your Electron, Tauri, or Qt app.
Browser Extension Authors
Examine SQLite-backed storage from Firefox profiles, Chrome history, or extension data files.
Data Analysts
Quickly query a SQLite dataset and pull a slice into Excel or Google Sheets via Copy Results (TSV).
Data Scientists
Inspect a Kaggle SQLite dataset or sqlite cache from a Python pipeline before loading it into pandas.
QA Engineers
Verify that your app wrote the right rows during a test run without spinning up a database client.
Database Admins
Spot-check a SQLite snapshot from a production export without installing tools on a fresh machine.
SQL Learners
Practice JOINs, GROUP BY, and window functions against real datasets without installing anything.
Computer Science Students
Open the .sqlite file your professor shipped with the assignment and run your queries in the browser.
Bootcamp Students
Inspect the example databases used in your SQL course without setting up a local environment.
Forensics Investigators
Examine SQLite-backed evidence files (browser history, chat app caches) without altering them on disk.
Security Researchers
Look inside SQLite databases pulled from APK or IPA reverse-engineering work.
Game Developers
Browse the SQLite save files or inventory databases used by Unity, Godot, or custom engines.
IoT Engineers
Inspect logs and telemetry stored in SQLite by edge devices, Raspberry Pis, and embedded controllers.
Privacy-Conscious Users
Audit a SQLite file (browser history, app cache) without uploading it to any cloud tool.
Open Source Contributors
Inspect the SQLite-backed test fixtures or sample data shipped with an open source project.
Technical Writers
Pull example query output from a SQLite dataset for documentation, blog posts, and tutorials.
Product Managers
Run ad-hoc SQL on a SQLite extract from analytics or BI without bothering an engineer.
Support Engineers
Open a customer-supplied SQLite log or diagnostics file to triage an issue without provisioning a database.
Researchers
Browse and query SQLite-backed academic datasets shared as a single self-contained file.
Journalists
Explore SQLite-format public records or FOIA datasets without installing technical tools.
Hobbyists
Peek inside the SQLite databases that power apps you use - Firefox places.sqlite, Signal, Notes, and more.
Anyone curious about a .db file
Drop the file in and find out what tables it has, what is in them, and how big it is - in your browser.
Tips for Using SQLite Viewer
List all tables first
If the table chips are too many to skim, run SELECT name FROM sqlite_master WHERE type='table' ORDER BY name to get a clean alphabetical list.
See the CREATE TABLE statements
Run SELECT sql FROM sqlite_master WHERE type='table' to see the full schema for every table - column names, types, primary keys, indexes.
Inspect a single table's columns
PRAGMA table_info('your_table') returns one row per column with name, type, NOT NULL, default value, and primary key flag.
Use LIMIT for big tables
Even with the 500-row preview cap, very large tables benefit from a tighter LIMIT in the query so the tool does less work: SELECT * FROM big_table LIMIT 100.
Paginate with LIMIT and OFFSET
SELECT * FROM table LIMIT 100 OFFSET 200 fetches rows 201-300. Combine with ORDER BY for stable paging.
Ctrl+Enter saves time
Press Ctrl+Enter (Cmd+Enter on Mac) inside the SQL box to run the query without reaching for the mouse. Great for iterating on a complex JOIN.
Modify the working copy freely
INSERT, UPDATE, DELETE, CREATE, DROP, ALTER all work on the working copy inside this page without ever touching your file on disk. Use Export CSV to save the result.
Quote table names with spaces
If a table name has spaces or reserved words, wrap it in double quotes: SELECT * FROM "My Table". The auto-filled query already does this.
Spot NULL vs empty string
NULL values show up as italic gray NULL in the preview. An empty string shows up blank. Use IS NULL in WHERE clauses to filter exactly.
Copy and paste into a spreadsheet
Copy Results gives you tab-separated text. Paste it into Excel or Google Sheets - tabs become columns automatically with no extra setup.
Export covers every table you queried
Export CSV writes one .csv file containing every table you ran a query against in this session, with === table_name === headers. Useful as a one-shot dump.
Refresh-safe by default
Your loaded file and selected table are saved automatically. A page refresh or accidental tab close still leaves your database loaded - only Clear All wipes it. Custom queries you typed are not kept across refreshes, so copy them elsewhere if you need to keep them.
Supported Input Formats
| Extension | Common Source | Notes |
|---|---|---|
| .sqlite | Generic SQLite databases | The default extension used by most documentation, tutorials, and Kaggle datasets. |
| .db | Mobile apps, Electron apps | Common on Android, iOS, and desktop apps that ship a local database. Same SQLite 3 format inside. |
| .sqlite3 | Python, Ruby on Rails | Often emitted by Python's sqlite3 module and Rails' default development database. |
| .db3 | Older Windows apps, embedded systems | Less common but identical SQLite 3 binary format. Loads exactly like .db. |
| .s3db | SQLite Maestro and similar tools | An older convention used by some Windows desktop SQLite GUIs. |
| .sl3 | Niche applications | Rare extension still in use by a handful of legacy tools. Same SQLite 3 format. |
All six extensions are the same SQLite 3 binary format under the hood. Files up to 200 MB are supported. Pre-SQLite 3 (SQLite 2) files are not supported - they use a different on-disk format.
Privacy & Security
SQLite Viewer runs 100% on your device. Your database file never leaves your computer - it is opened locally and queried right there on this page. Your data, your queries, and your results are never sent anywhere. Even modifying queries (INSERT, UPDATE, DELETE) only change a working copy on this page; your original file on disk is never written.
Your loaded database is saved automatically so you can refresh the page and pick up where you left off. No cookies are used, no analytics track your queries, and no third-party services have access to your data. Click Clear All to wipe the stored database immediately.