Report a Problem

If you go to the Edit variant property panel and try to grab one of the variants at the bottom of the list and drag it up, you will sometimes get the grab icon appearing in between items: Example of bug 

We have a design system with 3 variable modes for brands, this includes different colors and fonts for each brand. If I have, for exemple Component - Variable Mode Brand 1 (Default) and  Component - Variable Mode Brand 2, and I try to resize them using Scale (K) (either together ir individually), the following happens: 1. Component - Variable Mode Brand 1 (Default) keeps it's font family2. Component - Variable Mode Brand 2 changes the font family to the default used in Variable Mode Brand 1 The same thing happens with a third component using Variable Mode Brand 3. Here is a GIF I made from a video of me having this issue:   Any configuration I am using wrong?I do have all fonts installed and can change text and do anything else with them without having this problem. I do believe it's a bug. While this doesn't stop my normal workflow of designing screens for handoff as we never resize components, we sometimes need to this for some internal documentation to better illustrate or focus on

When I set my preference to have the zoom controlled with the mouse wheel, rather than the mouse wheel scrolling the view vertically, it works briefly, but then reverts to the original behavior. The preference selection still shows the new setting, but the web app is not honoring it. If I turn it off and on again, it works again...and then doesn’t. Dev mode and design mode.In Dev mode, it works until I use the center-mouse button, instead of the left mouse button, to pan. In Design mode, the left mouse button and drag selects, so I only use center + drag to pan. In that mode, the wheel zoom works until the first use of the center button. Changing modes resets things to the expected state (temporarily). 

In a plugin, I’ve got code that’s trying to apply and instance swap property to particular node in a component.The code is  const prop = Object.keys(this.componentSet().componentPropertyDefinitions).find((key) => key.startsWith("Peek view#")); if (prop) { try { const newRefs = { mainComponent: prop, }; console.log(newRefs); peekView.componentPropertyReferences = newRefs; } catch (error) { console.error(`Failed to set peek view property reference for ${prop}:`, error); } }This generates a log message showing that (I think!) the new property references are correct:{ "mainComponent": "Peek view#208:0"}But the assignment fails and throws this exception:{ "message": "in set_componentPropertyReferences: Could not create a new component property reference."} 

I have vector shapes selected. When typing “subtract” in the Actions search field, the action doesn’t show up in the list of options. When typing other vector boolean actions, like “union” or “intersect”, they do show up.This occurs in both desktop app as well as in the browser. Subtract would show up in the list of Action options in the previous version of Figma. 

Stroked elements (such as form fields) are not working in fill containers in responsive prototypes. The issue started on April 8th.

Hello Figma Users, I am Lead designer and while designing the product in figma I found glitch that there is no proper syncing between the library file and design file. Detailed description : I have created one main component in the library file and I published the library without any error and now there is no more any changes in library file and publish button get disable because everything in the library file has been published. Now when I am in the design file, I couldn’t see any pending updates in the design file because I already updated the library file into the design file so there is no more pending updates however all the changes which I made in the component doesn’t reflects in the design file instance of that main component. I tried lots of ways to do, I spent lots of time even though I couldn’t find anything. I tried to quit figma and restart, changed the internet connection if there was any network issue, close the working file and reopen etc. Only last option is that I hav

The Problem When I am in the edit mode of an annotation and try to click the more actions icon (...) to access the more action menu, no menu appears. It doesn’t matter if it’s an existing annotation or a newly created one, the menu won’t appear when triggered. When annotations was first released I remember being able to access the menu. Now it no longer works. To ReproduceLocate an annotation or create a new one. Once located/created, double click the notation to activate edit mode. Once in edit mode, tap the icon that looks like an ellipses (...) to trigger the more actions menu. Screenshot of menu icon within annotation edit mode. Completed troubleshooting stepsQuit and restarted figma Turned off rulers and other guides/effects Platform: Desktop App 125.4.9OS: Mac 14.7.

I created a file for work, there were my layouts. As a user, I was in a corporate team, and after leaving this team, my personal file disappeared, which was not inside the corporate Figma. I search for it by name, I search in the list of deleted, and it is nowhere. How can I restore access to it? I tried to return to the corporate team to find the file, but this did not give results, it simply does not exist. Although I remember its name exactly, I can not restore it. I once had a similar situation when a file disappeared after leaving corporate mail, but then I had a link to it and could go in, but now there is no link, and how can I restore access to it? I tried the option when I rejoined the team in Figma, but this did not give a result.

Hi,I need to update some details on my widget, but I'm encountering an error in the Advanced tab of the edit popup. However, I can't find any visible issue there—there's no red highlight or alert to indicate what's wrong. 

Hi! I first had this problem today, with designs that previously published correctly: center-aligned frames are publishing as left-aligned divs. See example below showing (top to bottom) 1) Previewing page within Figma Sites, 2) Autolayout settings, 3) Published page as displayed in Chrome  

