Suggest a Feature

Hey wonderful people at Figma, I love the new variables, absolutely love love them! Here’s just an idea, but when adding a numerical value variable, I wish I could include only “Paddings” as the supported property. Right now when I want to save paddings I have to use “gap (auto-layout)”. While usually these properties are the same value and I can see the though behind not separating them, I do want to play around with them and would like them to be separate, especially when changing modes for device sizes. Additionally, I’m not gonna start a new thread and I’ve already upvoted the ones I’ve seen, but I would also really like if I could use prototype interactions to change between modes. Thanks and have a lovely day!

I’ve already started using the new slots and I find them amazing, but I think it’s very limiting to prevent the use of grid layout. 

Hi I suggest that Figma includes a “Copywriter” permission level, allowing designers to grant edit access to copywriters for text editing only, preventing displacement of elements. This would enhance collaboration between designers and copywriters, who play a vital role on product teams.

 Currently, when viewing a prototype in Figma, it would be very useful to have Back and Forward navigation buttons, similar to those available in web browsers.These buttons would allow users to navigate between previously viewed and next prototype screens without needing to restart the prototype or manually navigate through the flow again.This feature would be especially helpful when reviewing multiple screens, testing user flows, and presenting designs to clients. It would make prototype testing faster, smoother, and more convenient.Suggested functionality:Back: Return to the previously viewed screen. Forward: Move to the next screen in the navigation history. Enable these controls directly in the prototype preview.Adding this feature would significantly improve the prototype review experience for designers, developers, and clients.

Hi Figma community 👋Our team manages a shared design system that is actively evolving, and we frequently update components to improve usability and consistency.One challenge we often face is tracking component updates across project files. While Figma provides version history and “Compare with previous versions,” identifying changes requires opening each component individually. This becomes especially time-consuming when updates affect many components or multiple screens.It would be extremely helpful if Figma could provide better visibility into component changes, such as: Notifications when a referenced component has been updated Visual indicators showing which components have changed A clearer diff or change log for component updates This kind of functionality would greatly help designers, PMs, and developers understand whether updates require action on existing designs.Curious if other teams managing large design systems experience the same challenge? How are you currently hand

Hello everybody, I have almost 8000 hidden components (they are without . or _ prefixes) in a library of almost 10000 components. Does someone know how to unhide them so that they appear in the shared library? For now I am right-clicking each hidden component and selecting ‘Show when publishing’, which takes 2-3 secs… So I hope to accomplish this task roughly in 5 hours, if I don’t take breaks…

