Suggest a Feature

I work a lot with dashboards a lot which means variable height cards in various configurations. I would like the figma grid to support a “Masonry” layout for grids where the horizontal and vertical gaps are kept consistent.Masonry grid exampleCurrently it’s only possible to have a grid layout that wastes a lot of vertical space like this.Regular gridI’m aware this can be achieved with AL but the responsive layouts are a pain.Please 🙏

It would be really really nice if a series of parameters could be declared when automatically renaming layers: lowercase, uppercase, separators, etc. It could be something similar to the bulk layer renaming feature, but with AI. Use case example: I have a project which has all layer names in lowercase and separated with hyphens, I would want the new layer names to have the same layer syntax when renaming them with AI.

It’s 2026 and Figma still doesn’t have a proper table component feature nor negative margins, shadows & gradients as variable.  

Creating buttons in Figma is fantastic, but when working with multi-layered components that have custom corner details, resizing often causes distortion even if saved as components. This makes flexible scaling challenging and affects design consistency. Don’t you think it’s about time to add native 9-slice scaling support? It would significantly improve precision and workflow. Please consider this feature for future updates.

I want to recommend an improvement to the way Ai uses library (or rather does not use them currently).By default AI cannot see what libraries you have within the assets panel. When I requested use X library It did ask me to add them to assets even though they were already active and available to meAfter a bit of back and forth it then revealed to me the + button under the chat to enable libraries.It make me think this is very unintuitive process. I would expect the AI to simple be able to see the libraries added already to assets and why the need for this (duplicate) step

Please consider addressing the following two common issues with annotations:1. Annotations can obscure the design. When a design frame is selected, it should be brought to the front instead of being covered by unrelated annotations.2. Annotations do not support copy and paste. Users have to recreate and re-enter them manually, which is very inefficient.These are very common use cases, and I hope Figma can address them as soon as possible. 

Obvious benefit would be to allow for things like specific values related to loading to be passed through on the code side... 

When working on a long-term project, the multiple files can get confusing to look through each time. The ability to freely arrange the files (similar to Google Drive) would make finding the file you need easier and quicker each time. Implementing sub-folders would greatly help this process as well. 

Describe the problem your experiencing and how your idea helps solve this A scrollable (clickable) list of items triggers the interaction even if a fixed element overlaps it. Additionally, this bug occurs even if that overlaping element has a “Tap → None” Add as much context as possible (screenshots, Figma files, mockups, etc.) Stumbled upon this issue when I had to position an iOS keyboard on top of an interactive list of elements. Demo file and steps to reproduce: Start the prototype from https://www.figma.com/file/GpbLNhQGrYKCTFO8aZy8BK/Hotspot-bug Click the gray bottom rectangle with or without scrolling It wrongly triggers the hotspot from the “background” items

Instead of being explicit when using Booleans.ie. when there’s 1 variant that is TRUE, all other variants must be labelled FALSE.What about just stating what is TRUE. Then it follows that everything that is not true, is FALSE.So only having to state what is true...

I have a UI/UX flow for a white label app, to create screens for the specific brands/labels I most of the time mainly just copy the screens and adjust the colors and fonts. What would personally really help me, is that we have the same functionality as we have with selecting the frame or component and adjust the “Selection colors” for fonts. Because now for fonts, you would have to select every text object there is within the comp. or frame to be able to achieve something similar. Just as a ref, here is the Selection colors, which works really nice:

When we share a prototype with a client (namely a website visual) we’d like the option to view the prototype at actual size but horizontally centralise it. This allows us to design at 1920px wide with a 1440px grid, and for clients with smaller screens to be able to view visuals without black bars either side, because the background evenly falls off to the left and right. Slightly inaccurate Claude-generated (but still a good enough example I hope) image included to help explain: 

I work at a UX agency and I am helping my client set up a Figma Make Kit for their product. Because of Figma limitations I cannot (a) create a Figma Make Kit or (b) publish / update a Figma Make Kit. This is very disruptive to my and my client’s workflow because I have to ping them to hit update any time there is a change. This is especially frustrating considering how much troubleshooting I am having to do between the Figma Make Kit and the Figma Make project files I am testing in. Has anyone else run into this limitation?

😁

I am trying to export an entire figma make prototype to figma designs. It seems crazy to have to do this screen by screen when there is so much embedded functionality (modals, tabs etc). Is there plan to do this in the future? Or am I missing something 😅 Thank you!

