Share Your Thoughts

Original Situation:I am working in the Figma tool, and while checking the preview of my designed screen, I encountered an issue. In the preview (actual size), there is a Figma header overlay. Parts of that header are not fully visible or clickable if I place a link within it. The overlay’s position and size seem to block interaction with elements in that area, especially when I move the cursor over the header section.Idea / Suggestion:It would be very helpful if Figma provided an option to adjust overlays vertically (in addition to the current positioning options). This would allow designers to better control the placement of overlays and ensure all parts, including headers with links, are fully visible and interactive during previews. I am sharing this idea to improve usability for designers and collaborators. Please refer to the attached UI for a better understanding of the issue.

Hi Figma Team, As a plugin developer and daily Figma user, I’d like to request an enhancement to the Plugin API. Currently, image adjustment settings such as exposure, contrast, saturation, temperature, tint, highlights, and shadows—which are adjustable via sliders in the native Figma UI—are not accessible via the Plugin API. The imageFilters property on nodes like RECTANGLE always returns default values, even when those image adjustments have clearly been applied through the UI. This limitation makes it impossible to build plugins that copy and reuse image adjustment settings across multiple image layers, which would significantly improve efficiency in projects that require consistent visual styles across many assets. Request:Please consider exposing the actual values of image adjustment parameters (filters) via the Plugin API—either through node.imageFilters or a new method—so plugins can read and apply those settings programmatically. This would enable:  Copy/paste image filter sett

I wish Figma will create prototyping functions so i could create a function template and send him the request variables, just like in javascript, a function that holds set variables, conditions and more. That will save a lot of prototyping time and the interactions will be managed better for changes. Currently, if you have a lot of variable interactions then it’s a hard to manage repeated interactions with small changes and adds or even keeping track of the prototype logic. I wish it will look like this: Creating the variables Creating the functions Applying functions to the prototype. Managing logical functions for changes Check out my screenshots to understand my pain of managing all of this.

Have you ever sent over a design file for feedback to open it a week later with 40+ comments? I have and I’m sure you have too. The problemIt takes a lot of time to review comments after a feedback round. It can get repetitive and sometimes the feedback can mean the same thing but being written differently. If you have a lot of different commenters, the list becomes long and tedious to go through. The solutionOne button to summarise comments that will produce out a summary and propose the next steps. Each summary should include links to the root comment so the user can review the original comment. The summary could be in a tab in the comments panel where you can toggle between original comments and summary to easily go back and forth. 

UX 101: do not do anything automatically that a user may not want. I have not once wanted a full stop (aka period) inserted into a text box when I hit spacebar multiple times. This is in the same camp of automatically adding a link when pasting (not once have I wanted this) or automatically turning text into a list. These should only happen when a user specifically adds these using UI.

Figma Design allow you to organize in a sub-folder like structure inside files, with multiple pages possible per project. Figma Slides however only consists of one top level presentation, not allowing you to create multiple presentations inside each file. This leads to a lack of organizing possibilities, and if you have multiple presentations or projects per client, things can get chaotic pretty fast. The option to nest folders inside each project in Figma Slides is a must, as I see it, or it will be impossible to keep track of presentations in the long run.

When working with a library that uses a large number of components and states, I think that like how we have a “direct select” tool for colours, we should also have a “direct select” button for component items.In my image, I have a component that has some booleans set up along with how I imagine the button would look and function. It would greatly help to have the same functionality we have to select any items using a specific colour with the “target” button beside it. This reduces time direct selecting items especially if there are items above the layer you intend to select. It also allows users to stay in the right panel for changes and adjustments if they can direct select the component element.  

