Suggest a Feature

Hey!When opening Figma you always end up on the home screen, I switch between projects a lot.There is currently no easy way to search my projects (without a mouse). It is a bit weird and frustrating that such a simple feature does not exist here. Just the ability to press CTRL/⌘ + F to focus on the search bar on the top left corner is enough :) Or, better, make it a search dialog with a big autofill thumbnails, a bit like Spotlight. (I do think this whole screen needs a bit of a redesign to make it easier to find my projects, but that is another topic) That was my ted talk :)If anyone could add this I would be so grateful!!

It would be great to have an option to send a link to others where you are already following the sharer as soon as loading the link - happens all the time in meetings where there is friction that everyon needs to click on the sharer to follow, sometimes people don’t load correctly or are logged in twice etc.

I don’t know if theres already a function in Figma that does this (could not find), but it would be so cool to not only have the standard prototyping triggers such as click, hover, drag etc, but also keybindings. Pressing a specific key as for example ‘P’ to trigger a popup, or ‘Spacebar’ to go to what ever screen. This would allow such cool things in prototypes!!

Issue and context:I frequently use the regular “design mode” with minimized UI on to focus on the canvas while doing larger walkthroughs with stakeholders or refinements with dev-teams.I use the regular design mode since most of the more complex designs have workflows and annotations right on the canvas so the designed screens/states etc are part of a larger illustrated process.While doing these walkthroughs my viewers often loose track of the mouse pointer. Especially in while hoovering over complex designs with a lot of visual clutter. Suggestion:I would like to be able to change the mouse pointer to a laser pointer with a color of my choosing. Its important that this is available while in the regular design mode since the current “present mode” starts a prototype and hide the rest of the canvas thus hiding all the contextual work flow illustrations and annotations etc.

Some fonts have Korean names, but they appear in English.It would be easier to find them if the names stayed in their original language, no matter the UI setting.

These dang annotations keep showing up.If I turn them off in the view menu, and then come back to the tab later or reload it they’re visible again! Perhaps devs are turning them back on? But shouldn’t they be a personal view setting??? Please fix this!Sincerely,A designer who doesn’t want to see redlines covering my designs constantly

Just like  i can Show/Hide Comments .. I wanna be able to do the same thing with the new features Annotation & Measurement 

Of course it is easy enough to lock layers but I think that it would be helpful to be able to lock pages in a fashion similar to the layers. I often place root (master, main, og?) components on a separate page and it would be nice to be able to lock these pages to keep items from moving around without intention.

Hi all,  can we bring right click to duplicate files back to the project folder level - now I have to open files to duplicate it’s a bit tedious when i need to duplicate multiple and some of them are large and has slow loading time.

​​​​​​I use the Annotation feature to capture bugs in the staging environment and it’d be awesome if we could tag the annotation component freely on an image without needing to create a frame to anchor on to. Secondly, it’d be super useful if we could re-position the annotations. 

Hi y’all. Please make the icon for Ready for Dev visible even when zoomed far out. Multiple times, my PM has misunderstood what is/isn’t dev-ready, because the icon doesn’t appear beside the section name when you’re zoomed out. But… when you’re looking for something, you’re more likely to zoom out to find it. (See screenshot, in which one of the sections is actually marked as ready.) Thanks!

It can be frustrating when repeatedly iterating on a scenario with minor updates. Upon revisiting the workspace, I often struggle to identify the specific changes made in the newer version. When similar screens are placed sequentially, they may appear identical at first glance, requiring me to meticulously examine each component to detect modifications.To streamline this process, I am interested in a feature that would allow me to select two frames of the same type and compare the differences between them via an action button, highlighting the changes for easier review.

Hey,we are happily using FigJam for our Scrum retros for quite a while now.I thought about also using FigJam for Planning Poker, it would be super cool if there would be an widget or similar to it.Rough requirements about the functionality:User is able to drop planning poker widjet into a FigJam file User is able to add a topic/item/user story that can be voted on User is able to set an item to “to be voted on” All Users on the board are able to vote on the “to be voted on” item An simple text input would be sufficient, but using pre-configured decks (like Fibonacci sequence, t-shirt sizes, etc.) would be very helpful After all users have voted, the summary of the votes is displayed and item status is set to “vote completed” Using numbers: Average Using strings (like t-shirt sizes): Frequency of given vote options User is able to set an item in status “vote completed” to “finished” (to remove it from the topic/item list) Kind regards,Vlad

