SQL Playground (In-Browser SQLite)

No. The database runs entirely in your browser using SQLite compiled to WebAssembly. Your queries and any file you open are processed locally and never leave your device.

It is real SQLite, so standard SELECT, INSERT, UPDATE, DELETE, JOIN, GROUP BY, ORDER BY, window functions, common table expressions, views, triggers and PRAGMA all work, matching whatever the bundled SQLite version supports.

Two related tables. A departments table with Engineering, Design, Sales and Support, and an employees table of ten people whose department_id references departments. It is designed to demonstrate joins, grouping and aggregate functions right away.

Yes. You can run a whole script separated by semicolons, such as a CREATE TABLE followed by INSERTs and a SELECT. Each statement that returns rows renders as its own results table beneath the editor.

Yes. Drop a .sqlite, .sqlite3 or .db file into the Load your own database zone. It opens locally in memory, replaces the sample, and you can query it or export it back out.

No. The database lives in memory, so refreshing or closing the tab resets everything to the sample. Use Download database first to save any schema or data changes you want to keep.

The SQLite WebAssembly engine has to download and initialize once on first use, which is the brief loading spinner you see. After it loads, queries execute instantly on your device with no network round trip.

Because it runs in memory in the browser tab, the practical ceiling is your device's available RAM. Small and medium databases are snappy, but a multi gigabyte file may be slow to open or exceed the tab's memory.

SQLite reports syntax and constraint problems just as a normal database would, and the message appears in a red panel. Check table and column names against the Tables list, and remember identifiers are case sensitive only where you quoted them.