Share Your Feedback

Its just confusing that we have a +1 that is not interactive and a very similar one that you can press and increment it. Would be nice to differentiate the interactive because people often just put the non-interactive one that is not desired

When working with both Design view and Figma Make view, editing local components becomes difficult and noticeably slow in Design view especially while typing or making text-level edits.If I’m exploring or generating an idea in Figma Make and then switching to Design view to refine it or prepare a handoff, working inside the same local component across both views feels friction-heavy. Text input and real-time edits lag significantly, which disrupts the flow of iteration. Performance drops and context switching makes it hard to work efficiently.This becomes especially challenging during handoff, when ideas generated in Make need to be quickly refined, adjusted, or structured in Design. The slowdown during typing inside shared local components makes even small refinements feel cumbersome and breaks momentum.Suggestion / opportunity:A smoother interaction between Design and Make when editing local components particularly improving typing and text-editing performance or a clearer separation

hi, im encountering condition where my file in figma make get warning of high memory usage, and it seems not because the amount of code that generated, i think it’s the cause is the chat is to heavy. any idea why this is happening?if the chat is the cause, i think add a chat deletion feature will be helpful, thanks

SVG is often treated as a simple export format — click “Export as SVG” and move on.In reality, SVG quality depends heavily on how the vector is generated, especially when starting from raster images like PNG or JPG.Over the last months, while working on SVG conversion workflows, I noticed a few recurring issues that designers and developers run into.1. Why raster-to-SVG conversions often look badMost automatic converters try to trace everything: noise gradients shadows anti-aliased edges This results in: overly complex paths huge file sizes SVGs that are hard to edit in Figma The key insight: clean input matters more than the tracing algorithm itself.2. Pre-processing before vectorizationBefore converting to SVG, it helps to: remove backgrounds increase contrast simplify colors isolate the main shapes Even basic cleanup dramatically improves path quality and makes the final SVG easier to edit or animate.3. Optimizing SVGs for real useA usable SVG is not just visually co

WHY CAN’T I ZOOM INTO WHAT’S SELECTED? CTRL+K, NOPE, IT’S GONE. I’M NOT LOOKING FOR SHIFT+2. IF YOU WORK AT FIGMA AND YOU’RE READING THIS: I’VE BEEN A DIEHARD SINCE 2016, WHICH MATTERS NOTHING, BUT I HATE EVERY THING YOU’RE DOING TO THIS SOFTWARE.

Figma has to be one of the worst pieces of software every created by humans. Seems promising and then the amount of frustration and time you waste using it becomes unimaginable.Mobile app sucks so much and is so slow and sluggish on iOS that I cannot use it for more then 2 minutes before wanting to just delete it off my phone.How can the Figma team be so terrible at their jobs?

My biggest issue with Figma Jam is tables. For instance, it's impossible to paste complex data from a Google Sheet into a selected table. You can only paste into a cell or create a new table; you can't paste into an existing one. You could paste as a new table and then copy a column to paste into another table, but that's just a mess I can't deal with.Basically, it’s a half-baked component. Figma team, please take a look at the Miro table component and its capabilities if you want more people to use your tools.

I am experiencing, that every time I use iOS26 components from Apple’s recent Figma UI-kit to make a prototype, my phone (iPhone16) lags like crazy and all interactions seem sluggish. It is very annoying that liquid glass is killing the prototyping experience. Also drains the battery Happens both with a mirrored frame or a prototype link. And also only between two screens.Anybody else experiencing this? 

I use the assets panel frequently to use our design system. The new layout with the sidebar obscures when our team’s library has updated, and it feels much slower to find and access assets. Instead staying in the same work area it feels cumbersome to move horizontally to the side nav, then back up to the search bar in the assets panel. I really dislike the new navigation, though I can understand wanting a clearer separation between these two domains. It just makes it slow for me as a user. 

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 — small but powerful. This feature helps new designers avoid messy component libraries and helps teams maintain consistency without spending hours on manual variant organization.

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.

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

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 and scale.---Practical Problems with Grid1. Flat and Unmaintainable HierarchyWith Grid, we end up with a flat structure: Table > 70 direct children (for a 7-column × 10-row array).Consequences:- Un

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 opacity because “k” + “.5” now switches to the scale tool and then drops the opacity to 5 because the #x scale field isn’t

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!

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. 

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

Right-click as the way to apply a variable (boolean) to the appearance of an element is so difficult to discover I am amazed it’s really organized that way.This offers zero discoverability - there is not even a clue in the tooltip - I had to check for how I’ve made it several weeks ago - I forgot how to get there.Please, why don’t you use the same pattern as for the rest of things (dropdown) or so.

Hi Figma,  I really like the Variables panel but why does’nt it support dots in naming variables? For example: basis.text.font-weight.default is much more clear than naming a variable basis-text-font-weight-default. Dots bring in some more possiblilities. I know I can use underscores instead of dots, but underscores look to much like hyphens. Thanks in regard.