Help others

Hi! I’m experiencing an issue with nested components placed inside a component slot.After triggering an interaction, some of the nested components visually reset to the default state defined in the design system. However, when I hover over them, they immediately return to the correct state they were supposed to display.In the attached video, the chips inside the drawer are configured with different labels and states. After closing and reopening the drawer, some of them appear with their default properties. As soon as I move the cursor over each chip, the correct label and state are restored.This appears to be a rendering issue, since the overrides are not actually lost and return without any additional interaction besides hovering.I’ve attached a screen recording showing the behavior. Has anyone experienced something similar or found a workaround?

Every time I move or import a component from my Design System into another Figma file, it loses all of its interactions — including click, hover, pressed states, overlays, and other prototype interactions.The component itself, variants, and properties are still there, but the interactions are completely lost or stop working as expected.Has anyone experienced this issue? Is there a specific Figma setting, Library configuration, or limitation that could cause prototype interactions to be lost when moving a component between files?I'd really appreciate any insights or suggestions on how to prevent this from happening.

I am facing an issue with split tabs. So this issue I have faced last time also and I am facing now also. When I select two different files. And right click on the tabs. Then click on the. Split tabs. It is splitting with the same file. Now for example. I have a. Project 1 file and project 2 file. I have selected project 1 and 2. And then I split it but it is splitting with project 1 and project 1. That is the issue.

Request: Through the Figma MCP, access contents of comments made in Figma Design file.Reason: Can provide context for designs, review bugs, etc.Current response from OpenAI Codex with direct link to comment:No, not the comment itself.What I can see from that link is the node it points to:file: XXXXXXnode: XXXXXXscreen: /sign-up-2 (iOS)That screen contains:nav title Sign UpEmail and Password inputsSign Up primary CTAContinue with AppleContinue with Googledivider OrAlready have an account? Sign inbottom legal linksBut I still cannot read the actual Figma comment thread or the #XXXXXX anchor content from this session.If you want, paste the comment text here and I can map it to this exact screen and tell you what change it implies. 

Colored tokens are correctly displayed in the Figma preview of Lotties, but this is not yet the case when exporting to .lottie, which requires two exports, increases file size, and necessitates mapping on the developer’s end.We would like to be able to manage this mode directly within a single asset.

When applying text styles that have associated variables attached the values presented do not respect the applied mode. For instance I have a title that has a mode for Mobile (20px), and a mode for TV (40px), when i open up the style, the default mode (in this case mobile) is displayed instead of the TV mode size. I have also observed this within grid layouts when applied it shows the default mode (26 columns). When in reality it is actually 24 columns, if you then detach the style it shows the correct number. And when detached you can see it shows the correct value Seems this was a major oversight, as it makes applying size variables pretty time consuming, as I have to check if I’ve chosen the correct size by clicking and opening up the variable list. In short it seems to default to the first default mode, instead of respecting the chosen mode. It also only seems to affect styles. Anyone else found this to be an issue?

I'm seeing an issue where publishing a Make Kit removes the component exports from the package root and creates an effectively empty JavaScript bundle. This worked in earlier versions of the kit. EXPECTED BEHAVIORComponents exported from src/components/index.ts should be importable from the package root after publishing. ACTUAL BEHAVIORAfter publishing:• dist/index.js contains only:/* empty css */• dist/index.d.ts contains only:import './styles/index.css';• Imports from the package root fail because no components are exported.The generated src/index.ts contains only:// Auto-generated entrypointimport './styles/index.css'; REPRODUCTION1. Export components from src/components/index.ts.2. Add the following export to src/index.ts:export * from './components';3. Publish the Make Kit.4. Inspect src/index.ts and the generated dist files.5. The component export is no longer present, and the root JavaScript bundle contains no component code. I ALSO TRIED• Creating a separate barrel file• Editin

Importing SVG created in Adobe Illustrator 2026 to Figma doesn’t work. SVG created in Illustrator 2025, with same settings works just fine. 

I’ve already started using the new slots and I find them amazing, but I think it’s very limiting to prevent the use of grid layout. 

Hi everyone,I'm having trouble deleting some token groups/collections from my variables panel and could use some help.As you can see in the attached screenshot, I have duplicate groups like 03. Spacing, 04. Viewport, 05. Border, etc., right under my 00. Core color line. However, the option to delete these groups is completely missing or unclickable.Has anyone encountered this specific bug or lock state? Is there a way to force-delete these groups without breaking the rest of my local variables?

I was reading the SEP 30, 2026 release notes which says audio support has been released. https://www.figma.com/release-notes/?title=motion-adds-styles-audio-animations-lottieI have updated my figma desktop and still can’t seem to drag mp3 or wav into the figma timeline. I get the error Files failed to import…File format not recognized or failed to convertaudio.wav

Hi Figma Support,I'm experiencing an issue with publishing new components to a Figma library.I've added several new icon components to our library. They appear correctly in the Publish library window with the “Added” status. However, when I select them and click Publish, Figma shows that the publishing process has started, but it never seems to complete.There is no success message and no error message. When I reopen the Publish library window, the same components are still listed as “Added”, and they are not available as published library components.I've already tried:Publishing all components at once Publishing only one component at a time Deleting the affected components and recreating them from scratch Publishing through the library updates/publishing interface Reopening and restarting FigmaSome components from the same file were published successfully earlier, but most of the newly added components are now affected.I'm using the Figma Desktop app, not Figma in a web browser.Could y

 Currently, when viewing a prototype in Figma, it would be very useful to have Back and Forward navigation buttons, similar to those available in web browsers.These buttons would allow users to navigate between previously viewed and next prototype screens without needing to restart the prototype or manually navigate through the flow again.This feature would be especially helpful when reviewing multiple screens, testing user flows, and presenting designs to clients. It would make prototype testing faster, smoother, and more convenient.Suggested functionality:Back: Return to the previously viewed screen. Forward: Move to the next screen in the navigation history. Enable these controls directly in the prototype preview.Adding this feature would significantly improve the prototype review experience for designers, developers, and clients.

