Suggest a Feature

Would be really nice to have line hops for when creating complex IA charts or other interaction maps, site maps, etc. Sometimes it’s hard to not have 2 lines cross and having a line hop is a really nice feature. If you’re looking for an example, Omnigraffle has had this feature for quite a while.

When updating a component from a library and clicking “update all” (either all updates, or all instances of one update), Figma will immediately tell you that the updates have been applied. But especially in cases when there’s a lot of instances to update, they clearly are not, as the whole client will slow down to a crawl for a considerable while and the updated versions keep slowly changing in the view. Could you maybe add a spinner and a message that tells me when it’s actually done and I can work again.Also the ability to set some frames/pages to ignore updates would be nice. I can have things I don’t want changing even if I update the rest of the page. Skipping those instances by hand every time is a pain in the ass.

It would be cool if you could right click and fill container and hug content and ignore auto layout. These are used a lot.  

I am actively using Variants, but there is not enough search in the Variants selection list in component. In my Design System I decided to design one basic component: 1 button, 1 input field, 1 icon … etc. I implement the rest of the variations and states in Variants. I’ve in my base 16px Icon component 34 Variants of icons, in base 24px Icon as many. Search bar would be of great help: Does anyone use Variants like me? How did you solve this navigation (Search) problem? 😊

So many times have i accidentally closed the file i am intending to open because of your decision to surface the close X on hover for a tab i am not active in. Chrome does not do this. Please remove it. Make close X only appear for active tabs

Hello Awesome People! First of all, I’m sorry if this has been asked somewhere already, I tried searching but didn’t see anything. Is there a way to know what design files have detached a component? Here’s an example scenario, I open up a DS file and navigate to the library analytics I click to view more details on a component which says it’s got 3 detaches I arrive on a screen with all the variants listed for this component, I click on one which states it’s got 1 detach I then arrive on a screen which is listing 16 pages and I’m not clear why wanting to just find the file that has the detached component. I hope the above makes sense, thanks in advance for any pointers here 😊

As written in the documentation (Prototype interactions and animations) the destination of a Scroll to action can only be an element of the same top-level frame. But with this limitation it is impossible to prototype a common navigation pattern. On one-pagers there are often floating menu for intrapage links. E.g you have an hamburger icon that opens a menu overlay from where you can scroll to a specific page section. This can’t be realized with an Figma overlay because of the restrictions mentioned above. There is a workaround, but it seems that it only works because of a bug: You can set the menu overlay as an child of the top-level frame of the one-pager, define the Scroll-to actions and then move the menu outside the frame (as an separate top-level layer) to show it later as an overlay. By doing this all the Scroll-to actions still work, but when you change an action the target will be rested and the navigation is broken. Working Example Maybe you can remove the restrictions that t

When you delete an element in a nested structure, you lose all selection. This means if you want to continue working around that level, you have go dive again to that level (double-click, double click, double, click, double click…) Deleting an element should auto select the immediate upper level to stay where we’re currently working Or auto select the previous element in that hierarchy maybe, or the next one. But staying around there, not going back to root level.

Hi Figma Team!I’d love to request a small but meaningful feature: Could you please make Figma remember the UI state (e.g. when panels are minimized) across sessions? Right now, even after clicking “Minimize UI”, the left and right panels open again after restarting the app. For those of us who work in a clean, focused canvas — having to manually hide the UI each time is a bit of a chore. Would be amazing to have an option like “Remember UI layout on startup” or “Start with minimized UI” in Preferences.Thanks for all your hard work — Figma is awesome! 🙌

Hey!I’m working with assigning primitive color variables to semantic color variables and sometimes I’m not sure which color is the right one. If Figma shows the hex color value, when hovering the color swatch, while selecting the color variable I want to use would be SOOOO helpful.  Thank you!

So I’ve seen similar posts before, but I’m putting this out there because its something that needs to be implented.Let me give an example, I’ve got a component for showing to elements side by side, one of the elements is a contact form, said contact form is also a component of its own.If I place a component instance of the layout component it only shows the properties for itself and not its children.It would be so useful if it could also show child properties.I would suggest showing “Parent/Current Component Properties”, a divider below it and then you list all properties the user in question added to it.Then if there are any child components you show “<CHILD_COMPONENT_NAME>’s Component Properties”, another divider and then all the properties that child has. Repeated until all child component properties have been listed.Of course someone could make a ridiculous setup where there’s like 10 - 20 child components that are each a child of the other child, which could create issues wh

Add the ability to add text-wrap: pretty and text-wrap: balance so that more options are available to ensure more flexibility to how text can flow/reflow and reducing hyphenations and word orphans.

Is it compulsory for the connector to snap to the edge of the screen? what if i want to show connection between specific elements in 2 different screens ? Also please provide good connectors in Figma as well  

When working with local variables and tokens I find myself constantly opening and closing the local variables panel. It would be nice to have a shortcut added for displaying and hiding that panel. If there is not a shortcut added in first version, then this action could be listed in the MacOS menu bar as a command, so that a custom MacOS shortcut could be added,

