DATABASE TOOLS / SQLITE

Local Database Explorer

Inspect, query, edit and export SQLite databases — privately in your browser.

Start with a SQLite fileChoose a database, or open a sample to explore tables, run queries and test edits. Changes are never written to the original file automatically.

DATABASENo file opened

TABLES & VIEWS—

FILE SIZE—

CHANGES0 · Unsaved

Ready

Table browser

Open a SQLite database to inspect its contents

Sort by

Choose a table from the left to browse its data.

SQL console

Read-only by default. Writes require explicit authorization.

SQL query

Run a query to view its results.

All processing stays local after the SQLite engine loads.

Explore SQLite without uploading a database

01 / Open

Choose a SQLite database file up to 32 MiB. Inspect tables, columns, and indexes.

02 / Explore & edit

Browse records, search, run SQL, or edit supported cells using parameterized statements.

03 / Export safely

Download your updated SQLite file, CSV/JSON table extracts, or a schema comparison report.

Using Local Database Explorer

Inspect a local SQLite database with the supplied browser Worker and sql.js files, browse tables, run bounded SQL, edit supported cells, and export a modified database or extracts.

Workflow

Open the supplied sample or a SQLite file up to 32 MiB, then inspect its tables, columns, and indexes.

Browse or search records, run a query such as SELECT name FROM sqlite_schema WHERE type = 'table';, and edit only supported cells.

Review a schema comparison or table extract, then explicitly export the modified database if you need edits to persist.

Worked example

Open the included sample database, inspect the table and index list, and run SELECT name FROM sqlite_schema WHERE type = 'table'; to list its tables. Make a supported cell edit only if needed, then export the modified database; the original file is not changed.

Limits and data handling

The browser uses supplied local sql.js 1.13.0 JavaScript/WASM and a Worker; WebAssembly and Worker support are required. The database size limit is 32 MiB and queries/exports have row and time limits. SQLCipher, WAL sidecars, external extensions, attached databases, and BLOB editing are unsupported. Integer keys beyond JavaScript safe range cannot be edited. Changes are ephemeral until exported. Runtime acceptance and browser-origin behavior remain unverified.

Frequently asked questions

Does editing change the original SQLite file automatically?

No. Edits are in the workspace until you export the modified database. The original file is left untouched.

Can it open SQLCipher or edit BLOB values?

No. SQLCipher databases, external extensions, attached databases, and BLOB editing are unsupported.