Share Your Feedback

This update is genuinely one of the most frustrating UX changes I’ve experienced in a professional design tool 😡 😡 😡The new left-hand navigation panel permanently steals ~60px of horizontal space on small screens, which is completely unacceptable. That space is my primary working area — the canvas. I am literally losing room to do my job so a panel can sit there doing nothing most of the time.Yes, Variables, Files, Assets, Find, and Library are important.No — they are NOT minute-to-minute actions.They do not deserve permanent, always-visible real estate. This panel is idle 90% of the time, yet it constantly punishes my workflow.On smaller displays, this feels especially hostile. Instead of prioritising the canvas (the entire reason Figma exists), the UI forces a bulky navigation column that adds zero value moment-to-moment and actively makes precision design harder.

Displaying the frame in the interface was a terrible decision; it made the interface very cluttered.

WHEN - will Make be able to read the very design system tokens, primititves semantics and componenets that third party applications already can? I love the platform but this is such an own goal for anyone really clued up- when and why is this not allready implemented? Whats the point in figma make ifw e can’t control the design system and connect design system primitives,semantic and componenets with wrappers around shadcn components etc without doing it manually.For anyone with a modicum of development knowledge this is crazy ommission. It puts me off recommending figma. I might have to resourt to my own custom ontoligies and the daft thing is claude etc reads the darn tokens and renders to production so that kind of also knocks figma make out of the game own goal number 2. Someone please please tell me I am wrong. This seem a massive hole in capability which shoulld have been a main reason for building make to start with doh...

I was very excited to hear that grids were coming to Figma. CSS Grid was introduced years ago and brought with it many things that flexbox was incapable of doing, so I was hoping for a similar level of new capabilities here, and I genuinely cannot believe that this feature is being shipped in its current state (even as a ‘beta’). This is a very long post, but I feel like this feature has been implemented so poorly that it legitimately sows doubt in Figma’s capabilities to deliver features in the future.Inability to ‘hug’ contents Both rows and grids themselves are unable to resize themselves to match their contents (‘Hug”). Row heights must be either “Auto” (1fr) or a fixed height, meaning that if you want your rows to be sized per their elements, you’ve now manually defined each row height in px (not even a variable value), and instead of getting a clean CSS output, now you have however many rows defined in exact values, destr

Come on Figma, it's just about adding the options into the menu. I now can translate from Czech to English, but not from English to Czech, because the option is not there in the menu. Same goes for Hungarian, Romanian, Bulgarian, etc. 

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

We need support for Alt text for images added in Figma Slides. This is a major issue for us. We are using Figma Slides to create presentations and those presentations must be accessible to our co-workers who are blind or low-vision, and to set a good example for other teams.

There’s a lot of plugins, and especially for certain features that there’s a lot of plugins for, like finding Icons/Symbols, there’s certain plugins that i prefer or like, but can only access them through the Recently Used section, but it disappears if I use other ones. There should be an ability to favorite a plugin for reuse.

I want to create a PDF export of my Figma files. But I need a solution to also include my annotations from Figma. Is that something Figma can support in near future?

I’ve been working on a project using Figma Make and I’ve noticed that after a while, Figma Make AI just does whatever it wants to even when I specifically tell it not to in the guidelines.md or even in the prompt specifically.I get messages from AI like this:******The user is very frustrated because I completely violated their explicit instructions to only fix the logic issues and not change the UI. They're also pointing out that there are errors in the console that show I broke things. Let me analyze what went wrong.The user is absolutely right - I completely failed to follow their clear instructions. They explicitly said they liked the UI the way it was and only needed the logic fixed.I think the best approach is to:Acknowledge the complete failureAsk them for guidance on how to restore the working versionPromise to make only the minimal logic changes they originally requestedNot make any assumptions about wha

With the strict enforcement of AI credit limits starting March 18, I’ve been looking at our organization's options for scaling usage. The current pricing structure for additional credits vs. adding new seats seems completely disconnected from reality for power users.Let’s look at the numbers for a Professional Plan (2026 pricing):Option A: Add a Full Seat. Cost: $16/mo. Cost/credit: ~$0.005 Cost for 3,000 credits: $16 Option B: Pay-As-You-Go (Overage). Cost/credit: $0.03 Cost for 3,000 credits: $90 Option C: Shared Credit Subscription. ​​​​​ Cost: $150/mo for 5,000 credits. Cost/credit: $0.03 Cost for 3,000 credits: ~$90

If you try to paste a component into FigJam, you can't set it as a thumbnail. You have to detach the component in Figma first, and then paste it into the FigJam. Then you can set it as a thumbnail.In the same way, if you add a library to a FigJam file (like for stickers) and use one of those, you can't set that as a thumbnail, even though the use case of making covers for clients or projects and being able to just drag and place those in FigJam is probably pretty common. I don't know why you can't set it, but it seems like that would be an easy thing to do. This ticket was closed after everybody gave up… but this seems straightfoward. 

