Report a Problem

Удалите эту парашу со страниц!! начните мониторить и фильровать что пишут люди !!!https://www.figma.com/design/42mNwme0cBfZwNZUIcN1mh/Яндекс.Маршруты?node-id=2-18586&p=f&t=xf8bXGFws0hQSksA-0 

hi there! I made some code layers and everything was working beautiful!after figma sites and make came out of beta, all the code layers started to glitch!Help! i tried to make a new code layer with the code and also glitching , what can i do? Thank you!  

When I select the guideline for the nudge, the entire canvas moves instead of just the selected guideline. The same issue occurs for both big and small nudges. I’ve tested this across the web and desktop apps, in new and different files, and even tried updating the preferences - but the issue still persists. can someone please help? 

For some reason there is one plugin that just won’t approve no matter who tries to approve it as an admin. Unsure if it’s a bug with Figma or the plugin itself. This is the plugin mentioned: https://www.figma.com/community/plugin/990910408295947511/lazy-load. Would like to see some resolution so we can try the plugin out for skeleton loaders mostly!  

I am having trouble with a keyboard shortcut, have any of them been changed?Ctrl +shift + K was opening up the window to insert media like images but no longer does so. Instead it opens a window to search or ask a question, anyone familiar with this issue, up until this point haven’t had an issue with any of the shortcuts. 

Unable to access figma ai toolset even in the paid plan. 

A various number of companies use the website brassring to host their jobs and upon submitting applications, the export version of the PDF file from Figma is old.brassring uses version 10 of PDF while Figma uses version 8. Upon submitting a resume on any company owned brassring sub-site, it just throws an upload error because of the version number.Can Figma update their PDF version so we can properly submit resumes without any issues?  

Hi all, I’m writing here to find some assistance or potentially a solution to a bug with figma design. After yesterday’s config announcements and updates on Figma App, I started experiencing extreme lag when copying specific complex components or pages/sections that include such components. My workflow includes multiple (Ctrl+C) copying commands and when I hit copy Figma freezes for about 20-30+ seconds (until it’s copied to clipboard). I didn’t have this problem before the update yesterday. (May 7) I tested everything - clearing cache, resetting the app, moving main components to different pages, trying figma in multiple browsers (I usually use the Windows App) - nothing works. The file has around 900+ variables and numerous main components. The memory usage of the file is at 14% and that shouldn't be an issue. I notice when I duplicate with Ctrl+D it works normally or when dragging a component to copy it while holding Alt, however just the Ctrl+C command makes figma freezes/lag and I

Hey Peeps,Right now my Figma Make is connected to one of my Supabase account which has two of my projects. But I have created a new Supabase account for newer projects, but Figma Make is not allowing me to disconnect the current integration and login or connect to another supabase account.Is this a limitation or can this be fixed with the current capabilities and features.​@Tom Reem Kindly help, ASAP!

Hello,I have a Lenovo X9, which supports Display P3 (checked on https://webkit.org/blog-files/color-gamut/comparison.html).However Figma displays this (even after a restart):   

When I add properties to a master component, I don’t see them show up in component variants. So, I can’t actually change or set their values. How can add a property to the master component and have it propagate to the variants? If that is not possible, how do I add a property to a variant? It seems I can only add a new property to the master component. why don’t I see all the other properties?? I’d be able to fix this error if it allowed me to change the properties I defined on my master component 

To make use of component properties better and reduce the no. of variants I tried creating my button with primitives which have 2 variants: Large: Icon size 20px (with instance swap), font style is button large (i.e. font size: 14px) Small: Icon size 16px (with instance swap), font style is button small (i.e. font size: 12px) Then I used this large variant to create a new component called ‘Button’ which comprises of all the different types (solid, outline, ghost etc) and states (default, hover, disabled etc.). Now when I take out a child of this ‘Button’, and change the properties of ‘Button’ first and then of ‘Primitive’ it works fine but when I have done this and try to change the properties of ‘Button’ again, then the icon colour gets back to primitive’s icon colour. I’m not sure what I’m doing wrong, I’ve kept the name of icons also similar as mentioned by @Molly_Hellmuth in this article for Icon Best Practices. For better understanding: P.S. If this works fine for you, plea

For the last two days I’ve been having this major issue where if I add a component that includes nested components from a library (via copy or from another file or directly from the library), the nested components are getting detached which isn’t a feature, even though it’s been requested as such.I’m experiencing this issue on Windows 11 (Native app, Chrome, Firefox) and Fedora 42 (Chrome, Firefox), with either old or new components created so it’s definitely something not on my end.I have to mention that this doesn’t happen if I use the nested components in the same file they were created.Anyone encountered the same issue? Thanks!

I'm trying to publish my website but this error keeps returning:Could you please help me resolve this ?

I made a Figma Make which is quite complex (more than 2200 lines of code in the App.tsx file) and now when I want to add or change something, the code stops during writing, Figma make reasons then goes back into a code writing loop and starts again like this... Sometimes after several reasonings it arrives at something but it loses all the work already done up to that point... Please does anyone have a fix to rectify this? I would really appreciate some help

Hello) I was creating my plugin for Figma Design with arrows from FigJam. Figma Design doesn't work with figma.createConnector() (this creation method is used in FigJam plugins), but I found a way to use them via template.clone(). These arrows are very handy for drawing Flow directly in the design.But today I found that the plugin gives an error and template.clone() no longer works for objects of type CONNECTOR.Can you tell me if this is a bug or is it an intentional ban? Because it affects the usability of my work.

