Share Your Thoughts

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.

Unsure if this would be considered a bug or feedback but it’s impossible to write words including the letter “n” within the text properties of components in Figma Buzz’s design mode tab in Asset view. The moment I type “n,” it immediately moves to the next frame instead of updating the text property or allowing me to continue typing. Editing the text directly in the canvas does not cause this issue, but it is frustrating to work around and troubleshoot for non-designer collaborators who are more comfortable using the properties panel instead of directly editing the text object.

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.

Please enable Figma motion to work for “Change To” interaction in components. I use it in specific sections that change on click / mouse enter interactions but can’t use it because of this obstacle.Example: 1st, 2nd, and 3rd variant has animations. When I proto click → change to variant 2, the animation does not load. However if I have it looped, it starts after the full loop time length finishes for some reason.It works when using “Navigate To”, so for now I have to fake it by creating multiple frames of the full page instead of it simply working within the specific section.

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.

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

1. Visual Clarity of Selection StateSelected state issue with suggested change. Issue: The current selected state for measurement annotations is barely visible (appearing as a faint, sub-pixel outline). Suggested Fix: Change the selection outline to blue when an annotation is selected, matching the existing visual behaviour of the ruler selection state.  2. Selection Persistence & Unintended ModificationsGIF showing selection issues.​​​​​ Issue: Clicking a new measurement annotation currently retains previous selections. This causes off-screen items to remain active, leading to accidental moves or deletions. Expected Behaviour: Single-clicking any measurement annotation should clear all previous selections by default. Multi-selection should only occur intentionally when holding Shift or Cmd / Ctrl while clicking. Similar thread found here (Closed):  

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!

I’d like to share feedback regarding the implementation of AI credit limits in Figmake. As a designer managing multiple complex projects, I believe credit restrictions would greatly undermine Figmake’s usefulness in real-world design and prototyping workflows.  1. Most AI usage is for fixing bad or incomplete output, not luxury use.  In practice, a large percentage of AI prompts in Figmake are iterative—used to correct layout issues, rebuild misinterpreted elements, or align behaviors with visual intent. Each refinement quickly consumes credits even though the output quality depends on that iteration. Penalizing iteration limits the model’s ability to produce accurate prototypes, especially when the AI output is imperfect through no fault of the user, making credit usage really unfair and frustrating.2. Predictability becomes impossible, discouraging adoption.  With a credit cap that no one knows how to predict and calculate ahead of time, I can’t plan how far my Figmake usage will tak

Hello. Since the latest UI3 updates, the native AI image generation and editing tool has suffered two major usability regressions that significantly slow down my workflow:Missing Prompt History: The "Recent prompts" history (the clock icon) is completely gone from the new floating toolbar. Every time I need to reuse or tweak a complex prompt on a new image, I am forced to retype everything from scratch. Missing Quick References (+): Before, while the image generation panel was open, I could simply click a "+" icon on any image or frame on the canvas to add it as a reference automatically. That option has been removed, and adding references now takes considerably more steps.Together, these changes make iterating on AI images much slower and more frustrating than before. Please restore the recent prompts history tab and the quick canvas reference tool as soon as possible. Thank you.

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. 

This thread is here for you to share your thoughts and suggestions about the Figma Forum.We’re proud of the work we’ve done so far, but we know there’s always room to make things even better.
Here’s some prompts that you can use:What are your thoughts on the forum makeover of January 2025? What do you like the most? What have you struggled with so far? / What are the top three areas that need improvement? What would you like to see us implement next?If you spot a bug or have any feedback, drop a reply here — we’ll do our best to respond and improve!

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…