Suggest a Feature

I frequently utilize prototype mockup features when sharing prototype links with clients and colleagues. Currently, I design web and responsive/mobile versions side by side to maintain a consistent visual aesthetic across both platforms. However, when it comes to sharing them as links, I must relocate one of the versions to a new page and adjust the prototype settings to display it as a mockup. This approach also complicates the review process for Figma files as it becomes challenging for reviewers to switch between pages. I believe it would be more efficient if we could apply prototype settings at the page level, with the option to inherit settings from a parent page if nested. This would allow us to have both mobile and web designs on a single page while using distinct prototyping settings for each.

Font missing error while login in from a different computer. If possible to embed fonts within Figma file/project will be very useful. this feature is present in Sketch.

Considering the fact that scss is much more powerful than vanilla css, and Figma showcased double linked variables of the type that are being used in scss code, it would make so much sense to suppport scss out of the box alongside with vanilla css This is really powerful and would make implementation of DS that much easier. Otherwise, supporting just CSS introduces the problem of having color names like body-color that just translate to #000 instead of color-neutral-100 for example. This would make so that devs would have to manually look up hex adresses in the main color definition file to understand what colour variable name “body-color” refers to if they would be using SCSS

Restricting the level of zooming out was a terrible idea, or at least terrible execution. It used to be much easier to navigate, just by zooming out to bird’s eye view and then back where I wanted to go. And I don’t who thought that the current implementation of this restricted view is okay to be rolled out but they probably haven’t been using Figma on a daily basis. It is now possible to lose frames – they can get behind the right edge of the screen so far that they can’t be dragged back. Ridiculous bug like this have never appeared in Figma before. It feels like there’s a new management and they don’t know what they are doing.

In the “Used in recent pages” section, I suggest a user-friendly way to keep track of where a component instance is used within the current project file. Simply by clicking on an item in the list, a sidebar will appear, showing you a comprehensive list of all the places where that specific component instance has been used in your project. Moreover, clicking on any item in this list will seamlessly navigate you to the exact location where that component instance is used. This feature is designed to make it effortless for you to locate and edit components, enhancing project organization and ensuring you never miss any important details.

I often need to know if the root of a component instance is local to my project or not, and so I find myself using “Go to main component” just to find out. I think something like this to indicate that the root is outside of the current project would really help. Option 1 Option 2

Sometimes, I want to identify all shapes matching a color that isn’t yet assigned to a variable. To identify them, I click on the button labeled ‘See all n colors’ to initiate the identification process, having the following options: Click the ‘See all n colors’ option, then use the color identification feature. If I select the wrong color, I must select the entire frame again and repeat the process until I choose the correct one. Change a color to a random visible color to check if it matches the layers I want to identify. If it doesn’t, I need to ‘Cmd + Z,’ click ‘See all n colors’ again, remember my progress, and try the next color until I find the one I want. Adjust the opacity to 0%, then return it to its previous level. This method “works” when the color has sufficient contrast. Proposed Solution: Implement a feature that allows color matching selection direct from the canvas.

Issue: Sometimes I need a guide at a specific location, IMO it should snap to the nearest vertex, but occasionally it doesn’t, requiring manual adjustment. Proposal: Snap guide to nearest vertex or, alternatively, have it snap to the selected vertex. Here is an image illustrating the current behavior:

Hopefully something that is already in your backlog but we need a way to set variables etc. on entering/exiting a screen via a ‘navigate to’ interaction. An example use of this is to store the last user entered value for a variable so a back/undo/etc. function can restore it. I’ve tried to hack this using ‘after delay’ set to 1ms at the screen level but this fails to trigger reliably. onPrototypeStart/End would be very useful too.

Please add scrolling of hidden content directly in the canvas. Otherwise, I have to constantly check and uncheck a scrolling area’s clip content checkbox when flipping between the prototype and making changes in the canvas. I should note that this wouldn’t be needed if Prototypes that fill viewport was implemented.

Please allow an object to be pinned to the side of a container without having to manually position it. Dragging an absolutely positioned object is imprecise and error-prone. It would be better to make it like CSS where you can enter numerical distances from the top, right, bottom, and left sides and have the object automatically honor the values. Here’s a graphical example:

