Question 1

Does my data ever leave my browser?

Accepted Answer

No. The SQL engine (DuckDB, compiled to WebAssembly) runs inside this browser tab, and your file's bytes are handed straight to it. You can verify this yourself: open your browser's Network tab, load a file, and run a query — you'll see no network activity related to your data.

Question 2

What file formats can I import?

Accepted Answer

CSV, JSON, XLSX (Excel), and Parquet. You can import several files and join or compare them with regular SQL, just like separate tables in a database.

Question 3

Is there a file size limit?

Accepted Answer

There's no hard cap on file size, but the SQL engine runs as 32-bit WebAssembly in your browser, which caps any single allocation — like the hash table built during a join — at around 2 GiB, regardless of how much RAM your machine has. This mostly only matters for large joins or aggregations, not for browsing or filtering a single file. If you hit it, try selecting fewer columns before joining, filtering each side down first, or pre-aggregating one side before combining.

Question 4

Does my data survive a page reload?

Accepted Answer

No — reloading the page gives you a fresh, empty session, same as opening a new in-memory database. Nothing is written to disk, which is part of how it stays private. Re-import your files after a reload to continue where you left off.

Question 5

What SQL engine powers this?

Accepted Answer

DuckDB — a real, full-featured analytical SQL database — compiled to WebAssembly via duckdb-wasm, so it runs at near-native speed directly in the browser.

Question 6

Do I need to install anything or create an account?

Accepted Answer

No installation and no account. Everything runs from this page, and after the first load, the app itself works offline — only your data transfers (i.e. none) happen over the network.