Suggest a Feature

In the case of multi-designers, multi-projects and multi-documents, it is really tiring to manage and classify files. I hope to have file management with tree structure like confluence!!! 🥶

Hello, Is it just me or is it challenging to prototype w/ Variable Modes vs. Variables? I kind of think of it like managing states in Canvas vs. Prototyping. In canvas, toggling modes is great, but with prototypes, mode toggles become almost useless unless you’re doing a broade based switch. Then ultimately what’s happening for me right now is that I’m creating both mode differences and single variables so I can prototype with precision but also handle manual changes in Canvas. One example would be setting up a profile card that is disabled, but based on another component selection becomes active. In canvas, you manually make adjustments and point arrows for what happens conditionally. But if you try to move that logic into an active clickable prototype you either lose precision or break your project entirely. Right now the only solution is to create individual variables and maybe multiple collections… But of course this creates confusion all around. There’s a gap in the logic b/w pro

Any way to restrict fonts shown to users by default? Would like to see only assets we’ve allowed to simplify choices for designers. Additionally, fonts (like Noto Sans) are brutal to work with. Only want to support variants that are used within the design system.

All files open in dev mode = not a fan. How can I turn this off? It isn’t a great user experience to have to do this manually every day for every file. Can the regular, non-dev mode, be the initial load standard? When you have 20 files you’re in daily this just isn’t the best.

An annoyance I deal with on a daily basis is having to change what feels like nearly every single prototype interaction, because Figma has chosen something else for me. In practically every interaction, I use the Spring - Slow timing, but unless I’ve just literally just created an interaction and made a second one, Figma chooses ‘Ease out’'. Also, when I do switch it from easing to spring, Figma always changes my duration to 600ms. This is incredibly frustrating, as I’ve already set the duration I want, but Figma messed up the easing, so now I have to also revert its duration decision. I’d love to get a statistic on how many extra clicks this has cost me over my years of using this software. Figma should use the most recent duration and timing functions chosen, and not change the duration when changing easing modes.

Currently, when video files are imported into Figma, we lose access to their original metadata, making it difficult to locate the file on the hard drive. Could we enable the option to view the link and metadata of imported videos to streamline the process of finding them later? For example, if I import an image and later delete it, I can export it back from Figma and retrieve the original file. However, this is not possible with videos.

I have a problem with a shadow that faces the Android engineer when applying the shadow styling “the shadow modifier is not compatible with this design in Figma” and the outcome shadow is not the same as the design Is there any solution or plugin to fix that?

Proposal: Locking Page Names to Prevent Accidental Changes Accidentally deleting or renaming a page is a common issue, especially in collaborative environments where multiple designers work on the same file. This becomes even more critical when dealing with essential files like a design system, where unintentional changes can cause confusion and disrupt workflows. I suggest introducing an option to lock a page name, preventing accidental edits. When locked, renaming would require an intentional action to unlock, similar to how locking layers works in Figma’s layer panel. Key benefits: Prevents errors by reducing accidental renaming or deletion of critical pages. Ensures consistency across the team by preventing accidental changes, allowing team members to reliably find and reference the correct pages without disruptions or confusion. Protects key files like design systems from unintended changes. This simple feature could save time, reduce frustration, and enhance collaborative effic

Please increase text contrast and add padding for the component description container. Even better remove the rounded container completely, as it reduces the width of the description text. → Especially for larger amounts of complex documentation, this currently really is quite bad readability.

Hi Figma Team, I have a suggestion to improve workflow efficiency. Introducing a system to sort developers and designers could be incredibly beneficial. For instance, when a section or frame is ready, designers could mark it as “Ready for Dev,” triggering a notification to developers to start work. This streamlined communication would save time and reduce confusion. Additionally, this sorting system could enable tailored features for each role, like automated checklists, role-specific notifications, and progress tracking. It would enhance collaboration and productivity across teams. Thank you for considering this idea—I believe it could add significant value to Figma! Also would love to here from you guys back in reply to this feedback. Best regards, Millind Sinha

Sticky (stop at top edge) is a great feature in prototyping, but is there a way when that element is no longer relevant to let it scroll? For example, you have share icons on the right-side panel, they come in handy as you scroll through an article to remain sticky, but towards the end of the article, there might be another block of content that doesn’t need those social media share icons and you want them to scroll up after a full-bleed section appears, is that possible? Thanks!

Hello, I just read the new pricing plan for 2025. Now we have: a full seat with dev, FigJam, design and slides, a dev seat with dev, FigJam and slides, a collab seat with FigJam and slides a view seat. To be honest I’m missing a design seat now, which only accesses design. This one could be cheaper than the full seat. Some designers don’t need dev access nor FigJam or especially not slides.

