Share Your Feedback

As a React/Drupal developer who works closely with a UX designer, we constantly debate what to call a CTA or how to phrase a short instruction. So I built a plugin that helps with exactly that. Microcopy Fixer suggests clearer alternatives for short UI text without rewriting your whole design.You can check it out here: https://www.microcopyfixer.com/figma-pluginFeedback is welcome.

Auto-Variant Grouping, A simple tool that automatically detects related components and groups them into variants. Designers waste time manually grouping 10–40 components into variants (e.g., Button / Small / Large / Disabled / Hover).This feature would scan selected components → detect pattern similarities → auto-create a variant set. Select multiple components → click “Create Smart Variant” Figma analyzes: Naming patterns Layer structure Size similarities Color + state variations Auto-groups them into a clean, structured variant component Auto-renames properties intelligently It’s not a massive AI feature. It’s a mini-smart workflow improvement

The idea is to have “synchronized sections” (see Notion Synchronized Blocks) →I often need to have the same content in several files (maps, etc.), and synchronized sections would save me from having to maintain them all.  Notion Example:  

A new left rail was added with some new AI prompting features in Figma Design. In this layout I’d like to have access to the icon for Review Unpublished Changes from the Pages/Layers tab in the same placement as it is on the Assets tab. Functionally, I’d like the icons in the header to be the same on both tabs with Minimize UI and Review Unpublished Changes always existing in the same place. I’ve selected Minimize UI more times than I care to admit when I really wanted the Review action instead. Also, I’d remove the X close button from Assets as it’s unnecessary. 

Some times i feel this mobile device should have opacity option fade out in background, when we hover it will active again ! What do you think of that? . Just a rough thought.

Right now, when I export a PDF from figma, I expect it to be like a regular PDF from any other software such as illustrator. However, when I look at the internal structure, some things are in an XFORM object, other things are not, text has redundant copies and are masked by other shapes elsewhere in the hierarchy. things in frames are similarly structured in weird ways.This makes it impossible for screen readers to read it, and it makes it impossible for me to use Figma to design stuff for use in PDFs, even though figma does support exporting to PDF. 

Just built a pitch deck to present to clients using Figma Slides and decided to start using object animations to add a bit of flare. I was sad to learn that Figma used the same “Start” animation choices as Powerpoint which is (1) Start on Click (2) Previous to last animation.We need more options. The biggest one is just add the same prototype prompt of “After Delay” on object animations. The other one is give us more choices then “Slide” and “Fade”. Add, the standard animations that most apps have, like spin and make 3D and more...

When you right click to view details about a variable within the variables panel, I would like to see if that variable is being used in my file and where.  Today my devs asked about a variable that I sent over via the TokensStudio Figma plugin. It was just called “default” and they weren’t sure what it was for. I must have created it by accident but now I don’t know if I used it for anything or not. I just deleted it but it may have been connected to something. I have no way of finding out.

We use variable for our colour fills for type layers.Unfortunately it is not possible to see if a variable colour is accessible over a background colour unless you detach and open the colour picker, and then reattach.. 

Hello! I am a community advocate for FOF, Sofia for Bulgaria and we experience difficulties when we want to use Bulgarian Cyrillic in several fonts with the “Stylistic sets” feature, but Bulgarian Cyrillic just doesn’t work. When I try the same in Adobe Illustrator for example - there are no problems. The only solution we’re able to find is to change the font’s core defaults to this type of Cyrillic, otherwise, it is impossible to use the stylistic set in Figma. Best Regards, Daniel Dungyov

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: Grid Limitations for Data TablesIntroductionThank you for this Grid update! Features like "hug" and "fractional units" are clearly a welcome improvement for simple cases (galleries, basic layouts, etc.). However, I must share a different experience regarding the creation of data tables, where Grid actually introduces significant friction compared to auto-layout.The problem: loss of structural hierarchyWith auto-layout, you could create a natural and maintainable architecture:Table├── Header (slot / component)│ ├── tr (reusable component)│ │ ├── th (cell)│ │ ├── th (cell)│ │ └── ...├── Rows (slot)│ ├── tr (reusable component)│ │ ├── td (cell)│ │ ├── td (cell)│ │ └── ...│ ├── tr (component)│ └── ...Advantages: Clear parent/child relationships, reusable components, easy to maintain

When testing out the new grid inside components, I noticed that there is no option to hug the content vertically. We use instance swaps in things like footer for our designers and it’s not ideal for them to have to manually resize. Would be great if this new feature hugged, otherwise we can’t really use it in a lot of our components in our design system we thought it would be good for.

