Suggest a Feature

Hi,The addition of annotations and measurements to Design mode is such a great decision.However this is rendered almost useless if the annotations and measurements can’t be made visible to View Seat users.Often annotations are used for communication with a range of stakeholders, not just designers and developers. It’s not viable to upgrade every stakeholder to a Full or Dev seat to engage with this content.

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

I feel a little stupid, because the app introduction says it is possible:Figma Help Center But I cant quite figure out how this works? I can log in with my private account but it only has one workspace, same goes for my company account. How do I sign in with both accounts at the same time?

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.

It would be great if the professional plan offered more than 4 variable modes. Right now I want to set up a mode for each component size-- XS - XL, 5 sizes all together-- which puts me over the 4 limit for pro, but well under the 40 limit for enterprise, which is a quantity I will never need. And there’s no use case for enterprise at all for a team our size. I think 10-12 modes for pro would be perfect to give small teams like mine room to grow before we reach the scale where an enterprise plan would be worth consideration.

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,

This makes it easier to use components in designs for different screen sizes. And then you don’t have to calculate every time what 40% or 60% of the width is. This also makes it easier to design scalable applications that grow with the width of the screen.

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 make Dev Mode Annotations visible by all roles, not just Full Dev Mode seats. This can become costly for users needing context but not all the other dev-mode features. Here’s the scenario: We have a dashboard, with cards showing a customer’s account status. This status can be mapped from multiple back-end statuses, to show just one front-end status. For example, any of the following could be mapped to a single status known to the customer as “Completed”: canceled, terminated, sold, complete, etc. This is something that the developer needs to reference, but then also the PM needs to reference in writing tickets (who doesn’t need full dev-mode access), the QE needs to reference for testing automations, and various other individuals on our team. Placing it in a comment makes it less clearly attached to the specific piece of the design, and requires us to keep documentation dispersed among different tools (Jira, Confluence, Figma etc). Simply making Dev mode annotations visible to v

“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

Since Figma does not support going back to previous views, it is quite frustrating to switch between pages. Would you ever allow the same file to be opened in another tab, but not in a new app window? This would become very handy to switch between pages in the same file.

why make this so hard? This should be in an obvious place. I read the info on the site seems to be out of date anyone know where this is? It’s supper annoying to look for billing info and writing in help chats instead of doing proper work. going rate this product way longer just because I wasting my time on things that should easily accessible.

Sometimes I want one boolean component property to both show something, and hide something else. It would be cool to be able to not only assign a boolean property to layer visibility, but also to indicate that it should show the layer if the property is false. Example scenario: Imagine a situation where I’m designing favourites section on the app’s sidebar. I want a sidebar to be a component. Now when favourites is empty, I want to show an empty state with a CTA instead of the CTA. And I want to add a toggle that both hides an empty state, and shows a list of favorite items.

Is it possible to map the HUG or FILL to a variable. It would be great to not only assign particular width values, but also set the width to either hug or fill the container.