duck/ui vs Origin UI
A large free collection covering the unglamorous surface area — forms, inputs, tables, application UI — as copy-paste Tailwind and shadcn components.
Short answer
Origin UI optimises for coverage and duck/ui optimises for identity. Origin UI is the better answer when you need many variants of ordinary things — twelve input states, a dozen table headers — styled neutrally. duck/ui is the better answer when the ordinary things already exist and the problem is that they look like everyone else's.
Origin UI is best described as: broad copy-paste component library. Compared against its publicly documented positioning as of 2026-07-31.
What Origin UI does well
Stated first, because a comparison that skips this is not worth reading.
- Breadth: far more variants of everyday form and application UI than duck/ui ships.
- Neutral styling that drops into an existing design system without fighting it.
- Free and copy-paste, with no runtime dependency.
- Strong reference material for input and form states.
Where they differ
| Origin UI | duck/ui | |
|---|---|---|
| Optimised for | Coverage of everyday UI | A stated aesthetic across the whole surface |
| Styling stance | Neutral, fits any system | Opinionated: dark-first, sticker borders, rationed holo |
| Restyles existing components | No | Yes — the theme is the first install |
| Best paired with | Your own brand tokens | Standard shadcn for primitives it skips |
Which to pick
Pick Origin UI
Pick Origin UI when you need volume — many variants of inputs, tables and application chrome — and the visual direction is already decided elsewhere.
Visit Origin UIPick duck/ui
Pick duck/ui when the visual direction is the missing piece, and one install that retunes every existing component is worth more than another twenty neutral variants.
Read the install guideUsing both
Good pairing. Take the Origin UI variant you need, swap its hardcoded colours for semantic tokens, and it inherits the duck theme like any shadcn component. duck/ui does not compete for that surface area — it is additive by design.
FAQ
Does duck/ui cover forms and tables like Origin UI?
Not at the same breadth, on purpose. duck/ui ships styled inputs, switches, checkboxes, radio groups, sliders and OTP fields, then defers to standard shadcn for tables and complex forms — which @duck/theme already styles.
Can Origin UI components use the duck theme?
Yes, once their colours reference semantic tokens rather than raw Tailwind palette classes. The theme implements the full shadcn variable contract, so anything written against that contract follows it automatically.