Share Your Feedback

Hi Figma team, Since the recent updates, it’s no longer possible to easily change image fills inside a frame by simply selecting the parent frame.Previously, selecting a frame allowed us to quickly replace image fills contained within its child elements, which made workflows much faster — especially when working with templates, cards, or repeated layouts. Now, the Fill panel only shows the frame’s own background color, and we must manually drill down into each nested element to replace images. This adds unnecessary friction and slows down production. It would be extremely helpful to bring back the ability to:• replace image fills from the parent frame selectionor• provide a quick “Replace image inside frame” actionFigma version 126.1.2 MAC OS This was a very efficient workflow for designers working with visual templates. Thank you 🙏 

I genuinely don’t understand how Figma continues to dominate given how hostile the experience has become — for both users and developers. The UX is chaotic and non-intuitive: layers buried under layers, controls hidden behind inconsistent interaction models, and navigation that feels designed to fight the user instead of helping them. For many people — especially neurodivergent users — the interface can feel actively exclusionary rather than empowering. It’s hard to shake the feeling that usability is no longer the priority. From a developer perspective, the situation is even worse. The platform is effectively closed. The MCP integration with Claude is read-only, and meaningful mutation requires plugins running inside Figma’s sandbox. There is no serious external API for programmatic design updates. That makes modern workflows — automation, CI-style pipelines, integration with engineering systems — far more difficult than they should be.

After a late switch from Sketch to Figma about six months ago, here is my conclusion regarding the UX of Figma:While Figma has many great features that Sketch does not have (dev mode, way more capable prototyping, variables,…) the general UX of the tool is just sooo bad! Here are the things that annoy me most:Visibility of functions: There are so many functions hidden below a small icon that has no label. Much stuff is hard to find. And what drives me really nuts: When a function is not available, then its UI element (or entry in context menu) is hidden – not disabled! I’m using Figma for UX Design, and it just feels so wrong to use this tool that does not handle UX basics correctly itself.   Library management – publishing components: You can do this from the book button on the top left where you usually update components from other files, but publishing is mixed in here if you click on “This file”. But then you can only publish all cha

I’ve already started using the new slots and I find them amazing, but I think it’s very limiting to prevent the use of grid layout. 

I think it would be very helpful to add select funtionality like selection colors for slots in the component instance panel.This would make it easier to quickly target the slot to use the repeat control, and also save library consumers from having to dig through the layers panel to find the slot on more complex components.

