Report a Problem

Hi, I’m not able to view the MCP server integration option in the Figma Desktop app in Preferences on Mac ow Windows, I am a paid professional (full Seat), pls see screenshot, I have the latest version of the desktop app also, please advise what I may be missing?

I’m sure that the page is extended to include the entire design content of my pages, but when I publish, some of them are fully viewable and others I can’t scroll to the bottom of them! Sometimes it’s just a little bit, and other times it’s a good 200px worth of content. I’ve tried different browsers and it’s consistent across them.

Hi everyone, since the last update I’m experiencing issues with the copying of images into other frames. It seems like the image isn’t stored in cache. Does anyone know how to fix it? Best, Finn

Hello awesome Figma makers, I’ve just upgraded to a pro account with full seat, but do not see the AI option in both iOS app and browser. In browser, there is an icon which looks like AI, but it seems to be a menu navigator only. I’ve also enabled AI in the admin settings. thank you

Hi, I duplicated 2 files, a library and a design file. The new design file is obviously still attached to the previous library. I want to attach it to the new library. Everything is still exactly the same. I open the library panel in the new design file, add the new library to the file and detach the old one, then I click on “swap library” in order to replace components and styles in the file, but I get this error ID: ba6fb6fe90044b46a5917a85bf89e636. Did this happen to anyone else? If yes anyone found a solution? How am I supposed to swap my libraries if this doesn’t work, I tried more than 20 times over the week end.

Hi, I have this issue in multiple Figma files. If I move frames with comments to another page, the comments still appear on the original page whenever the file is opened. The comments only disappear when navigating to the “moved” page and navigating back. This is really cumbersome because often the page in which frames with comments are moved to is a very large page which takes a long time to load. Also, engineers who are working off of the original page get confused about the comments that were moved and are not relevant to them.

The recently introduced fill patterns do not seem to be correctly saved in styles: They are not editable (cannot select a new pattern object, and the toolbar does not show the pattern tab) When exported from a library, using them in another file results in displaying dots (presumably the default pattern)

I’m not able to select into the text layer to make text edits. I’ve read previous discussions from a few years where people have experienced the same thing. It might have to do with the mouse tracking speed change, but I tried adjusting that as well. Would anyone have updated solutions? Thanks!

Double-clicking a text layer won’t let me edit it. The layer is not locked. This issue seemed to be resolved in past for other users, but the solution has not been mentioned in the thread. I am first time coming across this issue. Please guide.

