EXPLORER

No database open

TABLES & VIEWS 0

Your tables will appear here.

SQL guides

Local files. Private by design.

Workspace

Starting engine…

Storage for new databases

Exercise

Use this exercise’s dataset tables in the explorer. Run previews your query; Check answer compares it with a fresh sample.

Show hint

Show solution

SQLite

Preview limit

Ready when you are

Filter column Condition Value Sort by Order

A FRESH WORKSPACE

Let’s see what’s in your data.

Drop a SQLite database or CSV anywhere here.
Everything stays in this browser.

.db · .sqlite · .sqlite3 · .csv · .sql

Open a database to inspect its schema.

Scroll to zoom · drag background to pan · drag tables to move

100%

Open a database to see its relationships.

Loading SQLite WebAssembly…No data uploads

Export complete data

Export all matching rows, beyond the preview limit. Your files stay on this device.

Format

Report title Orientation

Latin font; 12 columns, 10,000 rows, 200 pages, 8 MiB of values. Unsupported characters or rows too tall for a page fail without a partial report.

Review-only schema and data draft for an empty target database. Keys, constraints (except NOT NULL), defaults, indexes, views and triggers need manual migration. NUMERIC values become text. A mapping report is included. Maximum 100,000 rows / 16 MiB.

Rows Save method

CSV/JSON/Excel/PDF runs one read-only SELECT again against the current database. It exports new results, not the previous preview. JSON preserves NULL and BLOB hex values; large integers are strings. CSV uses empty fields for NULL and escapes formula-like text.

Excel supports 50,000 rows, 256 columns, 500,000 cells and 16 MiB of values. Oversized results fail without saving a partial workbook. Large integers and formula-like values are stored as text.

SQL dumps include ordinary tables, data, indexes, views and triggers. Restore into an empty database with the SQLite CLI; transaction commands cannot run in this workspace. Virtual tables are unsupported. Database export preserves the original SQLite file format.

Direct file saving is used when available. Other browsers have a 64 MiB download limit. Failed or cancelled exports do not save partial data.

Drop your files to start exploring

SQLite · CSV · SQL scripts

Edit row

Edits affect this browser copy. Constraints and triggers apply. INTEGER preserves exact 64-bit values; BLOB accepts hexadecimal pairs. Choose NULL explicitly.

Delete this row, including configured cascades. This cannot be undone here.

New database

Create an empty database, then write SQL or import CSV files.

Database name

The storage mode in the toolbar applies to this database.

Open a local file

Choose a SQLite database, a CSV, or a SQLite SQL script. Select multiple CSVs to import them one at a time.

Database files open as separate workspaces. CSVs import into the current database. SQL scripts open in the editor for you to review and run.

IMPORT CSV

Import a table

Table nameDelimiter First row is a header

Text preserves leading zeros and exact values. Choose numeric types only for columns you want to calculate with.

Saved on this device

Browser storage can be cleared. Export important databases as a backup.

Saved queries

Named queries stay in this browser, including queries saved from temporary workspaces. Opening a query only stages it. Export a backup before clearing browser data.

Name Collection

Find a query

Import JSON

Compare database schemas

The open database is Before. Choose another SQLite file (up to 50 MiB) as After. Compares stored definitions of tables, views, indexes and triggers, including formatting changes. Data is not compared and no migration runs.

After database

Cell inspector

Migration report

The same report is included in the SQL download. Review it before importing into an empty test database.

Query history

Saved workspace queries stay on this device. Temporary-session history lasts until you close this page.

Query plan explorer

Planning only: the selected query was not executed. How to read a plan

Current plan

Baseline

A scan is not always a problem. Plans depend on schema, statistics and SQLite version. Baselines stay in memory until cleared or the database changes.