Share Your Thoughts

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

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 ve

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.

I would like to easily move an element to another frame rather than having to drag and scroll through hundreds of frames and layers to move it to where I’d like. There should be a ‘Move to frame’ in this menu.  

hey Figma fam, so, we’ve been going on about this for ages, but seriously, when are we getting the “lock guides” feature? it’s 2024, and we’re still nudging guides by mistake 🙄 we all know the drill - you’re in the zone, designing away, and then oops, there goes your guide. it’s like playing a game of ‘spot the difference’ trying to get it back in place. super annoying. i mean, how many times do we need to ask, right? it’s a no-brainer feature that would make our lives so much easier. locked guides = no more accidental shifts. simple. let’s give it another shot. maybe if we all shout about it (again), Figma will finally listen and add it to their to-do list. who’s with me? catch ya later! flo

Simplified use caseImagine there’s one component that is the same on iOS and Android but different on Web I create a Platform property with values of iOS, Android and Web In order to allow all selections, I need to have three variants, one for each Platform property value, even though there are only really two variants.This introduces a risk of someone editing the iOS variant and forgetting to make the same change to the android variant since there’s no way to merge these variants together. This is a really simplified use case to illustrate the point, but I am working with components with 9+ properties, each with multiple values. This creates many duplicate variants and makes it really hard to keep track of the duplicates and keep them all in sync.  Please add this! It would really save me time, headache and reduce the number o

It is driving me crazy when I follow someone, if I need to zoom to desired level, I loose the follow and I have to follow again. I just want to be able to continue following the user on the desired level of zoom I choose.

Is it possible concatenate variables within another?

Would love to be able to save and apply object styles such as a fill color and stroke color and properties; just like in CSS.

When using the eyedroppper/color picker via the shortcut ‘I’, you can select a color and the RGB value is copied to the clipboard, letting you paste this value to copy the color. (Very nice feature!)See below:  However, when pasting the value from your clipboard, the format is like: RGB 151 71 255. Figma does not recognise this a color when trying to use this value. Please see below, when pasting the RGB value in to a field that expects a colour, the RGB text at the start prevents Figma from recognising the 151 71 255 following it: Existing Process: Pasting the result of the Pick Color tool, automatically includes the text