Hi, I just want to share a concern.Recently I came across the message of the Figma Make monthly limit, which I would have crossed (when it’s going to be implemented). I just want to mention that the limits are waaaaaay to low. Especially, prompting with AI requires a back and forth of conversation usually because 1) it’s better to ask 1 thing at a time instead of a bunch of things, 2) with 1 things fixed, it can break something else, and so another prompt is required to fix what the AI has broken.This way, creating a decent prototype to test some UX patterns can exceed the limit in just a day or few hours of prompting. Which is kind of not what we want as we might need it practically every week, multiple days. So increase the limit by a ten fold (10x) would be a more acceptable limit. Also, I would love to just pay a bit more every month to just have unlimited prompts. Imposing those current very small limits will not help us at all, i

In FigJam I often duplicate a sticky that already exist, it can be because it is close by, or I want to create another with the same color. Then I move it where I wanted, often on top of an image, but then I ALWAYS have to “Bring it to top”.I understand the duplicated sticky is maintaining the z-index of the “parent”, but why? If I make a duplicate I would expect the same as adding a new sticky from the toolbar, in that case they are always on top.Thanks.

I know that something has changed because I use this shortcut constantly and my muscle memory is failing me.  Expected behavior:With an object selected Press “k” on the keyboard UI switches to Scale tool (if not already there) AND auto-focuses + highlights the value in the #x scale field Type desired scale value “Enter” to confirm Ex: select object with Move tool + “k” + “.5” + “Enter” = item reduced by 50% from center - it’s so easy, I do it all the time. Observed behavior as of 12/13/25 @ 5pm PST: Pressing “k” while on Scale tool behaves as expected Pressing “k” while on Move swaps to the Scale tool, but DOES NOT FOCUS the #x scale field In order to focus the #x scale field from Move, I now have to press “k” TWICE in a row (once to change tools and a second time to focus the #x field). As a result, my muscle memory keeps resulting in an object that is some lower opacit

Hello, good day.I’m experiencing serious issues with the new Figma UI update. Many essential tools — such as padding controls — are missing or hidden.Please do not enforce this new version. The previous UI was much better, clearer, and far more efficient for designers.This new version has no advantages, feels confusing, and makes our workflow significantly harder.

They are so bad, it’s sickening. First, masks go behind the masked object, (?!) Second, if you build a mask out of different compounded shapes (add/subtract), then you can’t select the sub shapes by clicking. You have to go to the layers and navigate through tens of shapes. Please change this, just do it like Illustrator. It’s unbelievable how bad it is. I get dandruff every time I have to use them.

Hi Figma team,I’d like to provide some feedback on the current Pages and Layers panel experience.Right now, the Pages section and Layers section are stacked vertically. When a file contains many pages and many layers, I have to keep dragging the panel up and down, which is inefficient.Would it be possible to redesign the layout so that Pages and Layers can be displayed side-by-side, or allow them to be expanded simultaneously in a more flexible way? This would make navigation significantly faster.Additionally, could the Pages section support a grouping feature similar to Layer folders? When a project has many pages, the list becomes long and hard to manage.Overall, the main goals: Reduce unnecessary scrolling Allow quick access to all pages and all layers Support grouping/organization for pages Thanks for considering these improvements!

Right now, Figma automatically stacks new layers in Auto Layout with the “Last on top” in the Canvas stacking. While you can manually change this for each frame, there’s no global setting to make "First on Top" the default.Having to adjust this every single time slows down the design process. It would be much more efficient if Figma allowed users to set a global preference for stacking order—just like how we can customize nudge values.Honestly, "First on Top" feels like it should be the default, with an option to switch if needed. This small change would save a lot of time and make Auto Layout much smoother to work with.

I’m trying to create a horizontal scroll section (basically a simple carousel) in Figma Sites, but it looks like this interaction isn’t supported at the moment.Has anyone managed to make horizontal scrolling work?If it’s currently impossible, is there any workaround or alternative to simulate a carousel?

The dashed lines are so inconsistent with any sort of shape with corners or rounded edges. There needs to be some sort of option to choose Adaptive styling or consistent styling or something like that so that the designer can choose to either have figma style the dashes to fit the shape how it thinks it should look, or consistent dashes and gaps as manually set in the advanced settings. This is very limiting and frustrating. Currently I’m having to go back and forth between illustrator and figma for every single shape to get a proper dashed line. 

When creating a component, I might use one setting of the extended collection, however, it always fixes the "Default" mode, which means, if I want to change the mode in an instance, I have to manually pick that mode regardless of it being applied on a parent container.Ex: A Collection with expanded brands, and dark and light modes. If I decide to use Brand X (not the default brand), it immediately applies the light mode, and every time I want to use the instance of that component, I need to manually set it to Dark mode even though the dark mode is used in that specific frame or section.I don't know if this is the intended behaviour, and if it is, I would suggest to consider changing it and always inheriting the mode from the parent unless otherwise stated.

Why do variation controls get hidden when I'm in the scale command!!! It's really irritating to have to switch out of it just to change a variation