We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
🎉 Welcome to the Figma Forum! 🚀
Find solutions, get advice, help others.
Hello Figma. This rotated svg does not satisfy the definition of absoluteTransform given by Figma. Here is a public Figma file including this svg. https://www.figma.com/design/zProXoGal9GMYLXSCyu7nX/svg-absoluteTransform?node-id=0-1&p=f&t=avPeqXZs3zNazPe3-0
When i place the overlay manually inside the frame, the prototype does not show me the overlay, but when i choose the other options they work fine, this is getting annoying as we need to position the overlay in the place that we want.
Me and my team is facing this issue where in Figma prototype screens, the pop-out options which comes when clicking on interaction type selector remains narrow. I have noticed that the narrowness is not random but rather dependent on the size of the object being prototypes. Here is how it looks like: Figma Interaction doesn’t open the pop-out window to it’s full width Is this a bug or a glitch?
I’ve noticed this issue for over a year, but it’s particularly bad now so I’m reporting it. Issue: If I try to use the color picker tool (either with the control+C hot key or manually by selecting the fill color, then clicking the color picker icon), then I do something else in Figma like type in a couple text boxes, then try to use the color picker again, it doesn’t work. Clicking it does nothing. Worth noting that it does seem to work if I use the color picker multiple times in a row without doing else in between. Things I tried: breaking components, using hot keys and doing it manually, updating Figma, restarting the app. No luck. My interim solution has been to refresh the figma page. But I need to refresh it literally every time I want to use the color picker, which is super tedious. (I’m creating a huge color sheet, I’ve refreshed my page literally 20 times). Context: I’m on a Mac, running macOS Sequoia 15.1.1 Using the Figma desktop app. Figma Desktop App version 124.7.4
Hello Figma team, Thanks for this beautiful solution. Just want to say that is in the title.
Firstly great job Figma Font variables are here!!! Figma tutorial: Variables for typography The only thing missing is the use of percentages in the line-height property. You can not use a percentage in the line-height as it only accepts variables that are a number type. Although the variables for line-height caters for pixel (absolute) line-heights (10,12,14)- it does not accommodate relative line heights. In other words you can’t use percentage variables for line heights that are a percentage of the font size (100%, 120%,150%). Interestingly …You can use a variable for letter-spacing ( which accepts a number variable - but reads it as a percentage) - the challenge remains that line heights by default are absolute not percentages - even though you can input a percentage. Percentages allow greater flexibility and less calculations Word around would be to allow formula in a variable e.g. =[variable] * 1.5 Or figuring out a way for the line height to be toggle between absolute or relative
I get these weird partial images below the component I have created for an interactive prototype. Can anyone tell me how I can get rid of them, and what they are? Thanks!
We have a “Media” component in our design system which assigns the aspect ratio to a property. Properties Aspect Ratio: 1:1 | 5:4 | 4:3 | 3:2 | 16:9 | 2:1 | 21:9 Orientation: Horizontal | Vertical When we create an instance of this component, resizing works and the aspect ratio remains locked. Using the Aspect Ratio property works as expected. However, if the component is resized, then the Aspect Ratio property seems to break. It will make the instance resize to an arbitrary aspect ratio based on the width of the instance and the height of the variant for said property. If you simply click the edge or a corner as if to resize it, the instance updates to the appropriate aspect ratio.
Why is placing images so tedious! It doesn’t have to be this way, Adobe XD makes it SO much easier to place images into a design file. For example you should be able to: Drag and drop images directly into a shape When manually selecting an image, the folder that opens up to select form should be the same folder that was most recently used in that file, so if I am placing multiple images from the same folder, I don’t have to navigate to the folder multiple times We should be able to select multiple images and drop into multiple shapes at once
Since yesterday the Figma to Framer Plugin no longer works, it freezes, claiming to be running. Turns out it works well on the web app, but not on the desktop version. A lot of users on the Framer forum are having the same exact issue. Anybody else here? Framer (who i guess developed it) have been notified, but no response (This plugin: https://www.figma.com/community/plugin/1037108608720448600)
Something went wrong Our team is looking into it now. If refreshing the page doesn't work, check our status page for updates.
When working on design iterations, I often need to create new versions of components by duplicating and tweaking existing ones. The problem? Simply modifying the original risks breaking existing instances across my designs. Right now, the workaround is: Create an instance Detach it Convert it into a new component But this is a lossy process—it strips away properties and variants, making it harder to maintain consistency and requiring unnecessary manual fixes. What I need is a “Duplicate as Component” feature that creates a true copy—preserving all properties, variants, and interactions—so I can iterate faster without losing key functionality.
Same issue here, M3 Pro mac / desktop app. Never had lag like this in Figma. Cleared cache to no avail. Seems to have started after a recent update in the past week or so.
In prototype mode, the hover effect (“while hovering”) sticks and does not disappear after hovering over an element. As a result, when hovering over several objects, all hover effects remain on the screen. What is the bug? : worried: Closing and reopening the prototype helps solve the problem. But after some time, the bug may appear again. It looks like some kind of memory problem, in general, prototypes and files take a long time to load and sometimes slow down. It’s very unpleasant to work. In Figma via macOS app
APIs, guides, plugins, and more.
Find a virtual event that speaks to you.
Find answers, learn more.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