I propose adding a contextual "Play" button directly on the selected frame's label, right next to the Dev Mode icon This simple addition would keep the workflow focused on the canvas and significantly speed up quick iterations. Maybe?

IMO in Dev Mode, the “Explore component behavior” button should be a primary button because nobody has seen this button while it could enormously helps a lot for the development Also, in the component behavior view, you should suggest the component behavior of the nested components

I ran into a common Figma Prototype issue:when the first animation uses After Delay (e.g. 10s auto-play for a hero carousel), it doesn’t start in Present mode unless the page is refreshed.Small preview works. Full Present mode doesn’t.The delay never starts, and progress indicators stay frozen.After some testing, I realized this is because the starting frame doesn’t reliably trigger initialization, so After Delay has no real “entry point”.My workaroundInstead of relying on time-based logic on the starting frame, I switched to event-driven triggering: On Mouse Enter (or any explicit interaction) Immediately navigate to a transition frame From that transition frame, start After Delay (10000ms) Then move to the next carousel slide This transition fram

I keep punching in the same preferences for how files should be displayed in home/project/org view. It would be good to have a json or something that can just save the config. its kinda rediculous how unintuative the files and folders are set up, I get where this is comming from and what its aiming for, but at least offer option for a more intuative folders structure, easy renaming, maybe alias files, drag and drop/force open paths… cream if simply cli shell input somewhere, I mean what are we even doing? what legacy are you preserving with the lagged ‘starred files’ sidebar and million folders that can only have one parent and no children? I would even just opt out of your egosystem with the figma files intact… if that were possible. maybe you are working on the next big thing and this is just backseat driving, regardless, this has bugged be the fuck out since it launched and twise more with updates that made it even worse (you could at least in the beginning double click on folder

The design of websites using AI in Figma Site is quite ambiguous. While designing React applications with AI is relatively smooth through Figma Make, it remains complex and unclear on Figma Site.

I tried making an AI called “Flow” by having the AI design the basic UI and the basic code and asked it to be inspired off of CluadeAI. I asked the AI multiple times, and it kept on pointing out its mistakes over and over again. This was very poor work and I was kind of angry and frustrated that Figma markets it so well but then asks you for credits. Here is a screenshot I sent it.Screenshot that I sent to it as a base to use for the UI.And- here is what it made. Also note: this was made when my credits were about to end. What the AI made.Not only is this a copyright violation, it is horrible.

I’d like to suggest a small but useful feature improvement for overlays.Currently, when opening an overlay, we can only apply a colored background with reduced opacity. It would be great to have an option to blur the background while also applying a color tint (blur + color combined), similar to native mobile UI patterns.

In my opinion, I think the position of "publish" isn't intuitive. Its new position is on the bottom of the left side bar, which is easy to ignore.

I have the preference “Use Scroll Wheel Zoom” enabled, and love that this option was added. But unfortunatly, it is very frustrating with the workflow.I use my mouse wheel to zoom in and out, and then click and hold my mouse wheel to pan around. This is just what I am used to in other software.My mouse wheel can also be pushed left and right for horizontal scrolling. If I accidently move the wheel left or right while clicking to pan, then Figma will switch to a “scrolling” mode. Now when I try and use my mouse wheel to zoom, it will scroll vertically instead until I do a single mouse wheel click.It would be great if “Use Scroll Wheel Zoom” was enabled, then horizontal mouse wheel scrolling would also be disabled. Or at least don’t switch it to a scrolling mode

The Issue: There is a UX "trap" when using the search filter within the Comments panel. If a search term is active, any new comments added to the canvas that don't match that term are immediately hidden. This creates the false impression that comments are not being saved or that there is a sync/connection error.The Experience: I searched for a specific term in the Comments panel during a meeting. Later, I began adding new comments to the canvas. Because my previous search was still active (but the panel was not my primary focus), every new comment I typed vanished instantly upon hitting "Post." Since I was focused on the canvas and not the right-hand panel, I didn't realize a filter was still applied. I spent several minutes troubleshooting my internet connection before realizing the search term was simply filtering out my new comments. Proposed Solutions:

I don’t know if positive feedback is allowed, but whoever made it possible to copy tables from excel to figma and make them editable? Yeah, they deserve a hug, a cookie, and a raise. 

Please before inserting new features resolve core issues:Optimising rendering of pages Optimising rendering of instances Optimising overall speed of platformDo not get me wrong, new features are always nice, but speed and efficiency of the application is the most important and Figma is becoming increasingly problematic in such things.As an example in December could not use the platform for a week because instances were constantly badly rendered and no workaround was possible. Today cannot use some files because interacting with them is impossible due to extremely low speed.If features are implemented but the usage of the application becomes more and more problematic in terms of performance, then what is the point of implementing new features?