Run SQL queries against an in-browser SQLite database with table creation, import, and result display.
This tool is a working SQLite database inside the page. The engine is compiled to WebAssembly and runs entirely in your browser; you issue SQL statements against a database you build yourself - create tables, insert rows, import data - and each query's result renders as a table you can inspect. The usual surprise is the dialect. This is SQLite, not MySQL or PostgreSQL: syntax and behavior you verify here apply to SQLite and nothing else. Queries written for another engine can fail here, and results proven here do not guarantee the same outcome on your production database.
A concrete input and expected output from the current implementation.
Input
CREATE TABLE books (title TEXT, pages INTEGER);
INSERT INTO books VALUES ('Pride and Prejudice', 432), ('Moby-Dick', 585), ('The Great Gatsby', 180);
SELECT title FROM books WHERE pages > 300 ORDER BY pages DESC; Expected output
title Moby-Dick Pride and Prejudice 2 rows returned
The WHERE clause keeps only the two books over 300 pages, and ORDER BY pages DESC sorts by page count, so Moby-Dick (585) precedes Pride and Prejudice (432). The Great Gatsby (180) fails the filter and is excluded.
The page loads the SQLite engine compiled to WebAssembly and runs it locally, so your statements never leave the browser. All statements execute against one shared database: CREATE TABLE adds a schema object, INSERT adds rows, and a later SELECT sees the accumulated state, just like an interactive sqlite3 session. Referencing a table that was never created fails with SQLite's own error message, which names the missing object.
Each executed statement returns either a row set or a change count. Row sets render as a table with the column names as the header; every selected row appears once, in the order the engine returned it. The import path turns external data into a table you can then query with ordinary SQL, and each new query re-reads the current state of the database.
Only if they happen to be portable SQL. This playground runs SQLite, which has its own dialect: TOP, backticks, NOW(), and similar constructs do not work, while SQLite accepts things like LIMIT and ON CONFLICT that others do not. Treat results here as describing SQLite behavior only.
No. The SQLite engine is compiled to WebAssembly and executes inside the page, so your statements, imports, and data are processed locally and nothing is transmitted. Note that running locally also means nothing is stored for you: keep your own copy of anything you want to keep.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.