Suggest a Feature

Some quick context: I recently created a basic Figma slides template. After using the template & theme to create an actual presentation, I identified some new slides that I would like to include into the original template. When copy pasting the slides that used the template into the original template file, it created a duplicate template with the same name for the slides that were pasted in, even though they used the original theme of the template. The main issue I have here is that when swapping the template to the original, it randomly shuffles the colors. So I have to adjust the entire slide. I feel like updating templates over time based on real usage is pretty common, and the current behavior makes it rather awkward. Thanks!

I want to pay for the design of the Figma Make AI, but I don't want to pay for the subscription, as I'm not a web designer and I don't think I'll be using Figma for any other projects anytime soon.That's why I need to know if it's possible to pay only for the finished product and not the monthly/annual fee.Thanks in advance,

I'm using a chat agent to prototype my designs. But currently in Figma mobile app, it only allow me to view and comment on my canvas. I cannot select the frame and share the frame link to my chat agent as a reference for vibe coding. The workaround of request desktop app from Browser crashes all the time. Please enable the feature to be compatible with the recent AI trends.

Why figma do not copy comments with page or element. when i copy some object that have client comment or feedback.

 it’s been months since this issue above was reported and asked, and i saw a solution here  however it’s too tedious and it’s not even responsive. i also have to create it on each page. When would devs add overlay feature on figma sites? overlay is such a basic animation on all sites. i only have free tier for school is the overlay feature locked behind a paywall?

Switching to the Enterprise license and would like the ability to assign a user to multiple workspaces. I see there is an option for folks to be invited to teams in different workspaces, but it would be more efficient if we can easily add and see how many workspaces folks are assigned to. In our organization we do a lot of cross collaboration, across the workspaces.

Currently, in Figma Make, the code versioning shows only the line counts added or removed (+/-), butdoes not allow viewing the actual lines of code that changed between versions. To review codechanges, developers have to restore old versions, which risks losing progress.Feature Request:- Add a “diff view” for code files, showing added/removed/changed lines similar to GitHub or VSCode.- Keep the diff view read-only so restoring is optional.- Optional: support side-by-side diff view for easier review.Benefit:This would make code reviews in Figma Make safer and faster, reducing the need to restore oldversions and potentially lose work.

Figma Team, Data Scientists like me are praying for you guys to develop a data visualization node! you’re missing so much by not providing so. Power BI, Tableau and the other softwares are so square in design and usability terms. I’ve been copy pasting my charts into Figma for the past month and you guys are definitely a level up if we talk about presentation.

As a grad student a data visualization tool is so needed! I love using Figma for all things deliverable-wise but I desperately need a better data viz interface to create meaningful artifacts. I’m currently pixel pushing my way through building my own graphs and bar charts. Figma, please help your beloved grad students!! <3

Currently auto layout arranges layers from bottom up, i.e. the lower most layer in the layers list appears on top of every other layer on the workspace. This creates two problems 1. Confusion There’s a clear confusion of the order of layers shown in the layers menu and the representation in the workspace. This requires a bit of getting used to 2. Effects like drop shadow don’t work like they are expected to Applying a drop shadow to layer 1 does not cast the shadow on layer 2 And applying a drop shadow to layer 2 casts a shadow over the top layer 1 The Order in the layer menu should be reversed. Does anybody else see merit in this? Update: The same logic applies to horizontal auto-layouts. The right most element is on top whereas the left most element should be on top majorly because we scan left to right hence the element on the lleft most extremity is to be scanned first. for example: Say we require a stack of layers to be shown which shuffles on drag It would make more sense to

Hello Figma Community 👋I wanted to raise a question regarding the monthly AI credit system and also share a suggestion that could benefit many users.Currently, on the Professional plan, we receive 3,000 AI credits per month, and as confirmed by support, unused credits reset at the end of each billing cycle and do not roll over.However, in real-world usage, credit consumption is not always consistent every month. Some months require heavy usage, while others involve lighter workloads depending on project timelines.📌 Example Scenario:Month 1: Allocated credits: 3000 Used credits: 1800 Unused credits: 1200 (expired) Month 2: Project demand increases Required credits: 4200 Available credits: 3000 only Result: Need to purchase extra credits, even though unused credits expired in the previous month.This makes planning usage difficult, especially for freelancers, small teams, and agencies where workloads vary.

In massive organisations with tons of projects and documents, we are trying to figure a way to tag them in order to facilitate our job when searching for anything.. The implementation of a tag system would be quite welcome. Here is a sample image of what I mean below :  

A very common way for me to share motion prototypes in an accessible way across my org is dropping it into a deck in Google Slides. I’ve found the best way to do this is to create a prototype (device: none), screen record that prototype using QuickTime, and then convert the .mov to a .gif using GIF Brewery 3. This process works pretty well. The primary downside is that the only way to get a touch cursor in the prototype is to set the device to a mobile device, which then includes the device chrome. This is not ideal for screen recording and creating a .gif as it increases the file and image size. A simple way of solving this would be to include cursor settings in top-level prototype settings that includes a choice of either a touch cursor or a pointer cursor (this is similar to how Principle does it: View->Toggle Preview Cursor Type). While this would solve for my specific use case, I also think it allows people to create more robust prototypes for touch devices that excludes device

