Does running SQL change my original file?

No. The browser works on an in-memory copy. Save database downloads a new file. Opening another database, closing the page, or stopping the worker discards changes that have not been exported.

Can a query freeze the website?

SQL executes in a worker. Stop worker terminates it, and a 15-second timeout also stops it. This resets the database workspace; reopen your source file to continue. Very large files can still consume significant memory.

Which features and formats are supported?

Unencrypted SQLite 3 databases up to 50 MB are supported. There is no extension loading, encrypted database support or remote server connection. Results are limited to 5,000 rows across at most 25 statements; later statements are not run if the display limit is reached.

What do result exports contain?

CSV contains displayed values with spreadsheet formula protection. JSON preserves columns, row arrays and NULL values. BLOB cells are represented by their byte counts rather than exported binary contents. PDF is an image-based reading copy limited to 500 rows.

SQLite Database Studio

Open SQLite files, explore tables and views, run SQL locally, and export databases or query results.

Database explorer

No database open0 tables · 0 views

Tables and views appear here.

SQL editor

Read-only

Query

SELECT * FROM inventory;

Results

Run a query or select a table to explore its records.

Open a SQLite file, create a database, or load the example.

SQLite runs locally using sql.js. No server connection, automatic saving, encrypted databases or extension loading. File limit: 50 MB; query limit: 15 seconds / 25 statements / 5,000 displayed rows. Stopping or timing out resets the workspace. BLOB values are shown as size labels; JSON preserves SQL NULL values. PDF is an image-based reading copy limited to 500 rows. Read-only is an editing guard, not a sandbox for hostile SQL.

Loading Tool…

What Is the SQLite Database Studio?

An in-browser SQLite workspace with an object explorer, SQL editor, recent query history and tabular results. The SQLite engine runs in a separate worker using locally served sql.js and WebAssembly assets. Database files stay on your device and queries do not connect to an external database server.

How It Works

Open an unencrypted SQLite 3 file, create an empty database, or load the example. Click a table or view to inspect rows. Edit SQL and choose Run SQL, or press Control/Command plus Enter. Read-only starts enabled; disable it deliberately to edit your in-memory copy. Save database downloads the edited SQLite file. Results can be exported as CSV, JSON or PDF.

When to Use It

Use it to inspect small application databases, learn SQL, review an exported dataset, or make controlled edits to a local copy. It is not a production database server, cloud database connector or a replacement for a full backup workflow.

Frequently Asked Questions

Does running SQL change my original file?: No. The browser works on an in-memory copy. Save database downloads a new file. Opening another database, closing the page, or stopping the worker discards changes that have not been exported.
Can a query freeze the website?: SQL executes in a worker. Stop worker terminates it, and a 15-second timeout also stops it. This resets the database workspace; reopen your source file to continue. Very large files can still consume significant memory.
Which features and formats are supported?: Unencrypted SQLite 3 databases up to 50 MB are supported. There is no extension loading, encrypted database support or remote server connection. Results are limited to 5,000 rows across at most 25 statements; later statements are not run if the display limit is reached.
What do result exports contain?: CSV contains displayed values with spreadsheet formula protection. JSON preserves columns, row arrays and NULL values. BLOB cells are represented by their byte counts rather than exported binary contents. PDF is an image-based reading copy limited to 500 rows.

Found an issue? Send Feedback. See our data sources and update policy for tools that depend on changing information.