duck/ui vs other shadcn registries
Most of these are not substitutes for each other. This page says what each one is for, including the cases where duck/ui is the wrong answer.
Short answer
duck/ui is a theme-first shadcn registry: the first install is a token set that restyles the shadcn components already in your project, and the components that follow are the ones shadcn does not ship. Most other registries are component-first — a catalogue of effects or of coverage — which makes them complements rather than competitors. The honest comparison is not “which registry wins” but “which problem do you have”: a look that reads generic, an effect you are missing, or behaviour that is expensive to build.
Everything on this page is compared against publicly documented positioning as of 2026-07-31. Counts and feature lists move fast in this ecosystem — check the other project before you decide.
The registries
One page each, with the case for picking the other one stated first.
- duck/ui vs shadcn/uicompareThe original copy-paste component collection and the CLI, schema and MCP server that every third-party registry rides on.The base layer every registry installs into
- duck/ui vs Magic UIcompareA large free registry of animated React components — marquees, animated beams, bento grids, text effects — built on React, Tailwind and Motion.Animated component registry
- duck/ui vs Aceternity UIcompareThe boldest visual effects on the shelf — 3D cards, spotlights, glowing beams, magnetic buttons, particle backgrounds — aimed at landing pages that need to look expensive.Visual-effects component collection
- duck/ui vs Origin UIcompareA large free collection covering the unglamorous surface area — forms, inputs, tables, application UI — as copy-paste Tailwind and shadcn components.Broad copy-paste component library
- duck/ui vs Kibo UIcompareA trusted shadcn registry shipping the components teams would otherwise build from scratch — Gantt charts, Kanban boards, a code editor, AI chat elements, colour pickers, file dropzones.Complex stateful component registry
When not to pick duck/ui
Three cases where the answer is genuinely something else.
- You already have brand tokens. The value here is the opinion. If a design team already decided the colours, plain shadcn/ui plus your own token file is less work and less to unpick.
- You need a board, a chart or an editor. duck/ui stops at controls, surfaces, feedback and three blocks. Kibo UI and standard shadcn cover that ground and the theme styles both.
- Light mode is the product. duck/ui is designed dark first and light is derived from it. It works, but a light-first product is not what the system was drawn for.
Install
One line in components.json, then the theme.