{ } Formatters

SQL Runner (SQLite)

Run SQL queries against an in-browser SQLite database. Paste your schema, seed data, and query — instant results.

SQLite WASM Schema explorer Instant results No install

How the SQL Runner (SQLite) Works

The ByteKiln SQL Runner uses sql.js — a WebAssembly build of SQLite — loaded from a CDN. Your schema and queries run entirely in-browser with no server involved.

In-memory database

sql.js creates a transient SQLite database in your browser's memory. You define the schema using standard DDL (CREATE TABLE, INSERT) in the left panel, then run SELECT or other queries in the right panel.

Result display

Each SELECT statement produces a result set displayed as a table with column headers, row data, and a row count. NULL values are displayed as NULL in a muted color. BLOB columns show <blob> as a placeholder.

Table explorer

After loading a schema, the table explorer in the status bar shows each table name and column count. Hovering a table badge displays the column names and types as a tooltip.

FAQ

Short answers for the things developers usually ask before trusting a tool.

What SQL dialect does this support?

SQLite syntax. This covers most standard SQL including CREATE TABLE, SELECT, JOIN, GROUP BY, subqueries, CTEs (WITH), triggers, and views. MySQL or PostgreSQL-specific syntax may or may not work depending on the SQLite version bundled.

Is my data stored anywhere?

No. The SQLite database exists only in your browser's memory tab. Closing or refreshing the page destroys it entirely. No data is uploaded to any server.

How do I reset the database?

Click "Reload DB" to re-execute the Schema panel, which drops the old in-memory database and creates a fresh one. This is useful after experimenting with INSERT, UPDATE, or DELETE statements.

Can I run multiple statements?

Yes. The schema panel supports any number of CREATE TABLE, INSERT, and other DDL/DML statements. The query panel also supports multiple SELECT statements separated by semicolons — each produces its own result set.

Why does the first load take a moment?

SQLite WASM is fetched from a CDN on first use (~1MB). Once loaded, the binary is cached by the browser and subsequent loads are instant.

Related tools

Useful follow-ups when one conversion usually turns into three more.