Please allow frames to fill the user’s viewport while viewing a prototype. This will let both the designer and the viewer to get a better sense of how a page will feel in the real world and eliminate the need to set frames to be some arbitrary lowest common denominator size when a prototype features scrolling sections. It will also set the stage for responsive prototypes whenever Figma adds those.

Hi Figma team, I would love if you could add a “Zoom to 100%” feature in the app. When we design for mobile devices, we always design for a 360px width screen (a smaller Android) to be sure that the design works on small and large screens. As the app’s default zoom mode is “Fit to screen”, and we usually mirror the design on a mobile with a large screen (for example an iPhone 14), it makes it tricky for us to judge typography, spacing, and other elements as the size and the design is not accurate. So, if you add “Zoom to 100%” we would be very happy. 🌟 Keep up the great work, Patrik

current situation： Code2Design: we need to add props or notes onto Figma layer. Design2Code: according to props/notes we can restore code. better design: Design Component based prototype such as Tabs/Button. And then we add theme system onto prototype. If we need Design2Code: prototype need marks CodeDesign. And design theme could adapt to CodeDesignTokens

Would love an option to Ignore Nested Layers when exporting, similar to Ignore Overlapping Layers. Often if I’m creating a banner ad or something similar with a background image and content on top of it, I will set the background image as the fill of the frame and then nest the text and buttons for the ad inside of it. This seems like it would most closely match how I’d set it up in code. The problem is, if I now want to export the background image at the exact crop I’m seeing, I have to hide the nested layers.

Hi! In the right-click menu, the wording “Use as Mask” is consistent whether you want to create a mask or remove a mask from an object. This is confusing because “Use as Mask” is the opposite of what you want to do when removing the mask from an object. My suggestion is to update the phrasing to be reflective of the object’s current state. Maybe “Use as Mask” and “Remove Mask”. Adobe Illustrator uses “Make Clipping Mask” and “Release Clipping Mask”. Anything more explanatory would be helpful. Thanks!

I find it very aggravating that to edit a master of a local component, I have to jump around to a random part of the document, or restore the component and have it be deposited in some random location. Just let me edit a master in some sort of modal or sidebar interface, regardless of where it is on the canvas or if it’s even on the canvas. This will also make it easier to see how my changes are reflected in my actual design without having to pan or jump around over and over.

Hi, imagine you have a switch whose synchronizes state is relevant in many screens. If you don’t want to set interactions on main-component but instances and keep some instances synchronized, you have to do a trick: blend button with state A off, same time blend button underneath with state B on. Short: would be great to have interactions option: „change to” for any(!) component in page (not only for the selected one). Regards

This is dumb and bad. Never ever show this. A container should still be scrollable even if its contents aren’t beyond the fold. This allows users to at least feel that it is scrollable if there was more content. Insanely dumb on Figma’s part. Does anybody work at Figma. there’s probably some dumb hack of putting frames inside of frames and whatever to get the desired behavior, but I care about future people who have to use this god awful tool. Please make it make sense. Thanks.

I want to be able to monitor the adoption of component updates via library analytics.

Improve the contrast of the highlighted menu item in the Quick Action Menu in dark mode. When keyboard navigating its hard for me to confidently select a quick action menu item bc I cant see the contrast between regular and highlighted menu items.

Currently, newly created variables always appear at the root of a variable group. When you have sub-groups within variable groups this behavior gets annoying fast, because it means scrolling up from the sub-group to the top of its parent, finding the newly created variable, and manually dragging it down into the appropriate subgroup. If the sub-group list is long and a lot of variables must be created, this can be a tedious exercise. It would be fantastic if we were able create a new variable at any level to eliminate the need for this manual step.

As a designer I would like to be able to color code comments in Figma as well as make personal or hidden comments for myself. It would be great to be able to discern questions from comments, suggestions, edits, and feedback without having to go through each comment.

Would be really really really helpful if the version history header of the list would be sticky instead of scrollable. It’s incredibly annoying to scroll through endless save points, but when trying to edit, forgetting you’re browsing version history because you can’t see the Version History header on the right side, in the list. And if I want to close it I need to scroll all the way tot the top to pres the X button to close it. Make it sticky please. It’s a simpler interaction

Hey Figma it would be nice to have a button at the top of the preview that would stick current frame so it would not change it when I change selection. Thanks Figma – 30 Aug 23