Hello,I'm writing to let you know that I just launched my online portfolio, and two people using Safari are experiencing issues accessing the site.For them, the site loads poorly and keeps reloading in a loop. Everything works fine on my end, but both of them had the same issue—one on a computer and the other on a phone. Another person tried it on a tablet (also using Safari), and it worked without any problems.Since this is my portfolio, I want to make sure that everyone can access it properly.I'm sharing the link with you: https://www.claramistou.frThank you very much for your help,Clara

Hi all,Love the new figma Buzz feature.There two things I’m missing currently:I’m working with a CSV with variable fields - some contain content, some don’t. But when importing a csv sometimes the empty cells aren’t recognized and Buzz still adds content to it. If there are multiple empty cells; only the first one is left empty, the rest is left untouched. The other thing is this: I would like Buzz to remember which fields are linked to which column/row - now when i run into an error I have to reupload the csv file and link every field again. If I miss one and the import fails, I have to start all over again - allowing for a similar mistake again. Would be amazing if Buzz could recognize the column titles and remember these, spot differences. An extra feature request would be to be able to hide or show layers based on content in a cell: i.e. if the cell contents are /hide to hide the entire frame. This is a feature in the free Google Sheets Sync plugin, which is an amazing amazing free

Here’s the feedback content: When using a plugin API to retrieve the font size of text within an instance, the value obtained is 24 before selecting the text layer. However, after operating to select this text layer, using the same method to retrieve the font size yields 12. Could you please explain why this discrepancy occurs? This issue affects the consistency of font size data retrieved by plugins before and after layer selection, which may lead to unexpected behavior in plugin functionality. Your clarification or resolution would be greatly appreciated. 

Hi Figma Team,I encountered an issue where the Export button on the right corner is not functioning. When I hover over it, the cursor changes into a text cursor (I-beam) instead of the usual pointer, and clicking the button doesn't trigger any export action.This behavior is unexpected and is affecting my workflow. Please let me know if there's a workaround or when a fix might be expected.Thanks for your support!

Hi! In design mode, when I select an object with a Move tool (V) and then click K to select a scale tool, scale factor input field is already in focus and I can quickly scale whatever, for example, by pressing K + ½ + Enter.How it works in Design mode after I selected with Move tool and clicked K onceHowever, when I tried the same in Draw mode, it didn’t work as a scale factor input field is not put in focus right after I click K button and thus I need to click K again to get this field focused.How it looks in Draw mode after I selected with Move tool and clicked K onceIs it supposed to work this way or is it a bug? Thank you in advance!Best regards,Kadir

When typing in Japanese and trying to go back to edit in the middle of a sentence, the cursor jumps to the end of the line. It’s frustrating because you have to delete the misplaced text and then manually return to where you were. The only workaround is typing the correction at the end, and then copy-pasting it back into place — which is a huge waste of time, especially when writing multiple comments.Ref: https://x.com/ken_tbdz/status/1790201098558407013Also, although I couldn't record it, there’s another bug where the whole text gets duplicated without line breaks. Again, this messes up formatting and forces you to spend extra time cleaning things up.I understand Japanese input might not be a priority, and maybe this only affects Japanese users — but please please please fix this. It’s seriously impacting usability. Thank you!

Hi, I would like to request refund,I was paying for my account from 2025, April 8th. And I found out I had another figma account, so I was paying for this account for 2 months, and I was not using it. Requesting for over 24hr refund, please let me know I can get refund or not.Thank you so much.

If you see the attachment, the annotations show up despte I am on Design mode. How can I turn them off? I clicked View menu and turned Annotations off, but they appear again when I logged again.

why figma getting slow. whether it is because of complex design components or any other reason.

After the most recent Figma update, none of my plugins are working.They either won’t open at all or just freeze when I try to use them.I’ve restarted, reinstalled, and tried both the desktop app and browser – same issue.Is anyone else running into this? Or am I just the lucky one?Would love to know if there's a fix?😭 

Today when I opened my Figma the top-bar colour changed on its own. 😡I’m using a light-mode theme, and I was happy with the black top bar.The top bar is not supposed to be grey, even in light mode, the contrast is terrible, and it looks like a UI from 90’s. Please fix this bug as soon as possible, this is unacceptable!  

프레임 추출시 오른쪽에 긴 선이 생기는 현상이 발생하고 있는데 모든 옵션을 다 적용해봐도 해결이 되지 않습니다. 이런 경우에는 어떻게 해야 하는건가요? 

Design Files and Presentations stopped opening on Desktop App for Windows. Reload didn’t help. Status - All Systems Operational 

Paste to Replace is no longer working properly as of a few days ago. It seems to be using Paste as Text despite using the shortcut and context menu options for Paste to Replace. Desktop app seems to be working as intended but I prefer the browser version if that’s still a viable option. In browser I have tried:Logging out/in Signing out of other devices Clearing browser cache, history, etc.Worst case I can switch to desktop app, just curious if I’m doing something wrong here.Thank you!