SQL Playground

Run real SQLite in your browser: write a query against a sample shop or your own tables, and see every result set, the schema and the query plan.

Query

SELECT c.city,
       COUNT(*) AS orders,
       printf('%.2f', SUM(o.qty * p.price_paise) / 100.0) AS revenue_rupees
FROM orders o
JOIN customers c ON c.id = o.customer_id
JOIN products p ON p.id = o.product_id
GROUP BY c.city
ORDER BY SUM(o.qty * p.price_paise) DESC;

Ctrl + Enter (⌘ + Enter) runs it. Each run starts from the setup script, so nothing you change is kept.

Setup script — tables and data

-- A small shop. Edit freely: every run starts from this script.
CREATE TABLE customers (
  id INTEGER PRIMARY KEY,
  name TEXT NOT NULL,
  city TEXT NOT NULL,
  joined DATE NOT NULL
);

CREATE TABLE products (
  id INTEGER PRIMARY KEY,
  name TEXT NOT NULL,
  category TEXT NOT NULL,
  price_paise INTEGER NOT NULL  -- money as whole paise, never a float
);

CREATE TABLE orders (
  id INTEGER PRIMARY KEY,
  customer_id INTEGER NOT NULL REFERENCES customers(id),
  product_id INTEGER NOT NULL REFERENCES products(id),
  qty INTEGER NOT NULL CHECK (qty > 0),
  ordered_on DATE NOT NULL
);

INSERT INTO customers (name, city, joined) VALUES
  ('Asha Rao', 'Bengaluru', '2025-01-12'),
  ('Vikram Singh', 'Delhi', '2025-03-03'),
  ('Meera Iyer', 'Chennai', '2025-04-21'),
  ('Kabir Shah', 'Mumbai', '2025-06-30'),
  ('Nisha Gupta', 'Pune', '2025-08-15'),
  ('Rahul Das', 'Kolkata', '2026-01-05');

INSERT INTO products (name, category, price_paise) VALUES
  ('Filter coffee, 500 g', 'Grocery', 42000),
  ('Steel tiffin box', 'Kitchen', 64900),
  ('Cotton kurta', 'Clothing', 129900),
  ('Masala chai, 250 g', 'Grocery', 18500),
  ('Pressure cooker, 5 L', 'Kitchen', 249900),
  ('Handloom saree', 'Clothing', 459900);

INSERT INTO orders (customer_id, product_id, qty, ordered_on) VALUES
  (1, 1, 2, '2026-01-10'), (1, 4, 3, '2026-02-02'), (2, 5, 1, '2026-01-18'),
  (3, 3, 2, '2026-02-14'), (3, 1, 1, '2026-03-01'), (4, 6, 1, '2026-03-08'),
  (4, 2, 2, '2026-03-09'), (5, 4, 5, '2026-03-20'), (5, 1, 1, '2026-04-02'),
  (2, 2, 1, '2026-04-11'), (1, 5, 1, '2026-05-06'), (6, 3, 1, '2026-05-19');

Results

Loading SQLite — about 650 KB, once. Every query then runs here, in your browser.

Runs in your browser — nothing you enter leaves this device.

About this tool

What it does

SQL Playground runs SQLite — the real database engine, compiled to WebAssembly — inside your browser. It opens with a small sample shop (customers, products and orders) so you can try joins, GROUP BY, window functions such as RANK and running totals, common table expressions and EXPLAIN QUERY PLAN straight away. Every statement that returns rows gets its own result table, and the side panel lists each table with its columns, keys and row count. Change the setup script to build your own tables, or paste one from a project. Each run starts from the setup script on a fresh database, so you can DELETE or DROP anything and simply run again.

How to use it

Wait a moment on first visit while SQLite loads (about 650 KB, once); the sample query then runs by itself.
Pick an example query, or write your own in the Query box.
Press Run, or Ctrl + Enter (⌘ + Enter on a Mac).
Read the results; download any result set as CSV.
Open “Setup script” to see or change the tables and data every run starts from — or press “Start empty” and write your own CREATE TABLE statements.
Use the Tables panel to check column names and types while you write.

Limits and your data

This is SQLite. Most standard SQL works, but other databases differ: types are flexible (a column declared INTEGER can hold text), and functions such as DATE_ADD from MySQL or ILIKE from PostgreSQL are not available.
Each result shows up to 1,000 rows; the full count is given and CSV downloads the rows shown.
A query that runs for more than 8 seconds is stopped, so an endless recursive query cannot freeze the page.
Nothing is saved between runs or visits. Keep your setup script somewhere safe if you need it again.
The engine is not part of the offline download, so the first visit needs a connection.
Your SQL and data never leave the browser: the database lives in memory inside this page and disappears with each run. Only the SQLite engine itself is downloaded, from this site.

Questions

Is this a real database or a simulation?

Real. It is SQLite 3, the same engine that ships in Android, iOS and every major browser, built for WebAssembly by the open-source sql.js project. Query plans, constraints and errors are SQLite’s own.

Why did my changes disappear?

Each run rebuilds the database from the setup script, then runs your query. That makes every result reproducible and lets you experiment freely. To keep a change, put it in the setup script.

Why is money stored in paise in the sample?

Floating-point numbers cannot hold most decimal amounts exactly — 0.1 + 0.2 is not 0.3 — so sums of prices drift. Storing whole paise as integers and dividing by 100 only for display keeps every total exact.

Can I load my own database file?

Not yet. Paste the CREATE TABLE and INSERT statements (for example from sqlite3’s .dump) into the setup script instead.