Share Your Thoughts

I use Sections as an organizing structure for all the prototyped pages in my project. When I am prototyping and creating links, seeing all the Section names is really cumbersome because they make the list long, and I will never want to link to them.It would be nice to have an option to exclude them from the list of linkable 'pages' — similar to constraints for variables.

Suppose I own a file but I want to change/hand over the file to my teammate which I can not do by myself. The other teammate who is going to access has difficulty for those files after removing the email id from which the file has been created. The idea is that the actual file owner should have access/option to change the ownership of the file so that it can be easily accessible to other teammates. Or there can be multiple owners of the file (Max 2-3). Please have a look at the statement mentioned. Thank you!

ProblemCurrently, Figma does not allow designers to create a reusable style for link-like or inline action text.Text Styles in Figma mainly control typography properties such as: Font family Size Line height Letter spacing However, common link or inline action properties like: Text color Font weight variation Underline / decoration intent cannot be defined as a reusable style and applied consistently across files.As a result, designers either: Manually restyle text every time, or Convert text into a component, which is not ideal for inline usage inside paragraphs or labels. ExampleA typical UI pattern:“By continuing, you agree to the Terms & Conditions.”Here, “Terms & Conditions” is an inline text link that needs: A specific color token Slightly different font weight Optional underline or visual emphasis Today, this styling has to be applied manually each time, which makes consistency difficult in large design systems.Suggested ImprovementIntroduce a way to crea

Currently check designs suggests the wrong tokens even though I have explicit names for tokens.For example, it tells me I’m using a hardcoded value for a horizontal or vertical gap, fine, but it suggests a border radius token or border width token. Meanwhile, I have tokens called “spacing” that could be suggested.Same thing for corner radius adjustments, it suggests border widths even though I have border radius tokens.Is there a way to configure this if we can’t get the “smart” version yet?Thanks ! :) ps: the feature is really nice by the way and already saves a ton of time ! 

Khi tôi gõ  >= hoặc =<, tôi rất kỳ vọng Figma có thể tự động chuyển nó thành ≥ và ≤

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

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!