Suggest a Feature

As the title says.We work with branches and do not work inside the screens themselves as it's easy to lose what's part of the handover and what's not for both devs and designers. Therefore, we have a separate "Handover"-page where we display what's relevant for the specific task/ticket. To make this work more seamlessly with merging branches later, we turn some screens in components and copy the instances to this "Handover"-page. However, the annotations do not come along with it and requires us to annotate twice - on both the component and the instance.

Currently there’s no way to have different prototype settings (device mainly) within pages. I have to rely on creating different pages for desktop and mobile flows. Which is not efficient for large companies where you’re working on so many features.Would love to have a feature where your flows automatically adapts device setting based on frame size. So I could basically have desktop prototype and mobile prototype side by side. 

Hi! I would like to suggest a feature for creating and modifying graphs/charts natively on Figma.I design a lot of dashboards on a daily basis and unfortunately, each chart I encounter, I have to manually create and then use them as just placeholders (and sometimes the devs and stakeholders really need to see the real numbers on the designs, and it takes a lot of time to modify them).I would love it if there were a tool on Figma that allowed us to:Create (at least) pie, donut, line and bar charts; Export and import the chart data as .csv; Modify chart data and have it changed in the chart design; Apply styles and variants to the chart design; Enable chart legend.PowerPoint and Adobe Illustrator have this type of functionality, so it would make sense to have it on Figma too. 

The year is 2025 and we still don't have the option to organize our files ourselves... frustrating!A segmentation feature ("templates") was released (I believe, to meet this need) where it is possible to distinguish between icons, illustrations, shapes, colors. However, unfortunately, we were not given the autonomy to do this ourselves. In other words, this predefined segmentation of "icons, illustrations, shapes, colors" is only valid for public files that have been published in the community.I've seen some people reporting here how horrible it is to deal with files in Figma when you are an agency or when you are working in a team, but in fact this lack of autonomy when managing files is also felt by a solo user like me who likes to switch between different types of icons, illustrations, mockups, 3D images, style guides, design systems, etc., but cannot do this easily because the files are scattered throughout the interface with filters of questionable quality.Finally, my feature sugg

Annotations and Measurements - when attached to an item, option to hide when item hidden.

While in prototype mode, try dragging the screen or interactive elements in multiple directions—left, right, up, and down—to test how the interface responds to user gestures and transitions.

1. Variable/Library Connection in Prototyping Overlay BackgroundsWhile Figma Libraries and Variables are brilliant tools, I noticed a gap:Buried Access: Picking colors from the library for overlay backgrounds is buried under multiple clicks and is not intuitive.Static Colors: Even after picking a library color, it behaves statically (just a hex/opacity). This means if the library color changes, the prototype overlay doesn’t reflect that update.Suggestion:Provide an upfront, dynamic option to pick colors from the library directly in the prototype panel. If the library is updated, the overlay should also automatically update.
2. No Memory of Overlay Background ColorsFor multiple overlays in a prototype, I have to set the background color manually for each one. While Figma remembers certain settings like Smart Animate (e.g., it retains the last-used easing and duration, reducing repetitive effort), it does not do this for colors. The overlay background color always defaults to #000000 25%

I work in the design system team, and we’re constantly updating and publishing the Figma component library. This is great for users who already have design files: They can choose whether or not to accept our updates. BUT for designers starting work on a NEW file, they can only use the current version of the Figma library components. That may sound ideal, but it’s not. Here’s why: Often product engineering teams are some way behind the changes that we publish in the Design System team. They simply may not be able to implement those changes quickly, or possibly, at all. Their designers may want to work with previous versions of the Figma library in order to design TO THE PRODUCT. If they are forced to use the current library, this can cause confusion in the product teams, because devs and QA won’t be able to work to or check against those designs. Could the lovely Figma guys somehow allow designers to choose which version of a library they pull assets from?

This seems like a very large design oversight in Figma Slides. The help article says that “Published changes only apply to new slide decks that are made with the template.” Doesn’t this defeat the entire purpose of having a custom template where you can edit a style and have it apply to your entire presentation, instead of needing to manually tweak a header style on every slide? I expected this to work the same way instances update in Figma Design when you make a change to the main component, but even after publishing changes to a custom template in Figma Slides, my existing slide deck that pulls from that template isn’t updating colors & text styles. The published template changes would only apply to brand new slide decks, which means I’d have to define the template first and then create my slide deck. That completely goes against the general approach to how many of us create slide decks. For example, I don’t make the template before I start the slide deck. I make my slide deck fi

Hello,In the UI3 when you switch to light mode the topbar becomes transparent-grey, other than looking like a UI from 90s, it does not pass the contrast test! Contrast test results:​​​​​​​It used to be black like this (even in the UI3), and everyone was happy with it, please bring this back: 

 Mostly I like to use figma on browser (with fullscreen) just because it has more space, because there is no tabbar on browser. So, my suggestion is, there should be an option to hide topbar (or tabbar) on figma app, so users on smaller screen like macbook air will have more canvas view. Most people keep open a single tab, Why to waste entire screen width with tabbar?.Something like “Dock” on mac os. You can hide it, but when mouse hovers on that area it will be shown.  