I have been using Figma Make to design my portfolio which was going great. Things I got done - Created a homepage Added Interactions Defined a visual design language As I am proceeding to drilled down pages further, I have noticed a few things : The images that were added previously are deleted / replaced by new ones - despite specific instructions to not do it. Slow speed : I also noticed that the typing speed of prompts slowed down as I proceeded further - cross-checked if it was a computer issue (which it wasn’t) It’s forgetting things! with every prompt & design updates, it’s now deleting the previous content + pictures :( all the hard work seems to be going in vain and I’m not afraid to touch the project in fear of disrupting the progress so far Can someone help me? Also, what’s the memory capacity of Figma Make? I noticed it was using Calude Sonnet so, assumed it should have been good. Am I missing something here?

When using “Undo” I want to undo changes not “clicks” or selections. Yes, this is addressed in several threads, but this is one of the reasons Figma is so frustrating, that I seriously considers changing job to a company NOT using figma. Funny how a UX design-tool can have a terrible User Experience. Question: Will and When do we get this fixed?

Material theme builder version 20, released in May 2024, is not operational. The plugin generates theme colours but does not update them in any project files other than the original kit project. This means that if you had any work using Material 3 kit, you are not able to update the theme since May 2024. It is not possible to do any theme-related M3 work with a custom theme since May 2024. Themes in any project that people had done in Material3 UI Kit cannot be updated anymore since May 2024. There is no other Material theme builder plugin. We are hostages of the situation. There are tens, if not hundreds, of reports on the M3 DK page and on the Theme Builder itself page where it has been ignored since early 2024. It appears that version 20 of the plugin was released untested, and the development team was immediately reassigned or disbanded. Nobody from the Material team reads bug reports; nobody responds. Figma announced the category of UI kits but did nothing else; nobody tests anyth

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, please try

I’m getting the following error- We can't open this file because we're having trouble with WebGL. Please try restarting the desktop app. If this problem persists, your graphics card or driver may not be supported. This happened after updating Figma. It works perfectly on different browsers but the desktop app isn’t working. Are there any fixes for this?

Hi! I’m testing a site built with the new Figma Sites feature. I’ve set the top navigation bar as a sticky element and made sure it’s positioned at the very top of the layer tree. In the Layout panel, canvas stacking is set to “First on top.” Canvas stakcking settings It looks fine on Figma and Chrome(desktop & laptop) On Safari and mobile browsers, the sticky navigation bar appears underneath the hero section content, even though it’s set to be the topmost layer in the design. On Chrome (desktop & laptop): everything works as intended — the GNB stays sticky and always remains on top. On Safari (desktop & laptop) and all mobile browsers (Safari & Chrome): the GNB is sticky, but appears underneath other layers and is partially or fully hidden. Is there a workaround or fix for this issue? Thanks in advance!

I'm experiencing an issue with the brush tool in Figma's drawing environment. I have a simple drawing tablet with a pressure sensor. When I was drawing, I noticed that the stroke was responding to pressure – the harder I pressed with my pen, the thicker the line became, which was great! However, this functionality suddenly stopped working. Now, no matter how much pressure I apply, the stroke remains uniform. Has anyone encountered this problem before, or does anyone know what might have happened or how to fix it?

Since the last Figjam update on the Ipad app, I cant see which color is selected on the pen/highlighter/etc.

I’ve made a flow diagram of a simple user task, i’ve adjusted the connectors to better fit the layout and available space. I then wrapped it in a section component and pressed the hotkey to resize the section to fit the flow diagram. However, when I do this, it always changes the positions of the connectors which i then need to adjust again. This usually happens when I move the connectors from their default. Attached a before and after: For a simple diagram this is annoying but not a big deal. but for a large, very intricate diagram … this is a nightmare

Dear Figma Team, There is a problem that is causing me a lot of trouble lately… When I add drop shadow on top of an outside stroke with no variable the drop shadow start after the stroke. The problem is that when I add a variable stroke width, the stroke goes above the drop shadow 😫. There is 3 diffrent behaviors for the exact same frame and same shadow. See screenshot attached It is really jeopardize a hard deadline for me , please help… (PS : the shadow is raw number so its not an interaction between 2 variables of the same mode in case you were wondering)

When I export a frame or component at any scale factor (@2x, @3x, or custom), Figma sometimes adds an extra 1 pixel to both the width and height. For example: A 100×100 frame exported at 3x should result in 300×300, but instead, I get 301×301 or 300x301 or even 301x300 . This does not always happen, but when it does, it's consistent across devices and files. Affects both PNG and JPG exports, regardless of pixel grid alignment or stroke presence. 🛠️ Workarounds I’ve Tried (with partial success): Creating a new frame, copying content into it, and exporting again — occasionally works. Manually scaling the frame by the desired factor (e.g., scale by 3x), then exporting at 1x — this consistently avoids the 1px error. However, these are not ideal for batch exporting or asset automation.

I'm encountering an issue with the Variables API endpoint when attempting to export local variables. The endpoint returns all remote variables from shared files, making it impossible to export only local variables. Current Behavior: The endpoint returns all remote variables from shared files Unable to filter or export only local variables Receiving a 400 error with "Request too large" message Error Response: { "status": 400, "error": true, "message": "Request too large. If applicable, filter by query params." } Technical Details: The error message suggests using query parameters for filtering However, the endpoint documentation doesn't list any available query parameters The endpoint lacks pagination capabilities This limitation makes the endpoint essentially unusable for files with many variables Expected Behavior: Ability to export only local variables Support for filtering variables (local vs. remote) Pagination support for large variable sets Impact: This issue significantly impact

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