DuckQuery/DuckDB GUI
DuckDB GUI
DuckQuery puts DuckDB in a desktop workbench: files as tables, cross-source JOINs, charts — without scripting a stack first.
What “DuckDB GUI” means here
DuckDB is an engine (plus CLI). People searching for a DuckDB GUI usually want a visual client: browse tables, write SQL, inspect results.
DuckQuery is that GUI: sources on the left, SQL editor in the middle, results below — powered by DuckDB locally.
GUI vs CLI / notebooks
CLI and notebooks shine for scripted pipelines. A GUI fits ad-hoc joins, reconciliation, and dropping Excel into a query.
DuckQuery also lets local files and MySQL / PostgreSQL share one SQL via ATTACH / cross-source JOIN.
Common workflow
Drop CSV / Excel → queryable tables.
Connect live databases → JOIN with local files.
Optionally draft SQL with AI on your own model endpoint, then confirm before running.
FAQ
Is DuckQuery the official DuckDB GUI?
No. DuckQuery is an independent MIT open-source project that uses DuckDB as the local analytics engine and adds a desktop workbench plus cross-source features.
Demo vs full GUI?
The online demo is DuckDB-Wasm in the browser only (no AI, no DB connections, no Excel). Use the desktop app or Docker for the full GUI.