I lead a team of designers and when i log into our project I want to sort by most recently edited; i want to see all the stuff thats been/being worked on since the last time i looked. This must be a common use case. What am I missing?

Currently, if you copy + paste a figjam flow into a Design file, the Connector Lines stay fully functional – they stretch and adapt as you move their origins and destinations around the canvas, and you can move their origins and destinations to your frames, components, etc. I’ve been using this to show user flows within my UI designs, not only for ease of sharing with other teammates (no need to give in-depth walkthroughs), but also for easily identifying missing states within a flow. It would be great if a) the Connector Line was added as a tool to Figma Design, or b) basic lines and pen vectors had the option to act as connector lines – attaching to anchor points on objects and components, scaling when the endpoints were moved, and able to be adjusted with mid-line handles.

It would be really handy to be able to set your own defoult settings for adding new section. I always use specific background color and corner radius and I need to change that each time I am creating new section it is really abundant work...

Hi Figma team,I’d like to suggest a feature that would be really helpful in collaborative workflows: the ability to copy and paste comments between different files.Currently, comments are a great way to communicate within a file, but when we need to reuse or migrate comments such as when duplicating parts of a project into another file we have to recreate them manually. It would be very useful to be able to copy a comment from one file and paste it into another, preserving its content, author, and ideally its relative position.This small improvement could save a lot of time and make collaboration even smoother.Thanks for the great work on the platform!

Just like how GitHub has the “Forking” feature where, we make our own personal copy of a public file so to edit it freely, without effecting the original. This way alot of other people can contribute to the file and help in improving it, adding new features or fixing problemsIt would be great to have such “Remix” ability to the community files so a bunch of people together can contribute in keeping files up-to-date. For examples, community files for Shadcn UI are outdated, they have not been updated for 2 years due to sheer amount of work. With remix, anybody can help in updating these files without the need of a primary dependency.Thanks.

Please update the feature for printing purpose. Because If I want to print magazines , brouchers at all and   and multiple pages option also. I go for adobe only. Please include this feature to coming up more users into figma .I hope you update this feature as soon as possible. 

Hi Figma team,I’d love to suggest a feature that could bring mobile prototyping to a whole new level: support for haptic feedback in prototypes tested on mobile devices (especially via the Figma mobile app).Today, Figma already allows us to prototype with beautiful transitions and rich interactions. But being able to trigger haptic feedback (via the Taptic Engine on iOS, or vibration on Android) during key interactions (tap, success, error, screen transition, etc.) would let us:Simulate real product experiences more accurately Design more emotionally engaging and trustworthy interactions Test and iterate on sensory feedback during user testing Elevate the quality of motion & micro-interaction design directly within FigmaIt would be amazing to have:Native support for defining haptic patterns (e.g. soft tap, success pulse, warning alert) per interaction Compatibility with existing mobile preview features Potential integration with Core Haptics or custom presetsLetting designers proto

Current behaviour (in Org): 1- after sharing a link to anything in a file (page, frame, section, etc) the url uses those names 2- if the name of any of those names included in the url changes, then the url, which has been included in documentation and dev tickets, breaks. Expected behaviour: use unique identifiers instead, so the url already shared do not break due to file renaming due, file clean up, etc Anecdote: 1- an entire set of sprint tickets (50+) had to be painfully relinked due to file name, frame and section renaming that happened after the PM grabbed the urls. 2- after a feature has grown (or low memory warning), and there’s a need to split the file into multiple files in another project folder, the frames are cut and pasted into another file. Once again, simple file management breaks urls already shared and an entire project needs to be relinked.

I often find myself trying to use the font weight shortcuts to change the weight of a line. Would be a helpful shortcut when you have a line selected. Possibly also when you have an object selected, it could edit the stroke width on that object. cmd - alt - < cmd - alt - >

It should be possible to swap library components manually. In this screenshot, I’m swapping a icon library for another, but the icons are not named the same, so I can’t finish the job. Why can’t I simply select the component I want to replace it with? Even worse, there’s no way to select the components from the old library to swap them them manually one by one. Component instances from my old library are scattered in pages and there’s no efficient way to select instances from a certain library (apart from the swap library modal). I’ve looked at so many plugins and none of them can get it done. It’s such a pain and could be resolved easily. btw - the same applies to “Missing Library.” Because I can’t swap them to an arbitrary library, I’m left with ghost components that I can’t even locate.

This is a feature comment specifically for Slides, but I believe it applies to Figma and FigJam too. When I send a Slides presentation to a client, there is no way to hide my presenter notes or all the comments from me and my team. So before sending I have to be sure to delete all my presenter notes and comments which are only meant to be seen internally.I would love to not have to do this so I can keep internal comments and presenter notes for reference. Would be great if when sharing externally I can choose to hide comments and speaker notes so they can’t see them.

What about having a feature where one user can share his/her selections to other team member who's working in the same file? 

Doing UI/UX for 23 years, since 2000. Hi everybody. The major issue of editing components right now, is the fact that ussually you have to go to the isolated component library and edit it there. And while you are doing that, you are completely disconnected from the rest of the design. I would like to see the future, for editing instance of component on the spot, and immediately see the result. After edit is done, there should be the “Publish changes…” button. Universe bless the Figma.