DuckDB in your browser · Zero backend

Starting engine…

A data warehouse that runs entirely in your browser

A personal data workbench with zero backend. The query engine is DuckDB compiled to WebAssembly, running in this tab. It ships with a Parquet file of 5,972,131 NYC taxi trips, two more built-in datasets — and room for yours: drop in a CSV, Parquet, or JSON file, or import one from a link, and it becomes a table you can join against everything else. Your files are opened on your device and nowhere else — this page has no server to send them to. After every run, look inside it: the plan, what it read, and where the time went.

5,972,131rows in the trips table
57.2 MBmain Parquet file on storage
0backend servers involved
—engine + data ready in
SQL editor Ctrl/⌘ + Enter
No query run yet.
The engine is loading. A preset query runs automatically as soon as it is ready — then edit the SQL and make it your own.
Inside this run Nothing run yet.

How this works

  1. Parquet on plain file storage. Each dataset is a single columnar Parquet file (ZSTD-compressed, sorted on its main date column, statistics in every row group). In production these files would sit on object storage like Cloudflare R2 or S3; here they ship with the page.
  2. Range requests, not downloads. DuckDB reads the file footer first, then fetches byte ranges for the column chunks a query touches. A count(*) is answered from footer metadata alone — kilobytes, not megabytes — and a date filter skips whole row groups without reading them. The “What it read” view above shows this happening, from the run itself.
  3. The engine is WebAssembly. DuckDB-WASM — the official DuckDB project, also behind MotherDuck's browser UI and Evidence.dev sites — runs the full analytical engine in a Web Worker in this tab. Your SQL never leaves the browser.

What it can't do

  • No shared state. Every visitor gets their own engine. There is no multi-user warehouse here — no concurrency, no shared catalog, no accounts.
  • Uploads live for the session. Files you add are held in this tab's memory and are gone when it closes — by design. Re-adding a file under the same name is the refresh pattern, and saved queries that reference a missing upload say so and ask for the file again.
  • Bounded by the tab. Working sets have to fit in browser memory — keep them in the low gigabytes and lean on predicate pushdown.
  • Two honest qualifications. Importing from a link contacts that link's host from your browser. A ClickHouse connection holds its credentials in this tab only — use it for your own database, ideally with a read-only user.

Data: NYC TLC yellow taxi trips, Jan–Feb 2024, trimmed from the source's 19 columns and sorted by pickup time. Engine: DuckDB-WASM.