Suggest a Feature

Hi, I've been working on a prototype, and animating the chat bubbles turned out to be quite a tedious task. To create the animation, I had to duplicate multiple frames and apply individual delay animations to each chat bubble.I'm wondering, is there a way to apply a delay animation to a group of elements collectively and adjust the timing for each, similar to how you'd stagger animations when loading a collection of cards?With Figma's current capabilities, the only workaround seems to be creating multiple frames and manually adjusting the opacity and timing for each element to simulate delayed appearance which becomes repetitive and time-consuming when applied across multiple components.Would love to know if there’s a more efficient approach or if this is something the team is planning to improve in the future.

I've been really enjoying the new Motion features in Figma. The experience feels intuitive, and creating animations has become much faster and more enjoyable. Even in its current state, Motion shows a lot of potential, and I'm excited to see how it evolves.While testing, I came across a few areas that could significantly improve the workflow: Nested Layers in the Timeline When working with nested layers, child layers currently appear individually in the timeline alongside their parent layer. This can make the timeline cluttered and difficult to manage. It would be helpful if the timeline supported nesting similar to the Layers panel, with expandable and collapsible groups. Dedicated Clipping Mask Workflow Motion currently lacks dedicated clipping mask support. A masking workflow similar to After Effects would make it much easier to create and animate reveals, transitions, and other advanced motion effects without relying on workarounds. Dedicated Alignment Controls Motion currently

why can’t figma make make components that we can import back into figma. It would be useful to us make to generate a design system, using prompting and be able to import thes eback into figma as components.

Hey! How can I transfer the AI generated Prototype in Figma Make to Figma Design and continue editing it manually there?

I don’t use Figma all the time, I don’t want it to run anything on startup. It’s frustrating to manually remove Figma from Login Items, since it automatically adds itself there again. It would be nice to have at least an option to disable it in settings, or even better - remove that functionality at all, since it’s not user friendly. I want control over what and when the apps do at my workstation. P.S. If it’s needed for updates check - I’m more than okay to update on app start

I strongly request the ability to turn off the Figma agent appearing by default when a new Design draft or file is created, and also to disable the Agent tab completely. In addition, the ability to hide AI options like “Make an image” for image design tools would be nice, as well as the ability to filter tools/plugins by their use of AI in the Tools tab and Community.This could be as simple as adding new toggleable options under Figma > Preferences… labeled something like “Show Agent in new files”, “Hide image generation tools”, and labels for Community assets that use AI and options to hide such assets in their respective categories.I know that these options don’t exist right now, which is why I am imploring them to be implemented as soon as reasonably possible. I understand these things can be helpful for a good amount of people and that’s completely their choice. But you need to understand that a similar amount of people, myself included, have no interest in using the agent or an

Im creating a prototype and would like to link to live pages on our site without having the User in the test have to see the “Leaving Figma Warning” page. My concern is that it takes it breaks the illusion of an actual experience. Is there a way remove this middle page from the experience?

The seats section lacks of a registry to know all seat changes history. The only information it shows is the seats taken right now. It’d be great to know since when some seats have full access o collab, is almost useful as it is now if you have to set up a budget or making a billing from it.

I would love to be able to see all my brand’s patterns in the preview of the style panel. Right now they all sport the same generic dotted pattern.I am able to add a “background” colour behind the pattern, but many of my patterns use the same colours in different combinations, so it isn’t a reliable way to distinguish between patterns.  

Connected Projects are a great way to have a shared space between two separate Figma accounts (usually between two organizations). A drawback is that all the files are in a single project.Without some kind of hierarchy (or filtered view) the Connected Project can quickly fill up with all kinds of working files, templates, older “archive” projects that are now needed only for reference, etc.Figma could either extend the “connected” concept to the team level (so there can be more “folders” in the connected space), or provide some other kind of other hierarchical or filtered view.

Can we allow Connected folder to have a sub-folder? Perhaps not 10 levels of nested folder. We can limit it to 1 or 2 levels should be good enough.Thanks!

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.

It would be really nice if I could pop out the variables into their own window. Currently I can only have it as a dialogue in Figma, which means it always overlaps over my design and especially on smaller screens this becomes quite the issue. I often need to see variables and my design at the same time, so moving it to a second monitor (or even on a laptop quickly switching with alt + tab between the two) would be very helpful.

We have a design system set up with tokens (variables) to enable all components to switch between light and dark mode. For developers/viewers to see what a screen should look like in Dark mode, we have to duplicate that screen. But as an editor I can set the colour mode variable at the Page level to Dark and all screens on the canvas/page turn to dark mode. If developers/viewers could also do this, I could delete the dark mode duplicates of every screen and only have one copy of each screen, defaulted to light mode, and then just toggle dark mode as needed. This would be much more efficient on memory usage and maintenance.

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

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. 

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, …