Updates

Shadcn/Studio is continuously maintained with new components, blocks, and refinements are added regularly to stay aligned with shadcn/ui as it evolves.

Keeping your kit up to date means you always have access to the latest components and improvements without having to rebuild anything from scratch.

How Figma File Updates Work?#

Updates are published as new Figma files containing new components, blocks, and minor fixes. Your existing file is never touched - you continue working from your current version without any disruption. Figma is file-based, not a package manager. Updates cannot be applied automatically like a software install. When a new version is published, it won't appear in your library on its own - you need to access it manually and bring in what you need.

Updates may include:

• New shadcn/ui components
• New blocks and templates
• New themes and variables
• Improvements based on user feedback
• Compatibility updates for the Shadcn/Studio Figma plugin and AI workflow

How to get new updates?#

When an update is available, access it the same way you accessed the original kit:

1. Changelog to Shadcn/Studio using the email address associated with your purchase.
2. Go to the profile menu and open Purchases
3. Click on the Designs tab to access, Here, you will be able to access the Figma files included in your plan.
4. Figma will open the file - click Duplicate to your drafts to save a copy.
5. You now have the updated file available alongside your existing project.

Applying Updates#

Once you have the updated file, we recommend copying only the new components or blocks you need into your existing project file. This way you selectively bring in what's relevant to your work without touching anything already in place.

If You Duplicated the Figma File

If you duplicated the Shadcn/Studio file and are designing directly inside it, you can open the latest version from your account and manually copy the updated assets into your current file.

Recommended workflow

1. Open your current duplicated Shadcn/Studio file.
2. Open the latest Shadcn/Studio Figma file.
3. Compare the updated components, blocks, templates, or variables. (You can refer the Changelog for Shadcn/Studio Figma file updates.)
4. Copy the required new assets from the latest file.
5. Review the design and adjust variables or styles if needed.

If You Are Using the Published Library

This workflow is useful when you have already customized variables, themes, styles, or components in your own library and want to add only the new updates from the latest Shadcn/Studio file.

If you have created a custom Shadcn/Studio library based on an earlier version of the Figma UI kit, you can still bring in the latest components without losing your existing customizations in design system.

Prerequisites

Before you start, make sure you have:

• A Figma Pro or higher account to publish and manage libraries
• The latest Shadcn/Studio Figma file accessed from your Purchases
• Your customised design connected to the Shadcn/Studio Figma file's variables

Step-by-Step: Add New Components to Your Existing Library

Step 1: Open Both Files

Open both Figma files in your workspace:

1. Your existing custom Shadcn/Studio library file
2. The latest Shadcn/Studio Figma UI Kit file

Step 2: Publish Both Libraries

1. Open your custom library file and Publish it as a Figma library.
2. Open the latest Shadcn/Studio Figma UI Kit file and Publish it as a Figma library as well.
3. Wait until all components, styles, and variables are fully published.
4. Reload both files in Figma.

Publishing both libraries helps Figma properly detect components, styles, and variables during the swap process.

Step 3: Copy the New Component

Now copy the new component from the latest Shadcn/Studio UI Kit into your custom library.

1. In your custom library, add any required new variables if the new component depends on them.
2. Copy the desired new component from the latest UI kit
3. Paste it into your custom library file.

When you paste a component into your custom file, it may still be linked to the source library if it appears as an instance. If you paste a full component set, it becomes a new independent component in your file and does not need to be detached.

The next step will help connect it with your custom library.

Step 4: Swap the Source Library

Use Figma's Swap Library option to replace the source library references with your custom library.

1. In your custom library file, open the Assets panel
2. Click the **Libraries** icon
3. Find the latest Shadcn/Studio file's library and add it to your file if it hasn't been added yet
4. Under Libraries used in this file, find the latest Shadcn/Studio library
5. Click Swap library
6. Select your custom Shadcn/Studio library as the destination
7. Review the components, styles, and variables Figma will replace
8. Click Swap library to confirm

This helps the newly added component use Variable values from your custom library instead of staying linked to the latest Shadcn/Studio source file.

Step 5: Verify the Component

After swapping the library and variables, review the component carefully.

Check the following:

1. Light mode works correctly
2. Dark mode works correctly
3. Colors follow your custom theme
4. Backgrounds, borders, and text colors are using your variables
5. Component variants are working as expected
6. No styles are still linked to the latest Shadcn/Studio source file

You're All Set#

This process helps you keep your custom Shadcn/Studio library up to date while preserving your existing design system, variables, and theme customisations.

Instead of replacing your full library, you can safely import only the new components you need and connect them with your custom setup.

Major Version Updates

Occasionally a major update is released when shadcn/ui goes through a significant change. In these cases, we recommend staying on the version you originally used for any existing projects.

Migrating to a new major version means manually transferring all new components and variables - a process that gets complex if you've modified variables or added custom components. For this reason, major versions are best adopted when starting a new project.

Changelog

A full list of changes, additions, and fixes for every version is available on the Changelog Page