Share Your Thoughts

Please go back to basicsYou are moving forward too fast, we don't need more drawing and AI feathers, we need basic CSS options that are the basics of CSS web development since the 2000.On top of the list image-background position, object-fit etcAre you going to do something about it?😡

Hi Figma, I wish it were possible to duplicate text style folders, instead of just the text style itself.

The black floating toolbar is really annoying as it covers up what I’m trying to type. Is there a way to pin it? I know that I can run a script to completely remove it each time. However, it’d be nice to have an option to pin it at the bottom.

Hi Figma team!I’d love to suggest a small but meaningful UX improvement. In Figma, many numeric fields can be reset by typing “auto” (such as width, height, or layout), which is great. However, when working quickly, it’s incredibly easy to mistype “auto” as something like: atuo auot uato aout atou utoa or other nearby typos At the moment, Figma doesn’t recognize these variations and simply rejects the input, forcing users to delete and retype again. Considering how common and predictable these typos are, it would be a great UX win if Figma could accept common mistypes of “auto” as valid and interpret them as auto.This would improve workflow speed and reduce tiny da

I’ve been using Figma for almost 7 years, and this has been a pain point for me while using Figma to craft UI designs in each of the projects I’ve been through. It doesn’t allow me to reorder the starting point flows I’ve created when more starting point flows are added. As more are added, there arises a need to reorder the way people navigate from sub-flow to sub-flow within an app design in the desired order. Additionally, having the ability to rename a specific flow directly from the present mode would be a plus, so the user wouldn’t have to leave the current context of present mode and go back to the shared workspace to find and rename that flow.I am pretty sure that there are a lot of folks in here in this feedback community must have the same concern as mine. So Figma, I am asking you to make an according adjustment to this and ease our lives. Thank you

I am calling this out because it wastes admin time, confuses teams, and quietly pushes paid seats without informed consent. The product nudges users to request licences from multiple places inside the app. These prompts are frequent and intrusive. They look like helpful guidance but they are sales prompts. Admin controls to decline or manage these licence requests are buried and clumsy. It is far easier to approve than to reject. That is a dark pattern that drives spend rather than clarity. End users are not clearly told that what they are clicking carries a cost to the organisation. In many flows there is no plain language that says You are about to trigger paid usage for your team. The end result is predictable. Finance gets surprise invoices. Admins become the bad cops. Designers are frustrated because they did not realise they had pulled a paid lever. This is not how a trusted design platform s

HelloFor years, Figma has been the gold standard for interface design. It’s fast, collaborative, and somehow manages to make design feel fun again. But even with all its brilliance, there’s always been one small—but incredibly frustrating—gap in its system.Figma doesn’t have subpages.And honestly, that’s wild.The chaos of one giant pageIf you’ve ever worked on a complex design system or a product with multiple flows, you know exactly what I’m talking about. You open a Figma file, and suddenly you’re staring at 200 artboards, 50 prototypes, and a sea of arrows that look like someone spilled spaghetti on your screen.Sure, you can organize things into pages. But those pages quickly become their own mess. Before you know it, you’ve got 25 of them—each representing some combination of “v2,” “final_final,” and “do_not_touch.” Not to mention the pages for design system tokens, experiments, and archived explorations.It’s not that F

I frequently share notes on designs with a group of developers without knowing which one will work on what I’ve designed. I’d love to be able to tag several in a comment via a “group” I’ve created within my team (eg- “@FrontendDevs”) How are others handling this?

I cannot find feedback options for figma features, so I had to use this space. Btw, please bring back interactions to Figma design, Figma Make is not at all easier to work with. Actually, it gets harder to use Figma with all those changes - that weren’t actually very necessary for some users. Why using AI in EVERY single product if the AI doesn’t work properly? It changes all the layout we submit to it, stuff that were PERFECT and now, because we have to use Figma Make to do interactions, it simply does not give the result It was supposed to give (and used to work with) for. It changes the submitted design in NOT ASKED ways. Redimensions the screens and elements, changing the whole composition. Please, bring old Figma back, there’s a reason (or MANY) why adobe XD died. Do not transform figma in another xd, i BEG you.

Hello, Figma team! I am an active user of your product and would like to propose a new feature that, in my opinion, can significantly improve the workflow for designers and their teams. We are talking about the possibility of allocating a separate editing mode only for texts inside layouts. At the moment, when it is necessary to make edits only to text elements (for example, to correct typos or change the content of the text), users have to get full access to all elements of the layout, which can lead to undesirable changes. It would be very useful to have a feature that would allow you to edit only texts, without the risk of accidentally changing other design elements. Such a mode would be useful for copywriters, marketers, and other professionals who interact with layouts but are not designers. It would also reduce the burden on designers, who would no longer have to worry about the safety of all other aspects of the project. Thank you for your attentio

In Figma’s playground file for the (beta) AI features, there’s a hands-on example for the AI feature called Replace Content. It sports a (vertical) auto-layout frame with two similar objects. When you select the frame, a wide handle appears on its bottom edge (in the instruction called the Duplicate Bar) , offering the option do drag up and down and add multiple instances of the same object(s).It looks and works a lot like the Repeat Grid of Adobe XD – the only featured I missed now and then in Figma, so I’m a happy camper now ! 😄The feature works very well, and the obvious next task of replacing the repetitive texts for uniquely generated dummy texts, also works very nicely BTW.But how did they get this Duplicate Bar to appear ?I can’t

Please unarchive this topic because now I cannot even send it as an answer to other people who are asking this question because they cannot access it.

