SQLite Database Browser

Open a .sqlite, .sqlite3 or .db file and inspect it like a desktop database browser: tables, views, indexes and triggers in a schema list, paged table data with sorting and per-column filters, column details with types, defaults, keys and generated columns, foreign keys and the original CREATE statements. A SQL editor runs any statement against the database, and the health checks run PRAGMA integrity_check and PRAGMA foreign_key_check.

The file is read in your browser and loaded into SQLite compiled to WebAssembly inside a Web Worker. Nothing is uploaded, logged or stored, and the original file is never written. Every change you make with SQL applies to an in-memory working copy, which is marked Modified. Save copy downloads that working copy as a new file named after the original with a -copy suffix. Closing the tab or the database discards it, and SQL history is kept in memory only.

1. 1.Drop a database file, choose Open database, or open a sample database.
2. 2.Pick a table or view in the schema list to page through its rows; sort by a column header or type in a filter.
3. 3.Open Structure, Indexes or Foreign keys to see how the table is defined.
4. 4.Use the SQL editor to run statements (Ctrl or Cmd + Enter), explain a query plan, and export the result as CSV or JSON.
5. 5.Run the health checks, then Save copy to keep your changes.

Files up to 500 MB can be opened; above 100 MB a memory warning is shown, because the browser keeps the file, the working copy and any saved copy in memory. A SQL result returns at most 1,000 rows, long text cells are cut to 10,000 characters for display, and BLOB cells show a 64-byte preview with the full value available for hex, Base64 and download while it stays within a 64 MB budget. Integrity checks list the first 100 problems. A query that runs longer than two minutes stops the engine and discards the working copy.

There is no grid editing: change rows with INSERT, UPDATE or DELETE in the SQL editor. Write-ahead log (-wal) and journal companion files are not read, so changes that were never checkpointed into the main file are missing. Encrypted databases (SQLCipher and similar) cannot be opened, virtual tables that need an extension missing from this build cannot be queried, and there is no persistent workspace, table export or schema dump yet. The tool never connects to a database server.