Every time we release a new update, you can access the new files via the Customer Portal. We provide updates to align with the latest shadcn/ui releases and incorporate user feedback. We also aim to provide updates when there's a new Figma feature or shadcn/ui component.
Log in to our Customer Portal with the email you used to make the purchase.
If you don't remember which email you used, try every address you might have used. If you're still stuck, contact us at hi@shadcndesign.com.
For Figma resources, updates are new Figma files that most often introduce new components or blocks, along with minor fixes and refinements. You can keep using your current version without disrupting your workflow. For code resources (the React and Premium packages), updates land in the registry: installing a block or template again with the shadcn CLI pulls the latest version.
Keep in mind that Figma is file-based, not a code repository, so updates can't be installed automatically like software packages. When we publish an update, it won't appear in your Figma library on its own, nor can it be "installed" with a single action.
Given this, we recommend copying over any new components you need from the updated file into your existing project. This lets you selectively incorporate the improvements most relevant to your work.
We rarely release major updates — usually when the official shadcn/ui receives a significant change. In those cases it's best to stick with the version you started your project on. Updating to a newer major version can be challenging because Figma treats each file separately: you'd need to manually transfer new components and tokens, which is harder still if you modified tokens or added your own components. We therefore recommend adopting new major versions only for new projects.
Kit 3.0 (September 2026) changed how colors are defined: the Tailwind palette moved to the Tailwind CSS v4 values, every base color token aliases that palette, and the custom/* and alpha/* tints are built with Figma's alias with opacity instead of flattened colors. A 2.x file keeps working as it is, but if you want the new model in a kit you already customized, the shadcn-design-update agent skill can migrate the variables in place. It keeps the colors you changed and only converts values that still match the stock kit; the report lists everything it left alone. Save a named version first.
This guide shows how to add new components from the latest shadcn/ui Figma kit to an existing custom library based on an older version, while preserving your styling.
Switch between light and dark modes on the new component. Confirm it uses your custom styling, including correct backgrounds for elements like input fields.
If some variables or components didn't swap, manually swap those instances with ones from your file.