The main source of inspiration for this idea was to match the keyboard shortcuts themselves to different keyboard layouts. Right now, users who don’t use US keyboards have to memorize the location of the keys, rather than to use the actual character location to be able to use the shortcuts. Those involving this region are primarily the case: ABNT2 layout (Brazil). And here’s an example of confusing shortcuts: Although this problem could be solved by just rebinding the shortcuts to the actual character and not the location on the keyboard, I’ve noticed there are some other issues concerning key bindings. On this forum post, a member of the community asked for help on backing one layer level with a different shortcut from what Figma has right now. This makes the user adapt their workflow to the tool, and not the other way around — and that hinders efficiency. It would be nice if the tool itself provided some sort of customization on this regard. Although being a workaround, Mac users c

Hey @figma you know what would be dope? Having the image field as a component property allowing us to just replace the image without having to go into the layers…even better if it would save the fit or fill setting

Figma currently offers a keyboard shortcut to hide the layers panel (CMD + SHIFT + \ ) or all UI (CMD + \ ) but no keyboard support to just hide the right panel (Design, Prototype, Inspect) For me the layers panel can often be more important to retain than the right panel. Anyone else want this feature?

Feature Suggestion: Per-Account Color Customization in WindowsProblem  Users who work with multiple accounts simultaneously (e.g., different profiles, tenants, or environments) often struggle to visually distinguish between them. This increases the risk of performing actions in the wrong account.Proposed Solution  Introduce a feature that allows users to assign a unique color theme to each account. The selected color would be consistently applied across key UI elements such as:- Window title bars  - Accent color highlights  - Taskbar indicators  - App frames or borders  Key Benefits  - Reduces user errors when switching between accounts  - Improves visual clarity and context awareness  - Enhances productivity for users managing multiple environments  - Provides a simple, intuitive way to differentiate sessions  Example Use Cases  - Personal vs. work account  - Production vs. staging environment  - Multiple client accounts  Optional Enhancements  - Automatic color assignment per account

Love the new Typography Variable release, but it falls short for our use case. Our goal is to use variable modes to switch styles between our 3 brands. 2 of those brands use all caps for headings, the other brand uses sentence case. We need to be able to bind a variable to the case of a character style (As typed, Uppercase, Lowercase, Title case, Small caps). Without this capability, when switching modes from brand 1 to brand 2 for example, we are getting the default case for the character style (sentence case coming from brand 1). We would then have to go through our designs and manually type in all caps for all instances of headings in brands 2 and 3. Certainly not ideal and will lead to inconsistencies / places where manually typing in all caps are missed if we went this route. Until binding a variable to the case of a character style is an option, using typography variables isn’t feasible for our use case.

We definitely need these, until every Styling option that can be applied to text in Figma is added to the great new variables options, it’s not usable as a complete UI system. Text decoration values like underline, slashed, uppercase, are all vital parts of out text style system. Would love to see these be added along with REM/EM support or at the very least percentage support for Line Height & Letter Spacing.

When working on complex prototypes, I often reuse interactions (e.g. animation curves) across screens or steps. In order to do this, I have to manually rebuild them each time. This requires a lot of work - selecting the interaction where I used my custom curves last time, open the interaction panel, copy the custom curves, go to the new interaction I want to apply the same curves to, open the interaction panel, select “custom”, and paste. It would be great if a) I could copy & paste interactions or b) I could leverage an “Interaction Design System” and apply custom values in the same way I can apply custom colors, typography styles, etc. Has anyone else found an easier way to do this that I’m missing or is there a plugin to manage this? 🙌🏼

Problem:When admin remove person from organization, drafts of this person move to Unassigned drafts.Idea:It would be very helpful to have notification  about unassigned draft, with Move function, so Admin can check drafts in the process of removing user from organization. In admin panel tab show and filter by name of Admin who removed member from organization. Current situation is that unassigned drafts (with deleted accounts) shows in Admin panel tab with lack of informations (only name, mail, date of deletion, number of files). Admins can't see workspace or teams to connect drafts with projects/ topics).Only possible way is manual investigation of deleted memebers and set workaround workflow during member management.I looked at the learn page about unassigned drafts before: https://help.figma.com/hc/en-us/articles/4420549259799-Manage-drafts-of-removed-users 

Recently a new member of our team (who was granted edit privileges) deleted our component library file, which led to a series of issues until I, the admin, realized what had happened and restored the file from trash. However, there was a chance that I never would have realized what happened, or that the user could have gone into the trash and permanently deleted that file, both of which are horrifying outcomes when it means re-creating the design system and all documentation from scratch and then replacing component instances across dozens of files with the new one. It would be FANTASTIC if I, as the admin, could prevent editors from deleting certain files, whether that’s on a per-file basis or with an across-the-board rule like “you can only delete files that belong to you” or “you can’t delete files in this project.” Such an option on all the paid plans and up would definitely help me sleep better at night!

Currently, Figma Slides on the mobile app only allows users to view and run slides. However, when giving a presentation, many of us connect our computer to a projector to display the slides while wanting to use our phone as a companion device to view presenter notes. It would be extremely helpful if the Figma mobile app could sync in real time with the slides being presented on desktop, so that the presenter can:  See their notes directly on the mobile app Follow along with the current slide in sync with the presentation Use the phone as a discreet presenter tool, without needing a second screen or printed notes  This would bring Figma Slides closer to the functionality of other professional presentation tools and make it much more practical for real-world use. I hope the Figma team will consider adding this feature, as it would significantly improve the experience for presenters using Figma Slides in professional settings.

Figma MCP should provide frame-to-image exporting as a tool. That way AI could export graphics in a page design as `.svg`s, `.png`s, etc... and upload them to our cloud bucket,or put them in our web assets folder.

The default settings (at least in my Figma) load a percentage for letter-spacing, but this is not allowed in CSS. For a less avid programmer this may be confusing, when trying to get it to work. Either set the default to a px value, or add a warning inside the Inspect code