Hello We are currently exploring the possibility of adapting our plugin to “Dev Mode”. However, due to the inherent limitations of Dev Mode, certain features and commands available in the regular user interface would not be applicable. Our plugin currently utilizes a rich popup menu with various commands designed for user convenience. In Dev Mode, many of these commands would be irrelevant or redundant. To provide a streamlined and contextually relevant experience in Dev Mode, we would like to customize the plugin menu by removing or hiding specific commands. Could you please advise on whether it is possible to dynamically adjust the plugin menu (defined in the manifest.json file) based on the active mode (regular user mode or Dev Mode)? If so, could you provide guidance or documentation on how to achieve this?

Dear Figma, could you set the default text color to the darkest black available in the page or library? This would save us from having to change the text color every time we type. Thanks.

Figma should create a prototyping option called “Loop,” which generates an infinite loop. This feature would greatly assist in creating infinite loops in prototyping without the need to create components, thus reducing time.

Figma Slides reduce my powerpoint frustrations tremendously, but they come with a few usability challenges. The slides have a general center-align and align-with-item snap to them, but getting better auto-layouts and more sophisticated templates would be a huge asset. Clear UI to create or save templates would be great, as well as live color changes to-template. If I change all of the colors in a template, having to go through my slides and reselect my template colors is redundant. Overall I would love to use Figma slides more than I am able to. A huge request is finding a strong integration between Figma Slides and Figma wireframes or Prototypes. Jumping straight from slide into prototype, or being able to have a natively stretched-to-fit wireframe in my presentation would immediately create adherence to Figma Slides over Google/Microsoft variants.

Hello, As far as I’m aware, we can only check/uncheck snap to pixel for the entire Figma document. This is not good practice for me as I like to keep it ‘on’ and keep everything flush to a whole number without silly decimal points such as 0.497. However, in some instance’s this is far from ideal too; for example, if I have an icon set and I’m trying to align icons vectors to the center point within their parent frame, sometimes this necessitates a decimal point, then I uncheck the option and forget, only later to realise my file now has decimals in odd places. So, perhaps a good idea is to create toggle on the right side panel next to the height and width boxes that controls (and indicates) snap to pixel for that component set. Moreover, would also be good rather than just to toggle ‘on’ or ‘off’, to add a third option: on, half, off; the half option allowing .5 increments. Would be handy.

Context I often work with files containing multiple pages, each of which I want to export individually. When exporting a page’s frames to a PDF, the default filename is based on the Figma file’s name, not the page’s name. While this can be changed, I find myself needing to do it every time. Proposal I recommend defaulting the export name to the page name, giving users more control over the PDF export process. Why This Makes Sense: You can’t export a PDF of the entire file, only individual pages within it. Each page serves a different purpose, and the file name is usually too general to be useful as a PDF name. Users can name each page with a file-like format, allowing for quick, easy, and consistent PDF exports.

As a user, it would be nice to be able to sort layers alphabetically or numerically. In addition, being able to also solo layers would be very helpful.

As an Admin in the Figma pro plan, I’d like to be notified on Slack immediately when someone in my team requests an upgrade to the editor in Figma or FigJam. Figma’s native notifications and email notifications often get missed, and these requests are often time-sensitive. Currently, only File-level comments & mentions show up in my Slack notifications, ideally, all kinds of Notifications should be shown in Slack.

New feature request regarding inviting new people a Figma organization. Current way of working The Figma Admin adds a new person - usually a guest - to our Figma organization using their email address. The guest accepts the invitation to the Figma organization Figma Admin assigns edit seats to the new guest - Figma and/or Dev Mode or FigJam The guest can finally edit their work files In this journey, there is an unnecessary delay due to the fact that the Figma Admin has to intervene twice. This delay represents a lot of time at the end - we’re talking about several dozen guest additions per year. Ideal way of working The Figma Admin adds a person to our Figma organization and assigns editing rights by default from the People panel when it’s in Pending stage The guest accepts the invitation in the Figma organization and the seats pre-assigned to them are automatically activated The guest can edit their work files It would make life infinitely easier on the Figma Admin

Figma recently introduced new feature for underline, But there is one problem which I have noticed during work. What do you think about this?

Am i the only one experiencing autolayout random behavior? Now sometimes it automatically changes the height of some components to 1px, or the autolayout widht to fixed, not hug. It worked perfectly before the new UI Rollout. Figma Desktop App version 124.6.5

Can we just go back to the simple component we had before? The preview inside the new color pricker is so energy/calculation consuming for an opeation that is so small and quick and easy.

Please, for my sanity, increase the width of the line/area where we can increase/decrease the width of the Files/Assets pane. The distance from scrolling, to the draggable area, and to the ruler is about 3 pixels which requires a high level of mouse accuracy to access the 1px middle draggable area.