Use this online SQLite playground and SQL editor to run real SQLite statements in a temporary database inside your browser. If you want a step-by-step workflow, see How to Run SQLite Online in Your Browser. Choose an example, edit the SQL, and run it to see result tables. The sample includes employees and departments; you can change its schema and data freely, then restore the sample at any time. You can also open a local .sqlite, .sqlite3, or .db file up to 25 MiB, or import spreadsheets and text tables using our browser-based CSV to SQL converter. Examples cover SQLite printf() and format() formatting, JSON and JSONB values, when to use SQLite JSONB, window functions, and timediff(). To format your current query, open the SQL formatter; query text is passed through one-time browser session storage. If storage is unavailable, the link stays on this page so you can copy the SQL manually. For SQLite formatting, you can also send the formatted query back to this playground to review and run yourself.
This playground runs SQLite SQL only. It does not connect to a server or emulate MySQL, PostgreSQL, or SQL Server. The database exists in memory for this page and is cleared when you reload it. SQL text, schemas, and result rows stay in the browser and are not sent to SQLiz.
Loading the local SQLite playground. It requires JavaScript and a browser with WebAssembly support.
Run SQLite SQL
Use this temporary sample database, create your own tables, or open a local SQLite file. The selected file is read into browser memory; it is not uploaded. Close applications using the database first. A WAL sidecar file is not imported, so checkpoint and close WAL databases before selecting the main database file.
Select one or more statements to run only that selection; with no selection, the whole editor runs. Press Ctrl+Enter (Windows/Linux) or ⌘+Enter (Mac) to run SQL. Multiple statements are allowed. Result tables show up to 200 rows each. Errors are displayed here and do not change the database beyond statements that completed before the error.
BLOB results are shown as hexadecimal. Values longer than 64 bytes show the first 64 bytes and total length. Download the database and inspect it in a local SQLite client to view the full value.
Starting SQLite…
When Google Analytics is enabled, SQLiz records whether a run succeeded, how many result sets it returned, whether a local file was opened or exported, and broad error categories (for example, syntax error or missing table). It does not record SQL text, file names, file sizes, database contents, result values, or raw error messages.
The browser engine is sql.js 1.14.2, which embeds SQLite 3.49.1. The active SQLite version is also shown when the playground starts. Functions added in later SQLite releases may be unavailable here; for example, jsonb_each() requires SQLite 3.51.0 or later. SQL.js is MIT-licensed, and SQLite is public domain. The engine runs locally in your browser and is loaded only on this page.
Frequently asked questions
Is this a real SQLite database?
Yes. The playground runs SQLite through sql.js/WebAssembly in your browser. You can create tables, insert and update rows, run joins, CTEs, window functions, and other SQLite statements supported by the embedded SQLite version.
Can I open my own SQLite database online?
Yes. You can open a local .db, .sqlite, or .sqlite3 file up to 25 MiB. The file is read into browser memory and is not uploaded to SQLiz.
Does the database persist after I close or reload the page?
No. The working database is temporary. Reloading the page resets the playground. Use Download database before leaving if you want to keep your changes.
Can I use this as an online SQL editor for MySQL or PostgreSQL?
No. This playground executes SQLite SQL only. For MySQL, PostgreSQL, MariaDB, Oracle, or SQL Server queries, use the SQL Formatter to format the statement, but test it against the actual database engine.