Report a Problem

So I have Inner and Drop shadow effects added to a shape but the effect doesn’t show when I go to make show my design in Prototype mode? Does anyone know a work around to fix this. This is what the image is supposed to look like. Image should be transparent in the middle. When going into prototype mode, this is what appears.

We have logos in a library file, as well as headers and footers in another library file. The headers include instances of the logo component. We use variables to determine which logo variant is loaded into a header. When using these headers in design files, we find that the logos intermittently load or not load. Is there a Figma loading issue for library images that is occurring? Very frustrating! We had a feature working we thought, and now when stakeholders look at designs, the headers are missing logos. The instance is in the layers tree, it just does not show. To get it to show, sometimes changing the variable to another brand will load the logo in the header within the design. Great, but then as soon as you reload the design file or someone else opens it elsewhere, the logo is not visible again. This is a bug as far as I can see.

Hello everyone, recently we have noticed strange behavior of interaction areas in some prototypes. For example, it happens more often that interaction areas of a button are no longer on the button itself after scrolling in the prototype, but are moved somewhere in the prototype. As a result, the prototype can logically no longer be used as the buttons are no longer clickable. In the attached image you can see the highlighted hotspot box of a button floating somewhere in the wrong place. Does anyone have similar problems and perhaps an idea or solution as to why? Cheers, Sven

I just rolled of a contract project, and Figma’s handoff sucks. I request to better automate and cascade user permissions. Situation: My fellow designer Winnie was taking over my design work I was rolling off from. As part of the transfer, first I made Winnie the Admin of the parent team. BUT as Admin, they did not have edit rights that cascaded down in to the sub-projects and files. Then I made Winnie to full Owner of the parent team. BUT even as the team owner, they were blocked at an at-team level for each sub-project. AND Ownership didn’t cascade down into the sub-projects. As a bug-report / feature request, my expected behavior would be: If a team member is elevated to Admin of a team, or Owner of team, that cascades down into all sub-projects belonging to that team automatically. Thus granting at least edit capability for Admins, and automatically makes the new team Owner the Owner of all sub-projects unless some manual override is done. BUT actual behavior is: Promote team me

Since the recent updates, the autolayout frame resizing functionality has been experiencing issues. Specifically, when switching between horizontal and vertical orientations, all child layers are reverting from their intended “fill” or “hug” behaviors to a “fixed width” constraint resulting in the inner layrs no loner being responsive. This unexpected change in layout behavior is causing disruptions in the overall design production. See Video for example

Nested components are not resizing when the tokens change. When they are not nested, it works well. Do you know how I can fix that? Thank you!

Hi guys, Why is the SAVING TO CLOUD icon near the avatar never go away sometimes? I do have a big file and sometimes I change something tiny and all hell breaks loose. Performance plummets and the SAVING icon and snackbar are always there. Why? How do I fix this? Please don’t roll out new features before fixing bugs, it’s really annoying. My job is to design, not to debug and find bug workarounds. Thank you kindly, Chris

In my main component, I have a state-layer, which has an auto layout applied to it. The frame inside is not absolute positioned. When I jump to my Instance, suddenly the frame is positioned absolute and i can’t change anything about it. This leads to a false behaviour of my components. I guess it’s a bug or am I missing something?

Hi, I’ve noticed that the comments aren’t moving along with the frames in Figma. I have to manually move them each time. I’ve tried closing and reopening Figma, but the issue persists. Is there a way to fix this? Thank you.

When working with complex nested layouts, especially auto layouts, I routinely need to move things around, add children to frames, or rearrange elements on the page. As such, I may end up copying elements (components, frames, etc.) onto my clipboard. When it comes time to paste the element, I can traverse the layers panel to find the parent container where my pasted element should appear. Once I select that parent node in the layer panel, when I paste, the element will appear in a predictable place - as the last child of the node I selected. However, I often need to add a component from a library. I usually do this through the resources toolbar (Shift + i). My expectation is that the inserted component would follow the same logic - inserted as the last child of the node I selected in the layers panel. However, the placement of the inserted component seems random. Sometimes it appears as a child of the element selected in the layers panel, other times it’s inserted into seemingly random

When my app is not in full screen mode the mac controls (close, minimize, full screen) sit on top of the tabs I have open. See screenshot. I am running the latest version of Figma.

I used to be able to hold Option in Design Mode and see the measurements between items that were selected and hovered on. This is a huge timesaver for me and my design workflow. I hope this is just a bug in UI3 and that it is not planned to be removed.

The latest Figma after config, no longer hides the selection rectangle when adjusting the stroke. So you cannot see what the stroke adjustments are. One of the top features of Figma from day #1, was you could see what you actually were adjusting. Notice the blue selection rectangle? How am I supposed to see the stroke while adjusting opacity? I have to guess 😦

Is anyone having trouble using the Figma app? It stays forever on this screen for me. I already tried restarting my iPhone, reinstalling the app and logging in/out, any ideas how to fix it?