Currently there is no way to make a tokenized mesh gradient with transparency.👇 Sample code from a Claude mesh gradient maker, bound to Figma color variables. .mesh { background: radial-gradient(181.01% 100% at 0% 100%, var(--ramps-amethyst-08, #653FC6) 0%, rgba(101, 63, 198, 0.00) 100%), radial-gradient(99% 99% at 100% 0%, var(--ramps-info-06, #88AEE4) 0%, rgba(136, 174, 228, 0.00) 100%), var(--ramps-amethyst-02, #F0EBFF);}This is impossible in Figma due to the lake of transparency.Once you use a tokenized color in a gradient, you completely lose the ability to make it transparent, without breaking it. Once you break it, light/dark modes no longer work.Seems like it would be relatively simple to make a transparency dropdown next to the tokenized color. 

Our design system leverages mix blend modes for hover states so our icon buttons appear on any background color and remain accessible, without needing separate hover–on-primary, hover–on-secondary, etc tokens. We use multiply for light theme, and screen for dark theme. It would be really awesome if we could apply blend modes directly to the color variables, OR support blend modes as variables in general. Our current work around is to apply the blend mode directly on each component variant, but this requires us to define separate light and dark theme variants. would be great if we could use variables here to have it automatically switch between light/dark.

Love the basic set available, but let’s be honest — how often will we get new music? Why not just let me upload my own jams? Like this AI Theme Song I made to pump up the team before our semi-regular Design Workshops…

Figma needs a glyph panel to access glyphs per specific font. Photoshop and Illustrator have this feature and it is a necessity for typographic design. Having to leave Figma and go to Photoshop or Illustrator is incredibly inefficient. Implementing better type setting tools within Figma would be a major improvement

make it so like you can add margins/padding in texts objects, like u can in vscode. example of what i mean:https://youtu.be/57ufN6eJPDs i think it will be very useful; maybe what can be done is that u can add more properties under the alignment tools for the margin control

Hi everyone,I often run into an issue when creating components: I want certain properties to be mutually exclusive.For example, inside a component (most of the time it’s a product card), I have Block A, Block B, and Block C, each controlled by a boolean toggle. If I want to switch from A to B, I have to manually turn B on and A off. This quickly becomes tedious, especially with multiple options.While variants are an alternative, they become impractical when dealing with many of this mutually exclusive choices, and they add too much complexity and file size.Conditional logic could also work for this but it is such a pain to do for this simple and recurent use case that I consider it as not a viable option for a day-to-day workflow. Feature Idea:It would be great to group boolean properties so only one can be active at a time—like a set of radio buttons instead of multiple independent toggles.Would this help your workflow too? What do you think?

Unified Variable Mode Switching Across LibrariesWhen multiple published libraries contain variable collections with identical collection names and identical mode names (for example: collection “Theme”, modes “Light” and “Dark”), Figma currently shows a separate mode switch for each library.It would be much more efficient if Figma detected matching collection and mode names and presented a single switch to the user. Changing the mode would automatically update all matching libraries at once.This would greatly simplify multi-library design system setups where core tokens, and product-specific tokens are split into separate libraries (and different design teams) but share the same theming structure.

Is it possible to obtain a free subscription to the Professional package for non-profit organizations, and what evidence is required for this? Thank you for your response!

Hello ! Everything is in the title 🙂 I really do think that Figma should work on a functionality that would allow designer to insert icons/images/etc into text content while keeping the responsive aspect of our design. Waiting for that update so bad, but if anyone has a hack to do it, I am aware! I already tried using auto layout but I had to split my text and it is painful when I want to make changes… Most of Adobe softs know how to do it. Ask them to share their knowledge, haha! Please Figma, read me. Hear me. Do it. ^^ Thanks!

I have hacked my way to do this Drop Cap on Figma but I think it’ll be a good feature to consider under the typography property.

I wish that the badge was able to trail behind the text and wrap to the next line, as if it’s part of the text. Right now, the only way I can make this happen and still be responsive is to give each word its own textbox and let the container with the words & badge wrap, but that surrenders my ability to use ellipsis.

Would be nice to have the ability to insert a UI component that sticks to the end of multi-line text similar to how the ::after function works in html. usage for this in my field is a “caret” (>) or external link symbol following link text. would be helpful for “buttons” as well.

QOL feature request.I will never want AI in my workflow and it’s just kept being marketed to me which takes me out of the flow. It also gets very tedious to block these features one by one with a browser extension.It would be a very useful and friendly feature to make Figma account fully AI-free with a single toggle. I’d make it up to my team members if they want to use AI, so I wouldn’t make this a team/org level setting.

This makes it easier to use components in designs for different screen sizes. And then you don’t have to calculate every time what 40% or 60% of the width is. This also makes it easier to design scalable applications that grow with the width of the screen.

Now that Figma has local variables and modes, is there a way that a component instance variant can changed based on mode? Basically, I have it set up so that when I define my main frame as ‘desktop’ mode, the margins are 32, and when ‘mobile’ mode is chosen they are 16 which is great. However I also have a nav bar, which is very different between desktop and mobile. Previously, i’d create two component variants, (desktop and mobile, but this means I have to change it on every screen manually. Ideally I’d like variants to swap out based on mode (or even frame width)

Please, for the love of God, add a keyboard shortcut for superscripting and subscripting. When I copy legal text over from an outside source, the superscripted trademark and copyright symbols do not carry over as superscripted. It is tedious to have to redo this in Figma and open the menu every time instead of using a keyboard shortcut.

Why doesn’t autolayout support inline layout This kind of design of including rich text elements (spans), icons, emojis, chips, and images inside a block of text is becoming increasingly popular and seems like it would be straightforward to implement. Im currently contemplating building a Figma plugin that would split a text block into individual words, then wrap them in a ‘Wrap’ auto-layout frame. This way you could insert arbitrary elements inside the text. @Figma pls

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

There’s currently no way to wrap text around an object like an icon, spot illustration, or image. The only solution is to manually break the copy into 2 text boxes and add the second one underneath the icon. We had big plans for our design system to include scaled variants of components where text would need to wrap around icons and spot illustrations to save screen space. So not having this feature makes it hard to design for accessibility and see how components will scale. It’s a little tricky to get the line height right, and also means we can’t easily add scaled variants to our existing design system library. It’s also stopping us from creating a plugin where designers could stress test their designs with larger accessible fonts. Would be great if Figma could add this as a feature. Has anyone else had this issue? Is anyone using a plugin or workaround to help solve this?