I was working in Figjam and somehow made the UI elements gigantic. They are nonresponsive to zoom out, reset to original size buttons, and show/hide UI buttons. It is blocking and makes Figjam unusable - has anyone encountered this? It feels like a bug.  

Hi everyone, hoping someone here can help. I recently started using Make after googling “Figma Make” to begin a new project. Unknowingly, I was still connected to my former employer’s Figma workspace and created the file there. When I hit a limit, I thought I was messaging Figma support—but it turned out I had requested Edit access from the design lead at my old company. He declined (which I totally understand), and I received an email, but I still hadn’t realized I was in their environment. I finished the design last night and only discovered the mistake when I tried to share the prototype. I sent a Move request (thinking I could transfer it to my personal account), but he can’t see the request, and I can’t publish or get a shareable link. It’s like the request is stuck in limbo. Has anyone run into this before? Any advice on how I can recover or transfer the file to my personal workspace? Thanks in advance!

Publishing website in Figma Sites is unsuccessful 

In Present mode I like to keep the sidebar open so I can have the list of flows available at all times.Sometimes Figma auto-reloads my proto (in which case a toast at the top reads “Loading...”), but in the process it closes the sidebar. Once the proto has reloaded I have to reopen the sidebar manually every time.How can I solve this? Pretty annoying, adds friction to the workflow.Thanks!

in App on Windows: From time to time the commenting function locks up when an accidental comment is placed in the Commenting cursor. When try to exit the comment, the cursor locks up as moving hand and no more Commenting can be made. The App needs to be restarted to get out of the cursor lockup. It is often related to an accidental drop of comment in relation toa movement of the mouse cursor. Is this a known issue?

I've been experimenting with the new Figma Make feature and noticed a recurring issue that's affecting usability: After about 8–10 successful prompts (each 1–2 lines long), Figma Make starts rejecting any further prompt with the message: "Try again, with fewer inputs." This happens even when the prompts are extremely short, e.g., "Create a dark-themed button component" or "Add a CTA section with three buttons." I’ve tested this across multiple projects and browsers. The issue persists consistently, and the only workaround seems to be refreshing the tab, which sometimes helps temporarily — but not always. Additional Context: Even though Figma Make is currently laggy while generating prototypes (which I can overlook), this input rejection bug makes it difficult to iterate quickly or finish design ideas. It feels like a silent rate-limit or session exhaustion issue that’s not clearly communicated to the user.

Hello 👋,Our team is very enthusiastic about the Figma Buzz concept, we decided to try it out. I created templates, locked the layers that don't need editing, published them, shared them with my colleague and gave him editing permission. My colleague logged in but was able to edit every layer of the template, also the locked ones. And also if he uses that template in a new file. Could you help me find out what's wrong? Why Figma Buzz doesn't meet our expectations?In the first screenshot below, we see the layers are locked in design mode. And in image 2 and 3, we see the user the template is shared with able to edit the same layers, while in Buzz mode. I cannot find similar questions in the Forum. Are we the only team having this problem? 😔For now we've concluded that Figma Buzz's beta version is not sufficiently developed for our current collaboration needs. Because we did not experience the anticipated 'simplified editing experience.' Thanks a lot in advance!Marinske  

I’ve had 2 problems with using team libraries with Buzz so far:Adding the libraries You have to manually reapply every single style or variable that was updated in the library.The first problem is more of a frustration that shouldn’t exist. Why change the method of adding libraries? It just makes it harder to find and use. (“Asset view” shows templates you’re using, and what would be called an “asset” in every other Figma app is now called an “insert”!? It boggles my mind that at least one entire product team thought that was a good idea. 🤯)The second problem is a deal-breaker. For a product that’s focused on brand, it should as easy or easier to apply and update styles and variables. If there’s a button to trigger the mass application of library updates, it’s hard to find. If there is no way to trigger a mass update, that’s a huge problem, because not only do you have to keep track of what was updated, you also have to reapply all of those updated styles and variables to each affecte

We have a design which includes an Instance that has Variables applied to its width and height. We want to take the full design and scale it up by 1.8x using the K tool. However, the Instance will not scale-- it stays true to the Variable sizes applied to it. Is there a way to bulk break the connection to the Variables, or to override them, using the K tool? Right now, we have to find each and every layer which uses Variables and manually break them.(Interestingly, if we leave the Instance as plain pixels, set it to “scale, scale” and wrap it in a frame where the frame has the Variable assignments for the x and y, we can scale using the K tool).