I believe this is similar to a bug reported here: GIFs not available in the API - #5 by Gleb I’ve also highlighted it in the Figma Developers slack here: Slack Reiterating it here for ease of context. I’ve recently discovered a bug where where existing gif content isn’t being detected as a gif, and they do not play in prototype mode. I’ve managed to successfully reproduce 3 different scenarios for this bug: Copy the source asset (it was previously detected as a gif, but now is an image) into a fresh file + frame. It is detected as a gif, and plays as a gif, as expected. Copy the source asset into a fresh file + frame. Paste the asset in, again. First target is detected as gif, second target detected as image. Both play in prototype mode (consistent with the UI bug reported). Following up from scenario 2, if the FIRST TARGET is removed, the second target no longer behaves as a gif. Same issue happens when it’s done programatically with createImage , whether it’s with a new fill or a

I’m not quite sure where to put this, but sometime yesterday afternoon (26 July), I lost connection to Figma. Although I could see my file when trying to preview it, received an Error 500: Internal Server message. Since then I have not been able to export/import SVG files that has a gradient layer (completely fine before). On trying to import an SVG file with gradient layer, the error message received is “There was a problem importing your SVG asset because it contains invalid SVG markup”. On following the link to suggested ways to resolve this issue - none of the listed applies. If I remove the gradient layer, either as an effect directly on top of an image, or a separate layer - the SVG exports and imports with no issues. Any suggestions?

Hiii 👋 first-time poster here! I’m experiencing green lines resembling wireframes or bounding boxes across different projects since I started using UI3. These lines overlay the design elements and do not disappear, persisting across various views. It seems to be a graphical bug, and I’m unsure how to make them disappear.

In the new ‘Ready for dev’ focus list/view clicking on the context menu on ‘Show on page’ does only jump to the page the ready for dev element is in but does not focus it. In general this focus list is pretty useless because as a non dev mode user there is no search bar, you can’t collapse the sections, you have no folders, clicking on the screen give me the damn ‘request dev mode’ popup all the time like I got it…you want to sell me a feature. The fact that we do not have simple folder like structures to hand off screens to the devs in a basic but free version is really killing the momentum for adoption in our company. So in short: Fix the bug and make clicking ‘Show on page’ really focus on the selected element Finally create a folder like handoff system where I can drop elements in and order them in different categories alowing me to share folders for certain parts of a project to our devs

Is there any solution to the following problem? When I import an svg from illustrator it loses its stroke and is divided into two shapes, one is the fill and one is the stroke. I would like to be able to import the shape with the editable stroke as created in illustrator. I attach screen below. Instead, I would like to have a shape like this automatically when I import the svg into Figma.

I’m only using AAA components in a file. When I search for components in the toolbar, I find components for BBB components. I think this confuses me. (AAA and BBB are both in a team project.) In the example below, I searched for [Status], and this component exists in the BBB component (my file does not use this component), but the search results showed this component. From the search panel, I selected the AAA component (this component is used in the file), but no results were found. Hope to fix this problem. Results found for the BBB component（This component is not used） Not found in AAA components Put the result in a file and display it as coming from the BBB component.

Before the latest update I frequently swapped nested instances by: Selecting the instance Opening the instance finder Press OPTION + ENTER to replace selected instance Now after the update, the OPTION + ENTER shortcut does not seem to work for me. Instead I work around this by instance drag and drop or right click menu, which seems less efficient to me. Has the shortcut changed or is this a bug? Thanks in advance

Hi, I’m having an issue when I scale a component. One part of the component moves outside of the frame and causes it to go outside the background. This only happens for some of the variants, which is annoying since I have no clue what is causing the problem. I guess the frame needs to be fixed because it’s not a specific size, such as 23, 24, etc, and shouldn’t be 23.5, 24.8, etc. If you know how to fix this issue, please let me know. Specifics: Figma(Latest Version) Macbook Pro MacOS Ventura

Hey guys, Just wanted to report a bug, maybe new users do not know about this feature, which is very useful and they will miss it. When hovering the variant name, the “3 lines” dragger thingie which allows you to reorder the variants is not visible. It only gets visible when you actually hover it, but that’s pretty much useless. Users who don’t know about this feature will not notice it.

Background I have developed a plugin to import and export Local Variables. So I tried to run the export on a Figma sheet that already had Local Variables set up, and got an unexpected error. See the example code below. Problems The format of the value obtained by variable.valuesByMode is { [modeId: string]: VariableValue }. For example, a value like { '522:0': {r: 1, g: 1, b: 1, a: 1}, '522:1': {r: 0, g: 0, b: 0, a: 1} }. I wrote a process that changes this key to the mode name. For example, a value like { 'Light': {r: 1, g: 1, b: 1, a: 1}, 'Dark': {r: 0, g: 0, b: 0, a: 1} }. Light and Dark values were taken from collection.modes. However, one variable returned an unknown third modeId. The program crashed because of a modeId that does not exist in collection.modes. In other words, I have reached the inside an if statement in the following code. Example Code const collections = await figma.variables.getLocalVariableCollectionsAsync(); const collection = collections[0]; // Assume a colle

I created a branch as usual, asked for review, got approved, and now instead of the “merge” button it says that I must have editor permission to merge. Which is odd, because I created the branch and everything, I obviously have editor’s permission (I even went to check if I did). I had to ask a collegue to merge it for me.