What you get in the window
The pieces of a database client, with nothing to connect first.
Open a database, or just files
A
.duckdbfile opens as the main database. CSV, Parquet, JSON and Excel files open beside it as views and tables, in memory or inside the database you opened.Write SQL with the catalog at hand
Browse tables and columns in the schema sidebar, generate a
SELECTfrom it, and let autocompletion offer your tables, columns and DuckDB functions. Tabs, formatting and the.tables,.schemaand.databasesdot commands are there too.See where the time goes
Explain shows the plan without running the statement. Profile runs it and shows each operator's own time and its estimated versus actual rows.
Query across databases
Attach another DuckDB or SQLite file beside the main database and join across them, for example a snapshot next to today's data. Attachments are read-only unless you say otherwise, get an alias from the file name, and come back on the next launch.
-- snap-2026-10-01.duckdb attached as snap_2026_10_01 SELECT t.id, t.amount, s.amount AS amount_last_week FROM orders t JOIN snap_2026_10_01.orders s USING (id);
Built around the DuckDB engine
DuckLocal exposes what DuckDB can do instead of hiding it behind a generic database driver.
- ExplainThe query plan, without executing the statement
- ProfilePer-operator time, estimated versus actual rows
- ExtensionsList, install, load and update DuckDB extensions
- ATTACHDuckDB and SQLite databases side by side
- s3://S3 and S3-compatible storage through httpfs
- Storage formatSee which DuckDB versions can read a database file
- start_ui()Run the DuckDB UI notebook on the same instance
- .dashPlain-text dashboards with charts and cross-filtering
How it differs from other DuckDB clients
The duckdb command-line shell is the reference client, and the DuckDB UI is a notebook that runs in your browser. General-purpose database tools reach DuckDB through a driver and a connection profile.
DuckLocal is a single desktop program with the engine inside, so opening a database is opening a file. If you want the notebook as well, the DuckDB UI runs inside DuckLocal with CALL start_ui(). DuckDB UI vs DuckLocal compares the two in detail, and DuckLocal vs DBeaver covers general-purpose database clients.
- No server process to start or stop
- No JDBC driver or connection profile
- No account and no telemetry
- Database files it creates stay readable by DuckDB 1.x
- A clear explanation when a database file will not open
Scripts and AI agents use the same engine
The same binary runs without a window. ducklocal query runs one SQL statement and prints JSON, and ducklocal schema lists what can be queried.
DuckDB GUI questions
- Is there an official DuckDB GUI?
- DuckDB ships the DuckDB UI, a notebook that runs in your browser and is started with
CALL start_ui(). DuckLocal is an independent open-source desktop app with DuckDB embedded; it is not made by the DuckDB project. The DuckDB UI can also run inside DuckLocal. - Which DuckDB version does DuckLocal use?
- DuckLocal embeds DuckDB 2.0. A database file it creates is written in the format DuckDB 1.x also reads, and a file already in the DuckDB 2.0 format opens and keeps that format.
- Can DuckLocal open my existing .duckdb file?
- Yes. Open it as the main database, or attach it beside the one you have open. When a file was written by a newer DuckDB than the one inside DuckLocal, the app says so and gives you SQL that copies it into a format it can read.
- Does it work with SQLite databases?
- Yes. Attach a SQLite file with Open → Attach database… and query its tables next to your DuckDB tables and data files.
- Is DuckLocal free?
- Yes. DuckLocal is free and open source under Apache-2.0. It runs on macOS 12 or later on Apple silicon, 64-bit Windows 10 or later, and Linux x86_64.
Related: Local data analysis · Parquet viewer · Query CSV with SQL
Open your first database
Download DuckLocal, drop a .duckdb file or a folder of data files onto the window, and run a query.