The biggest hindrance I have right now with using Figma Make is the inability to simply chat with the AI and/or make a plan with the AI before it executes changes. From what I can tell, the “Ask to start” setting does nothing different than the other options. I want to ensure the AI has a clear understanding of what I’m asking before it just starts making changes, particularly functional changes to a prototype. For comparison, I have been using Lovable for a while now and use the Plan mode (formerly Chat mode) almost all the time. It draws/writes up detailed plans that ensure alignment between me and the AI. If this is already in development and there’s a way to get early access, I would definitely like to try it. For now, I continue to use Lovable until this functionality is available in Make.

Figma has added percentages to text styles, which is fantastic. However, when the style is linked to a variable, the percentage is removed, and uses px units instead. I am trying to set up my design system using a scalable token system, and little features that don’t quite work are so frustrating. Please allow variables to support percentages! It will help us not need to use plugins like Token Studio. 

Hello, it would be nice to have the option to insert floating components inside text (like Emojis). Use case would be for signs or infos in complex dashboards. Its a hustle to do this now manually and also set kind of boundingboxes to sync different heighs of text and component. Regards

Abstract My team would like the ability to publish versions of multiple libraries simultaneously. Adding version control on a project level instead of on a file level would make this possible. This behavior would more closely mimic the kind repo versioning that our engineering counterparts are able to do with git tool like gitlab and GitHub. Background Our team builds and maintains a design system used by a very large number of designers who work across a variety of themes and extensions libraries. In order to support the various needs of our users we have various library files for tokens, core components, and component extension libraries. Frequently, changes to our libraries involve needing to make changes more than one library; any one of which is being consumed by any number of teams at any given time. We use semantic versioning and make minor releases on a quarterly basis. Problem We need to publish libraries with dependencies (tokens libraries, core components, etc) in order to i

 I cannot find a way to copy the image styles without using the original image. I just mocked up this kind of stupidly but… that would be great if you could do that..  There is no way to actually adjust from image to image. Unless I'm missing something! Thank you for your attention and your great work. I hope that I'm making myself clear. Chris

Sometimes a particular boolean variable can affect several layers. And some of that layers may require inverted visibility state. E.g. Layer 1 is visible when the variable is truthy and Layer 2 is visible when the same varaible is falsy. Let’s say, we have a multiselect field with a dropdown. When we select the first option, it should be added into the input as a label (label layer becomes visible). But also this option should be removed from the dropdown list as it’s no longer availiable for selection (option layer becomes hidden). So, both states depend on the same variable, but their conditions are inverted. It would be nice to have some negation operator when applying a varaible. Kinda logical not (!) in JS: ! isSelected. Or just allow us to apply boolean expressions as we do in prototypes , e.g. isSelected != true.

Right now, tying layer visibility to a variable means if the boolean is false = layer is hidden. It’d be great if we could invert this functionality (boolean is false = layer is shown) on a per-layer basis as I need to show some layers and hide others depending on the state of the variable. Anyone else run into this?

Hello, I was wondering if there was a way to hide the Figma Make chatbot bar at the bottom-left of the UI. I have to use my computer at a higher magnification setting due to visual issues, so the bar takes up a lot of space for a feature I’m not going to use. It’s also distracting to have it type out example prompts each time I open a new board, so I have to stop what I’m doing and wait until the animations stop before resuming my work.Thank you!

A ton of great features launched yesterday. One of them is Autolayout Wrap. It might be just me but I couldn’t find how to wrap from right to left. This seems weird as Figma did an amazing job of closing its long technological debt when it comes to RTL languages. Please tell me this gap has not been reopened again…

As a designer, I'm working on a large-scale Figma project with over 3 years of development. The file includes numerous deeply nested components used throughout the product.Even minor changes to a single component—such as swapping a fill for a stroke on a button—trigger severe performance problems:Figma freezes for 5–10 minutes as changes propagate across all instances. Another 5–7 minutes are needed to sync with the server. The tool becomes sluggish, with 1–3 second lag on every action due to background updates.This makes efficient work nearly impossible. I can't make consecutive changes without waiting for updates after each one, significantly hampering my workflow. Proposal:Implement a feature that allows users to temporarily freeze a component, preventing changes to the parent component from immediately affecting its instances.Implementation concept:Enable a "freeze" mode for the component. Make multiple edits without triggering updates to child instances. When finished, unfreeze th