Report a Problem

limit until 7 jun 2025, but it is 7 jun 2025 and still unwork

@Junko3 This issue is still persistent today. Actually there’s 2 issues here, depending how the component is built: Firstly a nested component that uses slots loses any override when using variables, this is not the case when changing from UI For components that have nested components in the master pre-made, without using placeholders, it is not possible to use DIFFERENT variables if the variant property is the same. In my example the blue instance has a light and dark variant. The property name is “blueProp”. Because the blue instance appears twice in the green component, the “blueProp” also appears twice in the nested component panel. See attached video for these 2 problems. Master with pre-nested instances: No problem while using UI Same setup but I cannot use different variables for different nested instances Master with placeholders / slots: No problem while using UI Using variables breaks / loose overrides I can provide the file if needed. Test with Figma Be

Hi, why can I not change the shape of a picture anymore freely without using a mask? It was so easy to do before, where did that  design option go? I would really love to use it in THAT simple manner (not masking pls) Also can we turn back the previous UI maybe?

I just upgraded to Profesional (full seat) so that I can, among other things, take advantage of the video feature — adding one to the workflow — and despite FIGMA taking my money and my profile now showing the blue “Professional” badge, the feature is NOT working. It’s still saying I need to upgrade. I tried the browser version and refreshed that at least 12 times, closed and re-started the desktop app at least 6 times and finally shut down and re-strted my Mac once...NOTHING! Worst of all, I submitted a support ticket (##1380952) and when completed, it showed me a summary at the end that said “Status: solved”. How can it be solved without anyone even looking at it or contacting me. So you take my money and then instantly tell me that my problem is solved? What a complete RIP-OFF! 

I’m struggling to configure projects in a way that lets Figma keep components synced between designs and the design system without destroying its performance. Is there any way to improve Figma’s performance while working with components? I watched their video, and they didn’t mention anything about addressing this issue. It feels like we’re being pushed into a setup that will be costly to change later on.

 We have a library of tokens with subgroups.token has a scope setting (like text tokens shouldnt appear in the list when user tries to select background color token etc) Scope setting works however empty groups are shown in teh dropdown (see screenshot, border tokens are not available):This behaviour is pretty annoying! Can you please hide grouping when no items available in teh group. 

I've been observing a drastic drop in Figma's performance for some time now. To tell the truth, it's impossible to work because simply copying a frame takes a dozen or so seconds. I observe this phenomenon on both native and web app. I've cleaned the computer's cache, reset the Figma cache and it doesn't help! It looks really bad.I'm very happy that you're adding a lot of new things, but I have the impression that you're omitting performance, which is the foundation. Please take care of the fundamentals 🙏

How do I Go back to the old UI in Figma & Figjam ? There is no such an option?

Hey everyone,I saw that there has been quite a lot of related topics with this one, but most of them are a few years old, so I’m not sure if there’s a solution for this without any crazy workarounds… I have this icon where I’m working with multiple brands, so for this I’m creating a variant that will allow me to easily swap between those brand and also the variable mode. The issue comes when I’m using the icon from Brand X and change the colour from “fg-primary” to “fg-inverse” If I change the Brand to Z, the colour doesn’t remain “fg-inverse” and uses the “fg-primary” instead The icons have all the same structure  I want for the colour to remain the same when switching Brands. Is there anything I can do? Thanks in advance!

Create a group Add autolayout to that group Voilá! That group is now a Frame.There is no way this is not a bug so I reported it as such.

Heyy, I have a card component with an icon container that I would like to switch with an asset container. The icon container is a component with hug attributes. It contain an icon inside with a height defined with variable and a lock on aspect ratio.The asset container is a component with a width in hug and a height attribute defined with a variable. It contain an asset inside with a fill height and a hug width. I would like to switch the icon container with an asset container in my card.When I’m switching the instance, the sizes and height are broken. I would like the height of my component to have the default size of the swapped instance but it’s keeping the original component size. To be honest I don’t understand the behaviour and don’t know if I need to built my component differently. Thanks ! I added a video explaining the behaviour   

Hi, everything is in the title,by release, i mean when executing the public plugin which is available to everyone,and by development, i mean my local copy.I have tested it on the exact same file and conditions, so i know it’s not related to something else.Do you know about that ?What could be the possible reasons ? It seems to be the case in any context, in development, a complete re-render of my algorithm would take 0.5 to 1 sec in average, and it takes from 2 to 3 sec in release.For context, my plugin is  :https://www.figma.com/community/plugin/1504087347056471789/10x-html-design-to-clean-responsive-code-10x-fasteran HTML exporter that runs vert fast,It is a big problem because my plugin shows a preview which allow for a WISIWIG live editing that has to re-render everything at every changes, and it’s only nice to use if the refresh time is below 1 sec.Thanks.

Hello, all the designs in Figma are showing the shadows incorrectly. This had been corrected and it is happening again. 

I am using material UI. I have a switch. I want to bring that switch into another component I’m making on a different page. Because of micro-interactions, material UI switches got like 4 states. I like them like that. Now… Those 4 states, in this switch are just for “lights off”; “lights on” has another 4 states. I don’t want to copy 8 instances into another page and then create a new component group that nests the OGs just so I can prototype this button behavior to do what I want it to do. @figmahelp; people… How do y’all deal with this. I have to be missing something right? I got my main component. I don’t want to assign attributes to it that aren’t universally applicable (change variable mode). Is there really no other way to manage this other than duplicate duplicate duplicate?

i cannot upgrade from my expired educational plan to a professional. i have tried everything i found googling stuff. i need help. I submitted a complaint ticket, here is the number: 1382307

Hey, my company’s social/ad template is set up with various artboards ready for export. But in the past week, ads that used to export as 300x600 are now 301x600 for example, which our ABM platform doesn’t allow.Is this caused by a figma update/glitch, and is there a solution? Thanks!

Hello everyone, today my Figma updated and now I can’t seem to find the old beloved “Layout/Autolayout” section, someone can help?  

In our company, we use font variables for our three types of branding. We build components using the font variables to make sure everyone uses the correct branding and components. Recently we discovered that - when resizing a component - the font variables are fixed to the branding of ‘Mode 1’. It can’t be switched back on, except when you Detach the Component. Is this expected behavior? Can it be looked at? 

My team recently transitioned from Professional licenses to an organization Figma Government plan. As directed, we exported our component library and design documents to local files, then imported them into our new account. Unfortunately, the components and variables in the design documents are disconnected from our design system component library. We’ve tried the Repair Component Connections and Repair Variables Connections commands, but they don’t seem to do anything. Is there a way to fix up these connections with recreating entire design documents?  

I am working on a library and some design files in parallel. Meaning, the library is not yet mature or stable, and updates are published very regularly. In addition to the ‘real’ updates, Figma keeps throwing in a bunch of ‘phantom’ updates for components that I havent’t touched.Plus, the ‘review updates’ preview thing is so slow that it mostly just never loads. I’m sitting on a pile of dozens of updates, some spanning back weeks, and I’m too afraid to just press ‘update all’ in case something breaks in my design, but it’s also impossible for me to go through all of these one by one because the preview never loads. And this whole problem multiplied by 6 files. Is this happening to anyone else? How are you dealing with it? I don’t know what to do.

Hi!Has anyone encountered this issue: some of our components had text properties so the text could be set directly in the properties panel. Some time later, we decided to delete these text properties. As a result, after publishing the library, in all instances of SOME components (not all, SOME), the text that was linked to the variable gets reset to the default. But this doesn’t happen in every component that had a deleted text variable.Is this a bug or expected behavior? Has anyone run into this? How did you deal with it?We have a large library used by 50+ designers, and what seemed like a tiny update that didn’t break anything during testing ended up resetting values to defaults in some components after publishing. 

Recently noticed that components search (Shift + I) results are a bit random.Sometimes before giving me the correct result, it shows a few absolutely different components that just doesn’t have any relation to my requested component’s nameAdditional info if it can help:Device: iMac M1OS: Sonoma 14.1.1 Figma: Desktop App version 125.4.9Searching components across different files/kits (our components each have a different published file)

Thanks for launching this new feature!I’m not sure if it is a bug, but I figured I would ask here. Let’s say you have a parent container, with a child element called “Instance A” with a width that is set to autofill width.When you swap out the Instance A (aspect ratio of 4:3) with another Instance B that has a different aspect ratio (16x9), and both components have ratio lock,  Instance A’s aspect ratio overrides that of the B’s.To me, this isn’t to me, the B’s ‘locked’ ratio value should take priority. (personal opinion)Now, there are two ways to restore B’s ratio.Right click into B, and reset. Resize parent container temporarily.  This will reset B’s ratio to 16x9.  And then you hit undo.#2 feels like a bug to me.But again, B’s locked ratio should take priority. (or give user control to set priority)Thanks!

Hi everyone,since we’ve used our branching/merging options in our Design System we are facing an issue, that keeps on giving the weirdest visual outputs.The issueWhen we merge a branch back into main, some frames appear to be smaller/larger than they actually are. Just last time, when we updated our icon collection and changed default size from 20x20 to 24x24px, some icons kept their visual appearance at the previous 20x20 after the merge. This is also weirdly reflected in the instance swap menu thumbnails for said icons.A similar issue, just reversed, has already been raised here:  How to fixThe easiest fix so far, that I have found, is to enter the affected frame, shape, etc., change width/height to some random number and undo the change immediately. After this, the affected object is corrected. Fun fact: Figma seems to know the correct size of the affected object as when you select it, it is displayed correctly, and retains certain information of when it was correct, such as box-sha