I regularly need to work with screenshots of webpages, which can be a couple thousand pixels tall. I need these images to be actual size. Can’t do this in Figma cause it automatically scales large images down. I know there’s a plugin but this seems like a silly thing to rely on a plugin for, there should be an option native to Figma that lets us shut this function off. Or give us an option to scale the image back up to the original dimensions? (even if the quality’s going to get wrecked) This has been such a huge thorn in my side! Please & thank you!

Currently, in prototype the cursor appears to be either ‘pointer’ (for everything) or ‘hand’ (if a click interaction set up on an element). I would like to be able to change this to a text cursor, when hovering over an input field in my proto. Affordance is a very important part of UI so surprised theres no way to do this? Of course can hack it by adding an image of a cursor, but then you end up having that plus the actual cursor on screen & it makes things worse. Should be an easy feature to add and would be very much appreciated!

Hi! My team exclusively uses Figma as the source-of-truth for implementation across various verticals: product, design engineering… We heavily rely on deeplinks to cross-reference other relevant files, flows, screens or resources to make the hand-off files easier to navigate for engineers. Our problem is, after clicking a link that leads to another frame in the same file, there’s no way to go back to the previous page: People need to manually navigate the file hierarchy and sections organisation to retrace their steps. Easy when you’re the person who came up with all these flows and know the file org by heart, but hard for anyone else. 😅 A floating action similar to the “Return to instance” button we have when shortcutting to a master component would be ideal. A keyboard shortcut to do that would be good enough. Any thoughts here?

When creating hand-off documents I like to showcase user flows by using arrows between different UI elements. I have to use plugins to create these arrows at the moment. When playing with Figjam I notice it had a connector option - this is great. I would love it if we could also have this connector option inside Figma as it would be a HUGE timesaver for hand-off. I would like to think this would be a super easy update given that we can already edit connectors inside Figma. We just need a connector button in the toolbar like so:

Context (You can skip it) I’m working on a plugin that stores frames designed in Figma independently, so different, unrelated to each other, people can use and edit them in their own Figma Files. Designs selected by a user are exported. If another user needs to edit the designs, it can import them to its own Figma File and save it. If another user needs to render the designs outside Figma, it can choose them from an Admin Panel Moreover, designs should have a possibility to implement Widgets, which should be stored and restored as well. Problem Widgets can’t be created by Plugins, they can only be cloned. Which is a problem in my case because exported designs may contain Widgets, which may not be familiar to another user, thus it can’t be imported back. Proposal I understand that this is probably for security reasons, but I really want to see this feature and I think I have a nice way to make it possible. createWidgetById I propose a new method for PluginAPI, which will be able to c

From what I see, Figma is struggling with variable heights, especially the ones relative to the viewport (heights of design elements vs height of the prototype and its elements when previewing, relative to the viewport). For example, you can’t have a section on a homepage be 100% viewport height both in the design and when previewing (which is the MOST ESSENTIAL, BASIC necessity in web/app design). Suggestion to fix this:A new option for Frames, a separate set of dimensions called “Viewport dimensions” These dimensions will NOT affect frame dimensions. Instead, these dimensions will provide variable boundaries which design elements can refer to, and adjust accordingly in both design view and when previewing a prototype.For example, your main frame is 1920 x 8000 in design mode and you have a section (auto layout) which should be “full screen height”. This can be a 1-click solution, here’s how:You select the main frame and set its “Viewport Dimensions” to 1920x1080 You select the sectio

Introducing an Invisible Mode for Figma to enhance user privacy. This feature allows users to work without showing their online status, preventing others from following their activity. Perfect for focused, distraction-free design sessions.

A back button (and possibly a forward button) would be very helpful in the sidebar to navigate larger Figma files with multiple pages.

“Please add a feature that allows moving a note after it’s written. Sometimes the note falls in the middle of the design, and that’s really not good.”

It’s hard to find the “Restore this version” button once a chat goes beyond 100 messages. Figma should add pinned Next/Prev buttons in the top bar, allowing users to preview each version after a chat and then decide which one to restore.

Hello Figma team and community,I’ve been working on a project where I need to display detailed information about multiple people (or products) in a modal. The setup is simple: Each Card component has exposed properties (Name, Job, Description, Photo). On hover/click, the card should open a global Modal that shows the same information. Currently, the only way to make this work in prototypes is to use Set variable → literal values (e.g., selName = "Norman"). This means: Every instance of the card requires manually duplicating interactions with hardcoded values. If I update the Card property (e.g., change the person’s name or job), the modal still shows the old hardcoded value unless I also update the variable action. This breaks scalability. For 10, 20, or 50+ people, it becomes very time-consuming and error-prone. 💡 What I would like to request:The ability for Variables to “read” the exposed properties of a component instance and pass those values dynamically to the Modal. In oth