CanDoYa
All tools
Saved toolsYour favorites

Add to favorites

Saved in this browser only.
Private browser utility / Developer

Free SQLite Viewer Online

Runs entirely in your browser - no upload, no sign-up.

Live workspaceLocal processing

Open a SQLite database

Choose a local database file or load the sample to explore the browser.

Drop a SQLite file here.sqlite, .sqlite3, .db, .db3, or .s3db up to 100.0 MB
No database open. Your file stays on this device.
Share this tool
sqlite browser / browser utility
01 / Overview

What is an online SQLite viewer?

An online SQLite viewer opens a .sqlite or .db file so you can inspect its tables, columns, rows, and schema without installing desktop software. This viewer runs SQLite through WebAssembly in your browser, keeps the database on your device, and lets you run read-only queries or export results as CSV.

02

How to use

  1. 01
    Open the database

    Drop a SQLite file into the page, choose it from your device, or load the built-in sample database.

  2. 02
    Browse its structure

    Select a table or view to inspect its columns, original CREATE statement, and first 500 rows.

  3. 03
    Query or export

    Run a read-only SQLite query, filter the loaded result, then copy or download the result as CSV.

03

Who it's for

  • Developers checking application databases, test fixtures, migration output, or a bug report attachment without installing a database client.
  • Analysts and support teams opening a small SQLite export, filtering a table, and downloading the useful result as CSV.
  • Students and reviewers inspecting table definitions, keys, declared types, views, and query results in one focused workspace.

The browser checks SQLite's standard SQLite format 3 file header before loading the database. It then creates an in-memory copy for the WebAssembly engine, lists user tables and views, and shows a bounded 500-row preview. Search and pagination work on the loaded preview, while the SQL panel handles focused inspection.

Your original file is never rewritten. Each SQL run uses a disposable snapshot with query-only mode enabled, so the database you are browsing stays unchanged even if a query alters its own temporary state.

FAQ

Is my SQLite database uploaded anywhere?

No. The file is read by your browser and passed to a local SQLite WebAssembly engine. CanDoYa does not upload its tables, queries, or exported rows to a database server. The normal page assets still need to load when you first visit the site.

Is this SQLite viewer free?

Yes. You can open a database, browse tables and views, inspect column details, run read-only SQL, copy results, and download CSV files without an account or payment.

How large a SQLite file can I open?

The viewer accepts files up to 100 MB. sql.js keeps an in-memory copy, so practical speed also depends on available device memory and query complexity. For very large databases, use a native SQLite client that can page directly from disk.

Which SQLite file extensions are supported?

You can choose .sqlite, .sqlite3, .db, .db3, and .s3db files. The extension is only an initial filter: the viewer also verifies the official 16-byte SQLite 3 header before it opens the file.

Can a query change my database?

No. Each query starts on a disposable in-memory snapshot with SQLite's query-only setting enabled. Direct writes are blocked, and the snapshot is discarded after the query. The database you are browsing and the original file selected from your device are never rewritten.

Why are recent rows from a WAL database missing?

SQLite write-ahead logging can keep recent transactions in a separate file whose name ends in -wal. A standalone copy of the main database may not include those transactions until SQLite checkpoints them. Copy the database after a clean close or checkpoint when you need its newest state.

How are BLOB and NULL values displayed?

NULL appears as a distinct italic label. Binary BLOB values are rendered as lowercase hexadecimal beginning with 0x, so copied and downloaded results remain readable without pretending that arbitrary bytes are text.