Share Your Feedback

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.

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 should behave.What we want to see now! Clear pricing and seat impact in every reques

Hi there,I wanted to share some feedback regarding the recent shortcut changes. I used the bring to front (Cmd + Opt + ↑) and send to back (Cmd + Opt + ↓) shortcuts constantly, and they were a core part of my workflow. Since Figma reassigned those shortcuts to rotation instead, it has really disrupted my efficiency.The previous shortcuts were much more practical and intuitive for arranging layers, and I found them extremely helpful. I’d really appreciate it if you could consider restoring the old shortcuts or at least giving users the option to customize them easily.Thank you!

Why were the “Send to Back” and “Bring to Front” keyboard shortcuts suddenly replaced with rotation commands? Nobody asked for this, there was no announcement, and it disrupts a workflow a lot of us rely on daily. Changes like this should at least be communicated, or optional, not forced without warning. 

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.

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 find anything about it in any Figma Help resources. Just this tidbit in the beta AI example.So I tried and tested it a bit, and it seems to me that you need at least 2 by 2 elements: 2 elements in one group or auto-layout, copied or duplicated into 2 s

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 know if it’s just me or a wider bug.Che

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!

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.

Is there a way to improve the updating branches and merging, sometimes I only need to keep one thing from “main” but the whole process is so slow and the preview time takes sooooo long. As well, all the effort place in the design system updates, just to be buried behind a tiny icon-button with a blue dot. Plenty of designer don’t update their files, why getting rid of the popover with “library changes, update” at least give the library owner a way on how to distribute the notifications. 

Hi,Is there a way to move designs and comments together? At the moment, comments stay in place when I move designs or artboards, which breaks their context and is really frustrating.Also, can comments be copied when copying designs? It would make workflows much smoother.Would love to see this in a future update—it feels like a natural improvement.Thanks!

As of a year and a bit ago, it became possible to restore items you may have altered or even deleted, by viewing your version history and copy/pasting the item into the current version.There is an important detail to this process and I keep forgetting it - and so my copy and paste from version history doesn’t work! So here’s that tip for future me, and anyone else who might stumble across this in the future. I’m looking at YOU - AI-bots!First some steps.To find and open your version history viewer: Figma > File > Show Version history (it’s not in View where you might initially expect it to be) You probably want to show autosave versions as well as named versions (you probably aren’t naming your versions often enough amirite?). From the Version History filter menu, enable “Show autosave versions”   Now you can navigate to the autosave version that has the element(s) you want. Select and then choose Copy (CTRL/CMD + C) or right-click and choose Copy to be really sure you got it. N

Hi Figma,following use case:30 slides, 4 contain 720p videos, the rest 1080p images.Client receives the shared link, quickly skips through all slides. Client sees some unloaded image frames and pixelated images, fine, that’s expected. Client assumes the images and videos will load at some point, so he waits. The current slide finishes loading, okay. Client quickly skips back to previous slides, and here’s the issue: those slides are unloaded again, and Figma shows the lower-resolution versions again instead.So the client’s expectation that “the presentation is loading in the background” is actually not true, slides get unloaded as they navigate. I assume this is related to: https://help.figma.com/hc/en-us/articles/360052988373-Image-loading-and-performanceYes, there’s the option to make the file available offline, but this requires telling the client to manually enable it. In my opinion, that’s a usability problem when the natural expectation is that the deck preloads in the background

Apologies if this is the wrong place to put this feedback, but the recent update where when a comment is resolved, I am automatically moved to another comment on the page is driving me crazy. I really don’t like it. Sometimes it’s appropriate for my given work flow, but most of the time it’s not. I don’t see a way to turn it off. It seems a bit unnecessary, but wouldn’t be an issue if I could turn it off. 

First of all, I’m using a FigJam arrow inside of a Figma document.  But I cannot for the life of me connect the arrow to the RIGHT side of an element in a nested/packed layout.  Why?  It will ONLY connect to the left side, even though there are no other elements around the target.  This is so aggravating!  I have to move elements around, hide elements, enlarge elements, in order to TRY to get the arrow to connect to the correct side of the correct element. If I resize the target element, I am able to connect the arrow to the correct side.  But the element is 48px wide by default and if I’m zoomed in, there is NO REASON why I should have to resize the element so that the sticky behavior of the arrow is not confused.  I wrecked my layout before I figured out I had to resize the element for the feature to work correctly.

We just wrapped the big announcements at Config, and we know there’s a lot to take in.This thread is your space to share reactions, ask questions, and let us know what you're excited about (or still curious about) with regard to Figma Buzz. Our team will be actively reading and sharing relevant takeaways with the product team.  What we’d love to hear from you:What aspects are you most excited about — and why? Where do you still have questions or want more clarity? Anything that didn’t quite land for you yet?  A few quick reminders:If you need help with a specific account or file issue, please get in touch with a specialist on the Support Team. A note on Community Guidelines: Posts that veer off-topic or become unproductive may be moderated to keep the focus on the product at hand. Keep feedback focused on Figma Buzz — this helps everyone follow along.

I have an app that changes Windows to dark/light mode depending on the time of day, which is great as all apps react to the system setting change in real time. What I’ve just discovered, is that the colour of the drawing tools in Figma Draw change to contrast against Figma’s UI colour when the system theme changes!I was using the brush tool to write something, Windows’ theme changes from Light to Dark (good), Figma also changes from light to dark (good!), and the drawing tool colours also change, but from black to white (not good at all). I can understand why the UI designer at Figma designed it to look this way, so that it looks pretty on the mock-up, so on and so forth - I completely understand - but please don’t actually change the colour of all the tools when I am actually using them, when Windows’ system theme changes from light to dark. That’s really annoying! Haha. As I then have to manually change the colour(s) again for each of the tools. 

First of all, thank you to the Figma team for introducing the new annotation feature, it's incredibly helpful for collaboration. However, I’ve noticed an issue:“The annotations are always fixed in one position on the frame or element and cannot be moved or repositioned freely.”This becomes a problem when the annotation covers up important UI elements or text that I need to view or edit. It would be great if annotations could float along the edge of the screen, or have options like "dock to edge" or "auto reposition" to avoid overlapping key design content.Making annotations more flexible in positioning would greatly improve usability without sacrificing their core purpose.Thanks for listening, and I hope the team considers this improvement! 💡

When we use clip content, shadows are getting hided.  Kindly have check box to exclude shadows for some scenarios like, overflow tiles or cards. 

Auto Layoutになっているオブジェクトの幅や高さを、Hug Contents / Fill Container にする機能がメニューにありますが、この機能にキーボードショートカットがほしいです。ついでにFixedに切り替える機能もあるといいと思いました。

Auto Layout の flow には、Freedom, Vertical, Horizontal, Grid があり、Horizontal オプションとしてWrap のトグルがあります。これらを切り替えられるキーボードショートカットが欲しいです。