Suggest a Feature

Problem Currently, Figma Number Variables do not support percentage values for line height. This makes it difficult to create a consistent and scalable typography system using variables.Many designers prefer to define line height as a percentage relative to font size rather than using fixed pixel values. For example, a heading might use 125% line height, while body text might use 150%. Suggested Improvement Please add support for percentage values in Number Variables, especially for typography properties such as line height.This would allow designers to create reusable variables like:line-height/tight — 120% line-height/normal — 140% line-height/relaxed — 150%Designers could then apply these variables directly to text styles and maintain consistent typography across their design systems.BenefitsMore flexible and scalable typography systems. Easier consistency between font size and line height. Better support for design tokens and design system workflows. Improved collaboration between

I know things are changing fast but I am struggling to find documentation or UI that explains if it is possible to use git for Figma Make templates. I work on a Design System team who wants to encourage use of our Figma Make template and right now the workflow of updating it is a bit cumbersome. Even naming versions in the UI appears broken (Publish → Publish History → ‘Name this version’ (nothing happens)).What is the roadmap here? Ideally even if it is going to be locked to changing inside the browser please add diff comparison feature and the ability to upload the entire dir vs one file (then we can at least use the download code button that exists now, work in our IDEs, reupload with all changes and look at diffs before publish).

Can Figma's personnel management feature be enhanced with a "Name Notes" function? Many usernames are email addresses, and some collaborators may only be temporarily involved in a project, so they are reluctant to take the time to change their Figma nickname. During periods of personnel turnover, when it comes to adding permissions or removing team members, it can be very inconvenient to manage as it is difficult to distinguish one person from another.

I would like to request that drawings made with the Draw tool in Figma Make are automatically saved, even when the user closes the window before submitting the prompt.Currently, if a user runs out of AI credits and cannot send the prompt, all drawings and annotations are lost when the window is closed.It would be very helpful if the Draw tool's markup could persist in the file or chat history, so users can return and submit their prompt once their AI credits are replenished. This would prevent the loss of significant work and improve the user experience.

Hi, Figma! I’m just here to suggest a simple split frame feature. It would be similar to the layout grid, but it would in effect create new frames inside a current frame. (It would be more useful than the grid for me).Frames could be split either horizontally or vertically and it would make creating tables super easy and other divided areas. Each frame with individual auto-layout if needed.This split function would split the frame into equal parts (columns or rows) and auto arrange them as individual frames inside the original frame. So if I create a frame and split it in 2, I end up with 2 smaller (equal size) frames inside the original frame. Just a suggestion. I love Figma. Thank you forever for creating it!Maricel

Playback behavior can’t be controlled from the component. There is currently no way to configure an animation to play only once and remain on its final keyframe instead of looping or resetting. The playback duration of an animated component nested inside another frame depends on the parent’s timeline. If another animation within the parent frame has a longer duration, the nested component must wait until the parent’s entire animation cycle is complete before it can play again. This makes it impossible for nested animations to run independently.Some possible solutions 🤗 ✅   Allow loop behavior to be configured at the component level. Add options such as Play once, Loop, and Stay on the last keyframe so the playback behavior can be controlled independently for each animated component. Decouple nested component timelines from their parent timeline. Allow animated components inside other frames to run on their own playback cycle, regardless of the parent’s duration, so each animation

Colored tokens are correctly displayed in the Figma preview of Lotties, but this is not yet the case when exporting to .lottie, which requires two exports, increases file size, and necessitates mapping on the developer’s end.We would like to be able to manage this mode directly within a single asset.

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!

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. 

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

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.

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)

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