Hey all, wondering if anyone else is running into this…When I open a screen in prototype mode and click “Present,” the interactions work totally fine on that screen. But when I cycle to the next screen in the flow, things start breaking — interactions stop working properly or disappear altogether.The really weird part is that the prototype connections also seem to move around or shift across the page. The only way I can get it to behave is to close the present tab and reopen it directly on the screen I want to test — but obviously that’s not ideal for testing full flows. (I have attached photos I have taken, I had to use my phone as I couldn’t screen print while clicking to show the blue prototype links)I also get it with things like my navigation bars - I have complex components set up to cycle through my system and they will totally glitch out and show colours and ui that is not even in the design.Is anyone else experiencing this? Would love to

I have a numeric input field as a component, and its value is set as a text property called value. Pretty simple stuff, right?For prototyping reasons, I want to bind this field's value to a number variable, so I can add/subtract to this value when I press a button somewhere else on the screen. Also pretty simple stuff, right? Well, apparently not. Turns out I just found out that we can't bind number variables to text properties for whatever reason — they don't even show on search results. And since there's no component property of type number, this simple prototyping scenario I'm trying to achieve appears to be impossible. Meanwhile, if I simply remove the value property from my component, then select the plain text layer with the value and try to bind it to my

I would like the possibility to add drag and drop in Figma prototypes in which you can reorder items in an auto-layout frame. Right now it is limited to adding a simulated drag and drop of one item, without auto-layout applied to the parent group/frame. Unless you create different flows to allow multiple items to be dragged and dropped, but always from a static position, to a static position. I’d like that extra bit of freedom, as it allows for better prototypes and conversations.

Hello Figma Team,My name is Faraz, and I am a UI/UX designer who frequently uses Figma for both design and animation. While I truly enjoy designing and animating in Figma, I often face challenges when developers request animations in GIF or video format with high resolution.Currently, Figma does not provide a direct option to export animations as high-quality GIFs. From a user’s perspective, this creates difficulties and forces us to rely on external tools such as Jitter or LottieFiles, which makes the workflow less efficient.I would like to request that Figma introduce an option to export animations directly as high-resolution GIFs. This feature would make Figma even more powerful and self-sufficient, eliminating the need for external animation tools and significantly improving collaboration between designers and developers.Thank you for considering my feedback.Best regards,Faraz

What can you do when you have unattached comments? There should be an option to place it back on a frame or object inside the canvas. Vote here if you have the same issue. (original question here: What do you do with Unattached comments? ) It would be great if @figma can let us reattach lost, unattached comments back to a frame. Even better if the comment automatically falls back to a children frame underneath when you ungroup a frame, to which the comment is attached. That just reduce unattached comments from happening.

This is odd behaviour in my mind!When i select an item and use the scale tool, it makes the new size its default 1x when i reselect that element.Example:I select an image, set the scale to 1.2x, go about my business, return because i want to return that item to it’s initial 1x scale, increase or decrease it. The new size has now been set as its default 1x. and now i have to do math!Why wont it just remember that i set it to 1.2x? This behaviour is weird and makes me wanna use scale less!

Option to select a precise video frame for the thumbnail preview.

Copy/pasting prototypes is possible with simple click interactions, as explained here: Create interactions – Figma Learn - Help Center however this does NOT work for conditional interactions with multiple if/then/else statements, which is arguably much more important, as it takes way longer to reproduce/copy over to another component.

I’ve never reported a bug with figma since they launched.Has anyone been experiencing a greater number of breaking bugs lately? Don’t know what’s going on, but I’ve had to report a whole bunch of issues to expected behaviour.Shortcuts being over-ridden to rotate instead instead of layer up, down.Strokes not setting colour correctly on layer mask images.Font weight selector not working for currently selected font.Canvas dragging after mouse click movement has stopped.Effects panels requiring a close and re-open to be able to adjust settings.Patchy library updates not always updating when attemptingI’ve reported all these individually, but if anyone at figma passes signal up from this community forum, this is a significant number of tiny issues that block or slow down work which I’ve never experienced from the product before in approx 8-9 years. Do with that information whatever you please.

Mass selecting elements in Figma can be a pain. Especially with the new changes to auto-layout sometimes elements will get nested 4 or 5 frames deep. In Sketch, you can press Cmd+Opt while dragging to select a group of objects. When you do this it will only select elements completely within the drag area. This makes mass selecting way more powerful. I’d love to see Figma copy it or come up with something better.

I would like to ask: are there plans to introduce such a feature (tool) for Figma Draw as an eraser in the future? For example, it could easily erase unnecessary vector graphics down to the smallest detail. That is, I mean the eraser, which is have for example, in Adobe Photoshop and MS Paint.

Hello! This is feedback for the Figma team. It would be so awesome to be able to see what was modified specifically when publishing components to avoid any potential unwanted changes that went under the radar. I see it will show some components or variable changes as “modified” with an arrow. But others it doesn’t show what was changed. Any insight into why this is would be helpful. Thank you! 

Hi Figma team,I'm reaching out with a request on behalf of several developers on our team who use Linux as their primary development environment.Currently, the MCP (Multi-Context Preview) feature is locked behind the Figma desktop app, which is only available for macOS and Windows. This poses a challenge for Linux developers who are unable to access or use MCP due to the lack of a supported desktop app.We’d love to see one of the following: A Linux version of the Figma desktop app to unlock parity across development environments. An alternative way to run an MCP server without the desktop app, such as a standalone CLI or server binary that can be installed independently. This would greatly improve the development experience and make Figma’s workflow more accessible to cross-platform teams.Thanks for considering this request!