Suggest a Feature

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

Request: Through the Figma MCP, access contents of comments made in Figma Design file.Reason: Can provide context for designs, review bugs, etc.Current response from OpenAI Codex with direct link to comment:No, not the comment itself.What I can see from that link is the node it points to:file: XXXXXXnode: XXXXXXscreen: /sign-up-2 (iOS)That screen contains:nav title Sign UpEmail and Password inputsSign Up primary CTAContinue with AppleContinue with Googledivider OrAlready have an account? Sign inbottom legal linksBut I still cannot read the actual Figma comment thread or the #XXXXXX anchor content from this session.If you want, paste the comment text here and I can map it to this exact screen and tell you what change it implies. 

I’ve been thinking about how the design of SIM registration forms affects the user experience, especially when users have to provide several pieces of personal information.A well-designed registration flow could make the process much easier by using clear form fields, helpful validation messages, progress indicators, and simple mobile-first layouts. This seems particularly relevant for services such as smart SIM registration, where users may complete the process entirely from their phones.For those working in Figma, how would you approach designing a SIM registration flow? Would you use a single-page form or break the process into several steps? I’d also be interested in seeing how you would handle error states, document uploads, OTP verification, and accessibility without making the interface feel overwhelming.

With the new update, we have a great new feature, but unfortunately, it’s not usable with our component structure. Exposing all props of a nested instance also exposes props that we don’t want in the context of the consuming component. What if we could also select which properties to expose? This would lead to a cleaner sidebar with only valid props.

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!

It’s just very bright, and I’d like to get some work done at night without killing my eyes. Please add dark mode. FigJam especially, but it’d be nice throughout. Yeah, just remember the user likes a dark mode, and make dark mode the default for everything: your website, this forum, Figma, …

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. 

Figma motion does not currently have the ability to play and export video fills, so video objects are treated as static images. The ability to incorporate video objects into the timeline would be extremely helpful. Exposing the current frame of a video as a keyframeable property be a great solve. 

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?

I am using Figma from almost 2 years. It’s a great tool. Previously I was using Windows 10 yet recently switched to Linux(Ubuntu). Figma doesn’t have any official release for Linux. There are some Unofficial desktop versions but they are “BUGGY”. I request you guys to release an official Figma desktop app for Linux.

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.