Hi Figma team,I wanted to share a small pain point I keep running into — and maybe a solution.As a UI/UX designer working on complex SaaS and mobile projects, I often end up with Figma files that have dozens of frames across multiple flows. Despite careful naming, it's easy to lose track of what’s ready for dev, what needs review, or which version belongs to which client.Lately, I’ve found myself wishing I could just tag frames — like #ready, #needs-feedback, or #v1.2 — directly on the canvas or in the left sidebar.Something lightweight, like sticky labels or even a built-in tagging system, would make navigating and collaborating inside Figma so much smoother.Right now, I rely on naming hacks or color-coded backgrounds, but it gets messy — especially when the file grows.I imagine a world where I could quickly filter or search for #mobile or #dashboard and instantly jump to relevant designs.Thank you for building such a powerful tool already. I just thought this small improvement could

You know how sometimes you feel like having a copy of a screen in another file (or page), and would like to have it be updated automatically, but it feels overkill to create a main component out of that screen? If you just copy and paste it (for example for creating a prototype in a separate Page without messing your original screens), it’s pretty much instantly out of date. You also know how you can embed Figma files, frames or prototypes in any website, even integrating in other services like Jira and Dropbox with the Live Embed Kit. It works AMAZING, it shows even up-to-date designs, and you’re simply copy-pasting a link, without the overengineering of extra components. What if this would work within Figma itself?? Check this out: Would this be useful for anyone else? We for example would like to have an example of “usage” of each component in the Components Library, which is usually a screen taken from a variety of other files. But they invariably get out of date super soo