Hi Figma community 👋Our team manages a shared design system that is actively evolving, and we frequently update components to improve usability and consistency.One challenge we often face is tracking component updates across project files. While Figma provides version history and “Compare with previous versions,” identifying changes requires opening each component individually. This becomes especially time-consuming when updates affect many components or multiple screens.It would be extremely helpful if Figma could provide better visibility into component changes, such as: Notifications when a referenced component has been updated Visual indicators showing which components have changed A clearer diff or change log for component updates This kind of functionality would greatly help designers, PMs, and developers understand whether updates require action on existing designs.Curious if other teams managing large design systems experience the same challenge? How are you currently hand

Sometimes when working in figma I accidentally click the AI-stars. How do I hide this popover without typing a prompt. It is in the way and I never seem to be able to get rid of it...

DescriptionWe are experiencing an issue with icons inside components when switching between states.Our use case is an icon that (example):In the default state is not filled and uses color #FFFFFF. In the selected state becomes filled and uses color #000000.When creating the component, we initially use a specific default icon, and the color and fill behavior works correctly across the variants.However, as soon as we swap/change the icon to a different icon, the selected-state properties are lost:The icon no longer becomes filled. The icon color is no longer changed to the state color.We have also tried alternative approaches, such as applying a variable that forces the icon to be filled. With this approach, the fill behavior works, but the color property is lost when changing the icon.Expected behaviorWhen swapping the icon within the component, the icon should preserve the properties defined by the component variant:State X → unfilled + color X State Y → filled + color YThese propertie

Hi all,new org admin here, so bear with me. I have trouble organizing the users in my instance to specific teams and user groups. I do plan to use groups for SSO config, so will add groups to team access. What i am really missing, is there a way to see specific user membership in team and/or group without exporting csv? Like when you click on one user details, you should be able to see which Teams user has access to, additionally, imagine having the info, on the type of access for each Team.

Hi Figma team,We're setting up Code Connect for our design system and the MCP preview in the Code Connect UI always shows "Can't generate MCP preview right now. Please try again later." It happens on every connected component.Our setup:- Code is hosted on a self-hosted GitLab instance (gitlab.atida.com), private repository.- Components are connected at the component set level from the Code Connect UI, using the GitLab file URL (e.g. https://gitlab.atida.com/<group>/<project>/-/blob/main/src/components/Button/Button.tsx) and the exported component name (Button).- We also published parserless Code Connect templates for the same components.- The components show as "Connected", and the design context returned through the Figma MCP server includes the connected component correctly.- We tried removing the local file-path connection and keeping only the GitLab one: same result.Questions:1. Does the Code Connect MCP preview support self-hosted GitLab repositories, or only repositor

Last weekend I was able to prompt the AI agent in canvas to create a prototype, with basic interactions, right on my file. Today, the chatbot says it can’t add interactions, and I have to do it myself, or use Figma Make. Is this a bug or a feature? Figma Make creates prototypes but when copying it to your Design file, it only copies the UI and not the interactions created. Could you let me know if this is a feature so that I can move on to Claude Design for prototypes?Thanks!

I have been encountering this issue for I do not know how long now, likely a year or more.Whenever I have a master component with different properties, for example a tab set with multiple tabs inside it (in this instance those are also individual components), which can be set to “idle” or “active”, which includes a color change.When I update something about the master component, such as removing the presence of an icon from each tab, the “idle” (default) states of the component instances will update and the icon is removed, but the “active” (non-default) instances will not update. The icon is still there.I encounter this most often with text, such as a message or alert component, where I change the text on the master, but for any non-default states of the instances, the text will not update. I have to reset, which returns every property to default, and then adjust all my properties again. Or manually update the text, which means it is now “custom” and will never automatically apply cha

Hello Figma Team,I just subscribe to collab for 1 year subscription but when exploring the Figma i accidentally clicked Dev in which i dont have plan to subscribe to dev mode. And now i am gonna be charge $113 as per billing.Can anyone help me cancel that?Thanks-Ricky

Issue Summary: My monthly quota of 20,000 Figma Make credits reset on October 2, 2026. While running routine, standard prompts with over 19,000+ credits remaining, my entire balance abruptly plummeted to zero.A total loss of 20,000 credits in under 24 hours is mathematically impossible under normal operations and far exceeds my typical monthly usage. This is an unmistakable system glitch that has completely blocked my workflow.Required Action: I require an immediate audit of my usage logs and prompt history to identify the system error, along with a full restoration of my depleted credit balance, or just fully refund my payment. Your support is painfully slow and unhelpful.

My attachments are not being seen by the program so i can't add attachments even when a thumbnail of my attachment shows

Hello Figma Support,I am reporting a possible prototype bug affecting an interactive component nested inside another component.By “language selector,” I mean a control on the right side of a website header. It shows the current language as a flag and a short code, such as EN. Hovering reveals an arrow, and clicking opens a vertical dropdown below the control, containing flags and other language codes, such as DE, FR, and IT.How it is built:The selector is an instance of its own component set. Its closed, hover, and expanded dropdown states are separate variants. The dropdown is part of the expanded variant.The relevant interaction sequence is:- Closed state, 131 × 52: Mouse enter → Change to the wider hover state.- Hover state, 170 × 52: On click → Change to the expanded dropdown state.- Expanded state, 240 × 274: Mouse leave → Change to the closed state.These transitions use Smart Animate with Ease Out, approximately 150–200 ms.The selector sits inside layout frames within the Header: