Share Your Thoughts

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

It’s very inconvenient and slows things down when you add an additional fill with 20% opacity. You have to go into the opacity settings every time and set it to 100%.

I’ts so freaking annoying that you can’t collapse the assets panel! 

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. 

Hey everyone,This has been driving me (and apparently hundreds of others) crazy since 2021: there is STILL no native way to properly move or duplicate an entire page from one Figma file to another.Copy-paste or “Select All” destroys page background/grid/rulers, breaks prototypes, loses comments, turns library styles into local duplicates, and forgets locked/hidden layers. Duplicating the whole file then deleting pages is the only “workaround” — but it’s a nightmare with 50+ page files or design systems.I’m a fellow designer who’s fed up and seriously considering building a free Figma plugin called PagePort that would let you:Export any page (or batch multiple pages) with 100% fidelity (layers, auto-layout, constraints, page props, prototypes where possible) Import into any other open file in one click Choose Move (delete from source) or Copy Smart remapping for styles/variables/libraries + basic prototype reconnection Progress bar for large pagesWould this solve the problem for you? Wh

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

The system is showing that AI credits are still available, but AI features remain unavailable and display an “out of daily AI credit” message. This creates a mismatch between the user’s remaining credit balance and the access state shown in the product.  

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 last used Figma make a month ago, and whatever change was made to the default LLM made it unusable. The default selection picks an LLM that can’t produce even the most basic protoype and is unable to follow instructions. It was a powerful tool that I highly recommended but I’d be embarrassed if someone tried to use it with the current default LLM. A lower token cost doesn’t matter when the tokens are wasted by failed outputs. 

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.

Don't get me wrong, I love working with figma and I greatly appreciate what value this software has done for designers and business. However, I will never understand why such simple solutions as folders for pages or "CSS Margins" (the basis in HTML) have not been included in this software for many years. I understand the pursuit of money and the AI ​​trend, but don't forget who makes your business run. People are very willing to jump to an alternative as soon as it appears and offers what you haven't been able to offer for years. Don't make the same mistakes as Adobe.

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. 

Dear Figma Team,I am experiencing several issues with Figma Sites and would like to share some feedback: CMS Collection Export I would like the ability to export CMS collections so they can be imported into another file. For example, when upgrading to a newer version of a site, it is not practical to recreate all CMS content manually and fill every field again. Plugin Access in Figma Sites It would be helpful to have access to plugins within Figma Sites, particularly for accessibility checks and other quality assurance workflows. Figma Make Integration Figma Make does not seem to work properly within Figma Sites, especially when it comes to responsive layouts and responsiveness-related adjustments. Styles Management At the moment, I am unable to create, edit, or delete styles in a Figma Site file that I created myself. Interestingly, another Figma Site file that is already live works as expected, so the issue appears to be specific to this file. Are ther

The setup docs for Code Connect UI show the GitHub Install & Authorize flow, but they do not explain why the app requests repository write permissions such as administration, code, checks, and pull requests. Please document what each permission is used for, whether any repository settings are modified, and which permissions are required for specific features versus GitHub’s standard app authorization model.

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