If you right-click on an object in FigJam and choose “Export selection…” the exported PNG or JPG image includes are large empty space around the object. Is this intentional? In my use so far it has been unwanted extra space that I need to trim with Figma or another app.

I use keyboard shortcuts (as I’m sure most “power users” do), so I don’t need the toolbar for anything. Now it’s just blocking valuable visible area. Please add an option to hide it. I know I’m not alone, because there’s already even a Chrome extension that does this. (How to Hide Figma Toolbar (Bottom) in the new UI3 - SaaS Design) Unfortunately that doesn’t help in the desktop app.

 Aannotation should have a dedicated panel, similar to the comments panel, where all annotations can be viewed and managed more easily.Some context about our team: we use annotations not only for design notes, but also to indicate where event tracking should be implemented. Currently, annotations are too subtle on the canvas, making it difficult for engineers to quickly locate them. This impacts communication and slows down development.

1. When I open a file in the community in the figma application, and then try to go back, the preserve scroll position does not work, and every time I need to scroll from the very beginning2. When I open a plugin in a file by clicking on opening a plugin through the community, the community tab automatically disappears from the tab panel at the top, the only way to go to this file in the community is to click on the community tab in the window of the plugin opened in the file, but then I go to the file again, and I can no longer return back to the list of what I am looking for

It bothers me going back & forth between my mac & my iPad when making figjam boards, mainly because the full desktop version has the ability to create & view projects, while the iPad version is restricted to recents, drafts, or stars, without organizing any boards in projects. Please add the ability to organize & view projects on the iPad as well, thanks!

 We have non-visual team members who are unable to fully participate in the process. Although an accessible navigable version has been released, it currently reads only “links” and does not allow adjustments to specify elements as buttons, for example.To ensure a fully accessible experience, our components should include a dedicated area in their original specifications for defining the correct accessibility roles and attributes. This allows screen readers to navigate the entire screen — not just elements anchored in the HTML.

My team designs complex, data-dense UIs—absolutely packed with text layers. It’s wild.We’re typically subject matter experts in our business area, but our job is to craft narratives that stakeholders can actually follow. To do that, we rely heavily on our PM partners to tell us how to label charts, buttons, lists—you name it—to help sell the concept.So why should viewers be able to edit text directly?Simple: efficiency. Instead of waiting on a PM or stakeholder to respond to a comment with the right copy—then having to copy/paste it into the right layer—just let the person with the right info update it themselves. Asynchronously. This would save us a ton of time during implementation and eliminate the endless back-and-forth over wording.Thanks

I love Figma and have enjoyed used it since the very beginning. It has come on leaps and bounds since since its early days. However, one pain point that continues to frustrate me is the decimal resizing issue, as detailed here almost exactly four years ago - https://spectrum.chat/figma/general/how-to-prevent-decimal-pixels~a6007961-7415-4c1e-9430-7e420491c446 Despite all the other fantastic enhancements in the platform, it is disappointing that this core issue is still present. Even in the latest Playground file (produced by your own team) outlining the latest ‘Copy & Paste’ advancements, you can see the problem firsthand, as per the screenshot below. FAO @Figma & @Figma_Support. Please can I ask that you look at this as a matter of priority. I am sure I am not the only one wasting crucial time, painfully and manually, checking and resizing everything back to integer values. Thank you.

I change my section background color to 10% black. The layer labels are barely visible requiring me to create my own labels so partners know what layers I’m referencing. Is there a way to set the default label color so it is visible? I would add a screenshot but you can’t see anything. Doh!Alternatively, is there a way for Figma to auto detect the background color and set the label text so it passes accessibility contrast ratios? Seems like an accessibility bug.

I would love to have a higher contrast theme for Figma’s UI. It has long been a minor annoyance to me that a tool I use to create accessible designs doesn’t itself meet minimum accessibility requirements. However I’m now at a point where it’s actively impeding my own workflows. I’m currently going over hand-off-ready designs to make sure they use variables in all their autolayouts. The distinction between pixel inputs that have variables assigned to them and those that don’t is unfortunately abysmal, making the work very strenuous when it doesn’t need to be. The little raised/sunken area and border around the value isn’t anywhere near WCAG contrast recommendations in either theme. There are plenty of other instances throughout the UI where I feel aesthetics have been prioritised over accessibility and that would benefit from an accessibility audit, but a higher contrast theme would be an excellent start.

Figma, please add connectors as a standard feature in Figma. I am willing to pay for it as a separate feature.  

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