Share Your Feedback

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.

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

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

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

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!

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. 

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. 

Hello Figma team,I'd like to request the addition of spell checking support for the same languages that are already available in Figma's UI language settings.Currently, Figma only offers spell checking for English, which creates challenges for designers working in other languages. When creating designs with Portuguese content (or any other language), I don't get any spelling error indicators, making it easy to miss typos and grammatical mistakes.Interestingly, Figma already supports these languages for the UI/interface translation:• Japanese (日本語)• French (Français)• German (Deutsch)• Spanish - Spain (Español España)• Spanish - Latin America (Español Latinoamérica)• Korean (한국어)• Portuguese - Brazil (Português do Brasil)Since these languages are already integrated into Figma's interface, it would make sense to extend this language support to include spell checking in the text editor as well. This would create a mo

When I set paragraph spacing for the block of text, the bullets ignore this spacing, and stay at 0px. This is weird.

Al ordenar los proyectos de figma, me gustaría poder ordenarlos en carpetas, como la de favoritos en el side bar, aparte de que al exportar me dé la opción de como quiero guardarlo, en carpeta, por separado, etc.

I just got here.  Obviously Figma has been around and I’m new… and good, because with a fresh pair of eyes, I have to ask: WTF, Figma? How many little “X”s will I have to close before I can finally use the app?  Boxes of propositions and I haven’t even gotten here.  Tip boxes to tell me things before I have even had time to click a single feature in the product.  I mean, there were like 4, or 5, just now!  And then when I was finally ready, the page refreshed to pop another product feature ad up at the top. Oi.  I just want to use the app. This is the kind of UX that makes people throw keyboards at the wall.  SO FRUSTRATING.

As administrators, we are constantly annoyed by “false” licence upgrade requests.All users get different modals that urge them to ask for an upgrade, even when it’s not needed (eg. they’re invited to collaborate in an open session, hence can edit without licence upgrade). This leads us to have to re-qualify every single request to determine if there is a genuine need, or if it's just someone who clicked to get rid of the modal (90% of the time).Is it possible to disable these modals inviting users to ask for an upgrade? It is a real burden on a daily basis.

I’ve been building a project using Figma Sites and I’m running into very slow loading times when navigating pages. Even after compressing all images and simplifying the design, the performance hasn’t improved.I ran a network analysis and the issue doesn’t appear to be assets or images — it’s the initial page response from Figma’s server.Here’s what I’m consistently seeing across pages: Waiting for server response (TTFB): ~2.9 seconds Content download: ~3 ms Connection/queueing: negligible So the browser is waiting almost 3 seconds before receiving the first byte of HTML. Once the response starts, the page loads instantly.The request structure also shows that each page loads through: /_runtimes/sites-runtime.*.js /_components/v2/*.js /_json/{page-id}.json …suggesting that Sites dynamically assembles each page on the server. Combined with:

I recently upgraded from a Starter seat to a Collaboration seat, expecting to gain access to AI features and the ability to share projects with clients.However, I'm experiencing significant limitations that are affecting my workflow:I cannot use plugins on any projects (both existing and new) I cannot share projects with clients Other essential features are also restrictedThese limitations are severely impacting my productivity and ability to gather client feedback. When I encounter these issues, Figma displays a pop-up suggesting I upgrade to a full seat. I wasn't expecting the Collaboration seat to have more restrictions than the Starter plan.I previously contacted support via email, but the response I received didn't clarify the situation or resolve the problem. Could you please help me understand:Why the Collaboration seat has these limitations What options are available to restore the functionality I