One of the things I used to love about Figma was collaboration. I have a paid Professional plan and my partner has another Professional plan. The thing is that we cannot collaborate in a same file. If I want to do that I have to paid another seat for her inside my team which is ridiculous because she is already paying for Figma.With that beeing said, the first time I fell into the trap and added her to my project. Nothing in the UI told me that I was going to be charged with another full seat (really bad UX and dark pattern from you Figma). There is only a button saying ‘Approve’, that’s it! I lost almost $80 because I added several friends to that single file. Figma, you robbered me.So, Figma, you are losing us, I saw this several years ago with Sketch and the community choose Figma. Now I’m open to explore other tools that allows me to work collaborative with other paid members (I’m not saying that I don’t want to pay).I used to love you, you changed! :(

I’d like to share feedback regarding the implementation of AI credit limits in Figmake. As a designer managing multiple complex projects, I believe credit restrictions would greatly undermine Figmake’s usefulness in real-world design and prototyping workflows.  1. Most AI usage is for fixing bad or incomplete output, not luxury use.  In practice, a large percentage of AI prompts in Figmake are iterative—used to correct layout issues, rebuild misinterpreted elements, or align behaviors with visual intent. Each refinement quickly consumes credits even though the output quality depends on that iteration. Penalizing iteration limits the model’s ability to produce accurate prototypes, especially when the AI output is imperfect through no fault of the user, making credit usage really unfair and frustrating.2. Predictability becomes impossible, discouraging adoption.  With a credit cap that no one knows how to predict and calculate ahead of time, I can’t plan how

I have a new branch and adding slots to some of libraries container components starting with modals. Set up and implmentation is fine but I added instructions to the slot description panel and I can’t seem to see how the designers are able to read them? When you select a slot in an instance you see two lines of text then it truncates, clicking the content does not open the rest of the instructions in a fly out and there seems to be no way to access the rest of the content. Am I missing something?  

I’m trying to recreate the structure of our Text Field web component with slots. I would prefer the Figma slots to behave similar to the <slot> element in that they wouldn’t reserve space until there is content in them.Currently I can work around this by adding a boolean property that controls visibility of each slot but this adds clutter to the property controls.In the properties panel slot contents are described as “Default” or “Modified”. Having a third state “Empty” that also hides the slot from Auto Layout would solve both for me. 

Here, I have an orange colour at 60% opacityPreviously I could paste a hex value in, and the colour would be replaced and remain at 60%Now it goes to 100% no matter what I paste here. As soon as I paste in a new hex value, I have to set it back to 60%.I am replacing a colour - not the opacity. Why change opacity as well? This is awful, and as of today, it has really slowed down my workflow. Thanks.

Introducing annotations is great, they’re super helpful ✨ That said, the lack of flexibility when it comes to their positioning is quickly counter intuitive. They end up overlapping with other elements, which can make designs harder to read and manage—especially when multiple annotations are stacked in the same area. It would be incredibly helpful to be able to manually drag the annotations component to reposition it (e.g. top, bottom, left, or right of the target element), while still maintaining their link to the relevant object.   

I’m not sure why this product is so disjointed.  integration is flimsy at best.

When overriding a single element inside a slot in a component instance, Figma marks the entire slot as overridden. As a result, updates made to the main component no longer propagate to any elements inside that slot — even if only one element in the slot was actually changed. Expected behaviorOnly the modified element should be treated as overridden.All other elements inside the slot should remain linked to the main component and continue to receive updates.

hey so im loving figma make ive built a few websites just by prompting but what i am confused about is why figma make and figma sites are 2 separate things i saw there is going to be an update to figma sites to be able to point and edit specific things but im just wondering where that then leaves figma make because now a couple of my websites are done i want to transfer them from figma make to figma site incase i want to make specific changes manually without prompting i just find the whole figma make and figma site separation confusing 

When you have a section selected, no colors show in the right-hand panel by default. So you click the “show colors” button and instead of showing you the colors, it gives a little preview of just 3 or so colors, and then you have to click again to show all the colors - this time with no prompt.What gives? Why make this take 2 clicks to see the damn colors? Also the second state takes up even less space than the first, just combine them into one so there’s a prompt for the user and a preview, or default to the second state from the beginning! Or the first state, frankly it doesn’t matter much its just annoying that its 2 clicks. Who would ever be like “Oh these 3 randomly chosen colors with no labels are exactly what I wanted to see here, all done.”UX rant over thanks.

Whether you are a major corporation or an emerging startup, you would have to decide which design system to utilise for your UX mockups.Do you choose a tried-and-true one like MUI or Carbon, which has a wide variety of created and produced components that are quick to implement but lack your brand's distinctive feel and representation?Or Do you choose an entirely original system that you build and install from the ground up to best represent your brand in terms of colour, font, iconography, and other elements that really set you apart?Let's examine the peculiar argument between Sir UI Kit and Captain Custom to see what works best for you.Consistency vs.

When creating a new project within a workspace, you’re able to change access to invited people only, but it gives access to everyone in the project’s containing workspace. Below is the screen with messaging when I change access to Only invited people. “Only people you’ve directly invited can access this project” means, to me, that only people I’ve sent an invite to within the project space will be able to see its contents. However, when you create the project and go into “Share”, everyone in the workspace where the project was created can access the project (Shown below). You have to go into that row and remove the access of that group. This feels deceptive and creates an unnecessary step

Hi Team,I am writing to implore you to restore a small but critical interaction detail that was removed in a previous update.The Issue: Previously, when a user adjusted a property via a slider (specifically Drop Shadows, Strokes, or Corner Radius), the blue selection bounding box would temporarily disappear. This allowed us to see the exact effect of the change in real-time.Currently, the blue selection outline remains visible while adjusting these properties. Because the outline sits directly on top of the edge of the element, it physically obstructs the pixels we are trying to style.Why this is critical: We are designing blind: It is impossible to fine-tune a subtle shadow or a 1px border when a 2px blue line is covering it. Broken Workflow: What used to be a fluid process is now a friction loo

Feedback 1: since Figma Desktop App version 126.1.2 text styles picker always shows libraries of styles in collapsed state. It’s super annoying, since search doesn’t work until you un-collapse it.Feedback 2: please fix up/down arrow behavior on styles. Example: the text span has style “Body/Emphasized” → I press arrow up expecting it to switch to “Body/Emphasized” → instead Figma selects “Headline/Regular” (the style that just happened to be below the search box). I papercut myself on this multiple times every day for the past couple of months now, at least.Figma’s a great product, I love it, but bugs like these are a big let down for me. I believe basic features like text styles should be dogfooded more to remain best in class. 

Picture this: You step into a role at a rapidly scaling enterprise launching multiple products simultaneously. Initially, team autonomy feels efficient. Everyone builds their own UI elements and moves fast. However, as the product suite grows, fractures begin to appear. You start noticing inconsistent visual styles, duplicate code, and misaligned user interfaces.As the developer responsible for creating cohesion, you realize the solution isn't just "fixing bugs", it’s implementing a Design System. This system serves as the anchor that keeps all teams aligned, regardless of how fast the organization grows.Bridging the Gap: The Birth of a Unified Sys

Like many design systems, our current library uses placeholders + instance swap and we would love to switch to slots.The issue: While it’s possible to wrap placeholders in a slot to preserve content in existing instances, that content is no longer preserved when the instance swap property is removed from the original component. As soon as we remove the instance swap property from the parent component, all instances lose their swapped content.This means we have two options:Remove the property anyway and cause major breaking changes to hundreds of projects Accept redundant properties in the already crowded property panel for any component we switch from instance swap to slotsI’d be very happy if we could remove the property, or rather reassign its function to the new slot. 

I use figma for a lot of subtracting and a bit more complex workflows, i would love to use figma’s tool more but working with pages that lag each time i make a change, cause of figma using only a few gb of RAM (I have 32) and only a single core is really annoying. Currently i use figma to design for game interfaces games and changing softwares is really not an options for me so adding this would definitely help a lot.

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.