SQLite Playground
A real database, not a toy
This is the genuine SQLite engine compiled to WebAssembly, so the SQL you write behaves exactly as it would on a server or inside an app — joins, subqueries, common table expressions, window functions, aggregates, indexes, views, and transactions all work. Nothing is faked or approximated.
That makes it a dependable place to learn SQL with instant feedback, prototype a query before running it against production, or simply open a .sqlite file and look inside — without installing a database or a client.
Query a CSV like a table
Drop in a CSV and the tool turns it into a real table, using the header row for column names, so you can answer questions with GROUP BY, WHERE, ORDER BY, and JOIN instead of fighting spreadsheet formulas. Combine two imports to join datasets, then export the answer as a new CSV.
Why run it in the browser
Uploading a database to an online SQL sandbox means handing your data to a server you do not control. Here the engine runs on your own machine, so a client export, an analytics dump, or a personal project stays entirely private. It is also instant — no sign-up, no round-trip, and no rate limit.
Import, export, and reset
Load an existing .sqlite / .db file to explore its schema and data, or a CSV to query it as a table. Export a result set as CSV, or download the entire database as a .sqlite file you can reopen later or use elsewhere. Clear wipes just the editor; Reset to demo database rebuilds the seeded example so you can start fresh at any time.
Frequently asked questions
Is my database uploaded anywhere?
No. SQLite runs as WebAssembly inside your browser tab, so your queries and data stay on your device — nothing is sent to a server, which makes it safe for sensitive or proprietary databases.
Is this real SQLite?
Yes — it is the actual SQLite engine compiled to WebAssembly, so standard SQL, joins, subqueries, window functions, indexes, and built-in functions all work exactly as they do in native SQLite.
Can I load my own database or CSV?
Yes. Drop in a .sqlite, .db, or .sqlite3 file to query it directly, or import a CSV and it becomes a table named after the file, with columns taken from the header row.
Can I save my work?
You can export query results as CSV, or export the whole database back to a .sqlite file to keep. Reloading the page starts fresh, so export first if you want to keep changes, then re-import next time.
How do I clear the editor or start over?
Use Clear to empty the SQL editor and its results while keeping your data, or Reset to demo database to rebuild the seeded example and begin from scratch.
Is there a size limit?
There is no fixed cap — it is bounded by your device memory, since everything runs locally. Small and medium databases and CSVs are quick; very large files may be slower because the whole thing is held in the tab.