Share Your Thoughts

Feedback on using components in Figma SlidesOn multiple occasions Slides will change the icon used in the component. Example: in a  screen component where I have a nested navigation bar instance that uses icon + text, everything looks proper on the Figma side. Once I copy an instance of the screen component over into slides, it changes the icon to something else. If I break the nested navigation bar instances, the icon now shows up properly on Slides Updating the component on the Figma side does not update the component instance in Slides, forcing me create and instance in Figma and then copy it over to Slides

I’ve always admired the UX & visual design of Figma from day 1, so many years ago. But the new lock/unlock icon is just terrible, I am sorry to say. The tiny arrows is so so so so so small and you can barely barely barely see the difference between lock & unlock. Now i need to hover to know what’s happening/function state. Why did you do this guys? The previous lock/unlock icon worked for years, so why fix something that did not need fixing. Pls revert to the previous icon. Thank you!

Hey guys, random thought—what if Figma had a built-in timer? Like, you start working, hit play, pause when needed, and keep track of your time. Could be useful for managing workflow and even showing clients how long things actually take.What do you think? Would you use it, or is it overkill? 😅

It’s difficult to toggle between editing board content and moving the board, because you have to either click the hand tool button or use the keyboard shortcut. Similar tools I’ve used allow for holding the right click to toggle to the hand tool, making it easier to go between moving the board and editing board contents. I’d love to see that feature introduced to make it easier to move the board around as I’m editing. I haven’t been able to find a way to do this, if it’s available already, please let me know how to enable it! Thanks!

Being able to right-click drag to pan around the canvas seems table stakes for infinite canvas and whiteboard-type products. It would be helpful and easier to be able to do that than trying to use the middle mouse scroll wheel button or holding spacebar.

Mapping out flows as part of UX design is critical. There are plugins for this, and we can copy shapes and connector lines from FigJam into Figma… but they can be much more accessible than they are today. In current state, I need to open a FigJam file every time I design so I can copy stickies, shapes, and connector lines into my Figma file for annotation and user flow mapping. It would be great to just have this toolbar directly accessible in Figma files, too!

I would like to make a suggestion for the layout section of figma. A frame rotation function should be implemented by simply clicking an “invert” button from the layout section in such a way that the frame rotates by 90° without changing the frame's rotation indication, in order to avoid incorrect autolayout behaviour and movement of elements within the frame.

The emoji is far too prominent and distracting. I feel like it's laughing at me while I'm working and it’s lowkey annoying.You may change it to something more neutral, like 👍.   

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

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 componentBut 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.

Could you please add a time stamp for last edited to the conflicts preview on each branch. It’s practically impossible to recall which of two seemly identical tiny preview designs was the latest. Time stamping, as a basic MVP feature, could help improve the experience radically. Thank you. 

I created several “simulated overlay” menus and would like the option to prevent accidental clicks on content behind the layer. From a UX perspective, I’d like a checkbox option that says “ignore all interactions behind this layer” when the layer is visible.In my case, I am creating a pseudo overlay experience using my own hack method. You create a modal (for example) on a components page. You put an instance of the modal on another page (separation of concerns from components and prototype pages). You then toggle the visibility of the modal instance on the prototype page where necessary. For example, a command menu that is displayed on button click.Why do it this way? Because the default modal/overlay experience is bad. They lack responsive design support, they have to be attached to every component instance on within a page (rather than just on the master component), and they can be buggy from time to time.There are other cases I would also like pointer events turned off, similar to

Description:When working with prototypes in Figma, the list of screens quickly becomes very long. This makes it time-consuming to find the correct screen. There is no efficient way to search for a specific screen or better organize the list. Expected Behavior:Ability to search for screens in the prototype list (like for components). For the moment search working not very well and does not recognize naming groups Better organization, e.g., through groups, folders, or favorites (for example: name1/category/)

If we can tag comments to a frame, group or component rather than just the canvas area such that one can simply search comment history for both resolved and active comments by clicking the element.

I am writing to express my concern regarding the UI3 update rollout. Despite joining the waitlist early, I have yet to receive the update, while some of my colleagues who did not join the waitlist have already gained access to the new UI. This inconsistency is causing significant disruption to our team’s workflow and productivity, as we are now working with different interfaces. The delay in receiving this update is not just an inconvenience; it is directly affecting our ability to collaborate effectively. As a dedicated user who relies on your platform for critical work, I am disappointed with the way this rollout has been handled. I kindly request that this issue be addressed with urgency. Please prioritize my account for the UI3 update to ensure our team can operate smoothly and uniformly. Thank you for your immediate attention to this matter. I look forward to your prompt resolution. Best regards,

Google Slides allows this and I love that feature. I can highlight the important things that I must talk about and they catch my attention when sharing my screen. Would be amazing if Figma allowed this as well. 

Hello there, I’ve been trying the prototype features. When switching from one frame to another with smaller height, it aligns the smaller one to the center of the screen. There should be a way to set the prototype positioning. I would like to align all my frames to the absolute top.

With the rise of generative AI, designers are busy making prototypes of chat-bot user interfaces. Instead of faking it, what if Figma provided a way for prototype users to interact with a real LLM? There’s two different ways you could do this. Easier Way - add a ‘generate text’ option to the list of actions in the ‘Interaction’ menu (in prototype mode). Once ‘generate text’ is selected you would need to: Select a text layer (similar to selecting a destination frame for the ‘navigate to’ action). This could be an empty text box or a text box that already has some text in it (in which case the generated text would just come in at the end). You could format the text box however you want but it would make sense to give it a fixed width and a height that hugs the content so that the box can continue to grow vertically as text is generated. Type in a prompt. This is the prompt that the AI generated text will be responding to. This prompt will hit the LLM once the designated trigger is set

Small piece of feedback after testing out Interactive Components. Ordinarily, I’m able to create a new instance of a component by copying-and-pasting it. This is nice when I’m creating components on-the-fly, as I can then quickly add them into my design. If I copy-and-paste an Interactive Component, it creates a brand new, identical component, rather than an instance of that component. Would be nice to see this fixed so that it behaves the same as a normal component. Thanks! Michael

I’d like the ability to stamp today’s date! 

Please, can we have alternating row colors for variables? I just need a little zebra striping to help me see what I’m working with. The system I work in has many color tokens in several themes. Adding alternating row colors is a small UI change which would greatly help the usability of this modal. I have a lot of other problems with the variables modal (it’s too small, lacks functionality, etc). All of those problems require higher-level design thinking. By contrast, implementing zebra striping is an easy win! 

Hi, Crop tool should snap to image border instead of being able to go out of bound. Thank you

It would really be amazing to bring the branching functionality to FigJam. My team is using FigJam to manage some very complex diagrams. And, to add complexity and stress, we are using the Figma APIs to use FigJam as a logic management tool (backend) for a feature we are building, so these complex diagrams are extremely valuable to us. So we would love to have the ability to branch → approve/reject → merge changes.  Is this something that is on the roadmap?

I’ve noticed that the “Dev resources” section is enabled if I’m in a main file but it's disabled while in a branch file. Is this an expected behavior or is my version buggy? It's the same issue either on web or desktop app. Thanks in advance. 

I have 46 pages on a project. (Maybe an extreme case, but yes I do). I just want to search for a page by name.