some of the comments on that thread are surprising. Are people not aware that software can be bundled in such a way as to run on machines not having internet access?
the background is this UI is the MotherDuck UI for their cloud SaaS app. MotherDuck is a VC-backed DuckDB SaaS company, not to be confused with DuckDB Labs or the DuckDB foundation
MotherDuck decided to take their web app UI and make it a locally usable extension via DuckDB. however as noted in that thread, the architecture is a bit odd as the actual page loads once the extension is running from MotherDuck’s servers (hence the online requirement)
I don’t think it’s intentionally malicious or bad design or anything, just how this extension came about (and sounds like they’re fixing it)
disclaimer: I do know and actively work with the MotherDuck folks, I’ve also worked w/ DuckDB Labs in the past
Not OP, but depending on your use case, client side operations could be a big deal.
Something like a dashboard app for instance, might have callbacks where it needs to run a new SQL query based on input, but be small enough to make loading all data onto menory and querying locally a mich faster option.
Obviously ymmv and if you have a dashboard with a heavy data set under the hood, your gonna make a lot of users unhappy fast by doing that.
Here's some quick issues and suggestions I found after about 5 minutes of playing around with it. All test were done using Firefox FYI.
1. One of my favorite features from the built in DuckDB UI is the panel that automatically generates graphs for each column, both for the whole dataset itself and for the specific query you're running. I often find myself not even writing any queries because all I needed was something really simple already available in that panel. This would be my #1 reason for not using this GUI instead of the built in one.
2. I could not find any panel to show the currently selected value in the grid view. Ideally I would like this to also be able to auto-detect common formats like JSON and format them, etc.
3. The grid view can show a maximum of 200 rows. Finding a way to virtually render the rows in an infinite list would be much better IMO. I've found myself selecting up to 10k+ rows in the built in GUI and to copy all IDs, etc, several times (saves sometime compared to exporting a CSV and copying from there).
4. The column filter dropdown in the grid view has a search bar which is nice, but it is automatically deselected on each character entry, making it very annoying to use...
5. Additionally the dropdown filter menus are not automatically closed when you click outside or open another dropdown, which is a minor annoyance.
6. The right click menu in the grid viewer will close on "mouse out", however it does not close on "click outside" and the cursor does not start inside of the menu itself. This means the menu becomes permanently stuck until hover over it if you immediately move the mouse to the top-right on open.
7. The grid view resizer is behaving buggy sometimes after changing the number of page rows to display.
8. The transparent tooltip background in the chart viewer makes the light-gray text impossible to read in dark-mode when there is yellow behind it (from other the chart bars).
9. The explorer side panel seems to be sized based on a percentage of the window size. this is quite minor but it would behave nicer if it had a fixed size so changing the window size does not also resize the side panel. It is also overly large when you first load the site.
This is cool, thanks. I use the embedded UI but I’m going to play around with yours too.
DuckDB is the single-most impressive piece of software I’ve used in my career. I’m mangling terabytes of parquets daily and it just handles them effortlessly; the bindings also also well-written.
TRUE! It's amazing and I have in other project too! The idea of of this app 100% in browser came from handling lots of CSV's from different people in my former company... Just to load in excel it took forever, then I came up with this, it made my life much easier, hope it makes yours too!
You’re underselling this. Running it locally also gives you access to all cores and all RAM. Wasm is very limited comparatively - perf is not even close.
I'd love to make it work with flightsql or HTTP endpoints returning arrow IPC [0]!
Did you consider using perspective for last-mile charting [1]? Building your own seems like a huge chunk of work. Well done!
I just leave 'duckdb --ui' running on my computer at all times. While the functionality is great, I'm really not happy that UI itself isn't open source and instead controlled by motherduck. There are many quick and easy improvements that will probably never get made, as motherduck has no real incentive to improve it at this point.
Wonder if this work could be ported as a replacement to duckdb local UI?
I would love for this to be the case... I'm also not a fan of mother's duck ui... Also I created this project like 2 weeks before they launch it (that's why it's named duckui...) I would choose another name but well I had bought the domain already hahaha... But SURE, I would like this to be the best UI ever for all of us... Just need some ideas/help to implement all missing parts...
Curious how tricky it would be to connect this to a local instance of duckdb running in UI mode instead of browser WASM. (Or if that even aligns with your vision of this project). From what I can tell looking just looking at it on my phone your UI seems like a great start to replacing motherduck.
Or it looks like that's basically already supported?! Sorry, I need to spend some time with this, but I'll definitely be testing it out and will provide feedback and/or contributing
This is not really a problem introduced by the thing in the article, but the "UI" for duckdb just kinda sucks. When I want to interactively explore some data, I want to easily add conditions and aggregates, but there's nothing in the Duck UI that actually does this. It will make a little table of the top 20 values of irritating_column_name but there's not a 1-click way to add `where irritating_column_name = 'incredibly inconvenient value'` to the query and re-run, which is an absolutely basic data exploration feature.
In theory there's none... DuckDB is like Sqlite, it's a file, but in this case it's 100% wasm so theres zero interaction with any "server", it's all on Browser. One example of DuckDB in server is mother duck... It makes .duckdb files "available" on the cloud.
When DuckDB queries across multiple sources (say, Postgres and a CSV) does it first load all data into DuckDB or is it smart enough to only pull minimal data needed for the query on the fly?
"DuckDB offers robust capabilities for querying data stored partially on S3, particularly when dealing with Parquet files. This is achieved through several optimization techniques:
Predicate Pushdown: When you apply a WHERE clause to filter data, DuckDB can "push down" this filter directly into the Parquet file scan. If the Parquet file contains zonemaps (metadata about value ranges within columns), DuckDB can use this information to skip reading entire sections of the file that do not contain relevant data, significantly reducing the amount of data transferred from S3.
Projection Pushdown: When you select only specific columns in your SELECT statement, DuckDB automatically reads only those required columns from the Parquet file. This means you avoid downloading and processing unnecessary data, leading to faster queries and reduced S3 transfer costs.
HTTP Range Reads: DuckDB leverages HTTP range headers when interacting with S3 (or other object storage supporting range reads). This allows it to fetch only the necessary parts of the Parquet file, such as metadata or specific column chunks, rather than downloading the entire file."
https://duckdb.org/2025/03/12/duckdb-ui
(You can use it offline)
https://github.com/duckdb/duckdb-ui/issues/62
MotherDuck decided to take their web app UI and make it a locally usable extension via DuckDB. however as noted in that thread, the architecture is a bit odd as the actual page loads once the extension is running from MotherDuck’s servers (hence the online requirement)
I don’t think it’s intentionally malicious or bad design or anything, just how this extension came about (and sounds like they’re fixing it)
disclaimer: I do know and actively work with the MotherDuck folks, I’ve also worked w/ DuckDB Labs in the past
Separate entities, but cooperative/comprised of many overlapping people, right?
1. DuckLake is the best datalake spec and their team is improving on the extension rapidly.
2. With DuckDB WASM, you can make apps that would normally have 2 to 3 second latency for network calls work in < 200ms.
We use it as our built-in datalake at Definite and couldn't be happier with it.
0 - https://ducklake.select/
1 - https://www.definite.app/blog/ducklake
Something like a dashboard app for instance, might have callbacks where it needs to run a new SQL query based on input, but be small enough to make loading all data onto menory and querying locally a mich faster option.
Obviously ymmv and if you have a dashboard with a heavy data set under the hood, your gonna make a lot of users unhappy fast by doing that.
INSTALL iceberg;
to start working with iceberg https://duckdb.org/docs/stable/core_extensions/iceberg/overv...
I was using it even before it hit 1.0
1. One of my favorite features from the built in DuckDB UI is the panel that automatically generates graphs for each column, both for the whole dataset itself and for the specific query you're running. I often find myself not even writing any queries because all I needed was something really simple already available in that panel. This would be my #1 reason for not using this GUI instead of the built in one.
2. I could not find any panel to show the currently selected value in the grid view. Ideally I would like this to also be able to auto-detect common formats like JSON and format them, etc.
3. The grid view can show a maximum of 200 rows. Finding a way to virtually render the rows in an infinite list would be much better IMO. I've found myself selecting up to 10k+ rows in the built in GUI and to copy all IDs, etc, several times (saves sometime compared to exporting a CSV and copying from there).
4. The column filter dropdown in the grid view has a search bar which is nice, but it is automatically deselected on each character entry, making it very annoying to use...
5. Additionally the dropdown filter menus are not automatically closed when you click outside or open another dropdown, which is a minor annoyance.
6. The right click menu in the grid viewer will close on "mouse out", however it does not close on "click outside" and the cursor does not start inside of the menu itself. This means the menu becomes permanently stuck until hover over it if you immediately move the mouse to the top-right on open.
7. The grid view resizer is behaving buggy sometimes after changing the number of page rows to display.
8. The transparent tooltip background in the chart viewer makes the light-gray text impossible to read in dark-mode when there is yellow behind it (from other the chart bars).
9. The explorer side panel seems to be sized based on a percentage of the window size. this is quite minor but it would behave nicer if it had a fixed size so changing the window size does not also resize the side panel. It is also overly large when you first load the site.
DuckDB is the single-most impressive piece of software I’ve used in my career. I’m mangling terabytes of parquets daily and it just handles them effortlessly; the bindings also also well-written.
[0] https://duckdb.org/docs/stable/clients/wasm/data_ingestion#a... [1] https://github.com/finos/perspective
Using my textplot extension doesn't result in my expected output:
---
install textplot from community;
load textplot;
select tp_bar(0.5)
---
I ask because I am under the impression that the 'DuckDB Wasm' client provided by DuckDB doesn't yet support all of the DuckDB functions.
So I am interested to know if this has implemented more, fewer, or the same set of functions.
Wonder if this work could be ported as a replacement to duckdb local UI?
quote - google ai mode:
"DuckDB offers robust capabilities for querying data stored partially on S3, particularly when dealing with Parquet files. This is achieved through several optimization techniques:
Predicate Pushdown: When you apply a WHERE clause to filter data, DuckDB can "push down" this filter directly into the Parquet file scan. If the Parquet file contains zonemaps (metadata about value ranges within columns), DuckDB can use this information to skip reading entire sections of the file that do not contain relevant data, significantly reducing the amount of data transferred from S3.
Projection Pushdown: When you select only specific columns in your SELECT statement, DuckDB automatically reads only those required columns from the Parquet file. This means you avoid downloading and processing unnecessary data, leading to faster queries and reduced S3 transfer costs.
HTTP Range Reads: DuckDB leverages HTTP range headers when interacting with S3 (or other object storage supporting range reads). This allows it to fetch only the necessary parts of the Parquet file, such as metadata or specific column chunks, rather than downloading the entire file."
Rill Data - https://www.rilldata.com Summer - https://summer.io Hex - https://hex.tech Evidence - https://evidence.dev
https://observablehq.com/framework/lib/duckdb