Hello,My developer pointed out to me that when they view the Figma files in Dev mode, the font information only shows this: color: var(--rgb-353132, #231F20);font-family: "New Science";font-size: 24px;font-style: normal;font-weight: 700;line-height: 30px; /* 125% */ Are you able to have dev mode show that information within the css styling?

Hello, I know some of you already submitted feedback regarding Figma Grid in Beta and I share the same frustrations regarding rows and columns attribution/organization and size management. Would be great to be able to just select a grid’s column or row or multiple and handle bulk edit. Removing rows and columns are really a pain. I have another issue and wanted to see if it’s a shared one? If I remove a content from a grid cell, or if I move some around and then decide to undo what I’ve done with ctrl +z, I have no history of what has been done in the cell, it’s gone :(. Does it happen to you guys also? 

It would be beneficial if Figma included the option to enlarge the interactions panel. Reading all the conditional and variable interactions within the small preset frame size can be challenging. Enabling users to expand the panel size, similar to the way the variables frame can be expanded, would make it easier for users to review the interactions they have set. Being able to copy interaction would be extremely helpful and reduce redundant work

Is there a way where i can bind the border with a bolean variable in which i can show it on or off.

Something that would really help me to present my design once it is finished would be to have the ability to copy and paste sections of the completed design to another page and be able to change the prototyping behavior on those sections independent from the main design. The purpose of this would be for example, if I am showcasing a particular mobile screen and it’s capabilities I want the viewer or user to only be able to go so far in the prototype and have to move on to a different Flow in order to be able to see the next interaction or sequence of interactions as I see fit. This would help greatly in being able to use Slides effectively in terms of controlling the narrative of a project. The other obvious benefit is that up to date some interactions only work as designed when the viewer starts that interaction from a certain place in Prototype chain. This ability to separate out sections of the design as I have described would enable me eliminate people viewing interactions in any o

With regular horizontal or vertical auto layouts, we can shuffle/move child items of the auto layout using the arrow keys.Why has this not been implemented in grid auto layout?  Users should be able to use the arrow keys to move grid child items up/down rows or left/right columns.In general, I have been finding grid very hard to work with.  It’s very unintuitive to populate a grid with items—you try to drag and drop items into specific spots and the items never land in the spot you tried to drag them to, and then it always ends up adding extra rows or columns.  And then once a grid is populated with items, it is extremely difficult to move the items around in it, because it requires that you basically either remove the items from the grid or drag and drop them over one another, and this presents all the problems described above.  A user should just be able to move grid child items around with the arrow keys just like any other auto layout,

Hi! First, thanks to the Figma team for all the hard work. Now, let’s talk about Figma Slides Templates. To edit the template styles, I have to select a slide first — which feels a bit unintuitive. In Figma, when you click on the canvas without selecting anything, you can access the file’s styles. Can we bring that same concept into Slides?When I open the template selector, I can edit the styles there through a dropdown. Is that really the best or only way to manage styles in Figma Slides? I don’t think so.Colors & Text Styles: I can delete them, but only through a pretty complex interaction — right-click?Layout Grid: How can I set a default grid? Right now, I have to manually add my custom grid to every new slide I create. If we can't set a default, the feature kind of loses its purpose. :(  

I was editing some screens and Fimga just popped me to the home screen and showed me an advertisement for their new AI. This was so disruptive and disrespectful to the task I was trying to do. And it made me SO angry that I had to spend the time writing this feedback--and now I have to get back to WHAT I WAS TRYING TO DO IN THE FIRST PLACE. 

I’d like to suggest an improvement that would streamline the design process—especially when working with components.Currently, when resizing or aligning elements, I need to press the ALT key to view spacing measurements (such as padding, margin, and distance between elements). This adds unnecessary friction, especially during frequent adjustments.My suggestion is to add a toggle in the settings that allows users to always show spacing measurements by default. This way, whenever an element is selected, its padding, margin, and size can be instantly visible—without needing to hold down a key or guess the values.This feature could be customizable. For example: Always show padding/margin/size values when selecting an element. Let users choose which measurements they want to see by default (padding, margin, width, height, etc.). This wouldn't overcomplicate the UI but would significantly increase efficiency, especially for developers, UI/UX designers, and those working with design systems

Maybe I’m missing something (and I know it’s in beta right now so I’ll manage my expectations accordingly), but it doesn’t seem like you can set a min/max on a container with the new grid auto layout option? It seems like such an odd decision to intentionally remove it for no good reason (that I can see) I wanted to ask and see if everyone else is missing this or if it’s just me?              

Hey there! It would be helpful to allow additional metadata to be stored on pages, which could then be queried via the search function.In daily use, this could include alternative titles (especially useful when using a page for one software feature), specific variants or identifiers that refer to third-party software (JIRA numbers), or version numbers. Adding a date field would also be beneficial, especially when working with large files, to better track updates and content relevance.

In the properties panel to the right of the name of whatever you have selected some options pop up such as multi edit, select matching layers, use a mask and/or 3 dots for more options. What is odd is that when I select a variant for example from one component those options can be either wildly or subtly different than if I select a variant from another basically identical component. It almost seems random to me though I’m sure it is not. Is there a resource that could illuminate not so much what is showing when a selection is made but why that particular pop up icon is visible so as to get a better understanding of what inconsistencies might be happening on my end? Always curious. 

During design system development, we often encounter components that could be simplified as templated versions of existing ones.Examples: A datepicker is essentially a pre-configured text input. It could be created simply by setting specific properties on a standard text input component.  A menu component could serve as a generic list for dropdowns, but we could offer templates like "Countries", "Categories", or "Currencies". Adding these templates to the design system would help designers avoid "reinventing the wheel" by creating slightly different versions of the same pattern.Proposed UX for Template Instances in Figma: Create a generic component. Create an instance of that component. Customize its properties as needed. Click "Save instance as preset" or "Save instance as new component". Give the template a name. The template appears as a selectable option (e.g., in a dropdown) when creating new instances.  

I think it would be interesting if plugins inside Figma could be organized by categories, similar to how it's done in the Community. You can see in your menu that your installed plugins are already arranged in a way that helps you better understand how each one works.

Screenshot from Figma's right panel, focusing on "Go to main component in library" under a component  When using components in my team, I often missclick this link under the instance selector dropdown. Working with my library closed consumes less memory, so that's why I do it - but everytime I hit that button it opens my library and takes me away from the file I'm working on.I work with low DPI (650), so I feel like that my issue isn't about not being able to hit the instance dropdown, but rather the proximity of the click area of the elements.Does anyone feel the same?

In one of my projects I was wanting to capitalize a single word, but realized I didn’t have the ability to do so without it being manual. I feel a shortcut, even if its just in the drop-down sub menu, would be useful for multiple selections that need to be capitalized especially when it’s not the whole sentence/paragraph.