Suggest a Feature

Add it as a toggle here, so you don’t need to go trough the Assets panel and right click on the component. 

Is there a way to set default settings to newly created projects? Most of the time I use Figma to create desktop webdesigns, so I’d like to have my prototype to have a custom size device (1920x1080) and a different background color. And perhaps have a predefined grid.

This functionality exists in Photoshop and it's pretty useful, especially for those of us that use a tablet and pen instead of a mouse on a daily basis.Having to do the keyboard shortcut to zoom in and out gets repetitive very quickly. Simply holding the “Z” and left click up/down or right/left to zoom would be huge

Hi, Shortcuts are great but not enough. I’d like to share an idea for improving the editing experience in Figma.This concept is inspired by Windows Explorer. When you press Alt + Space, a context menu appears, and some shortcuts are underlined for quick access: A similar approach could be implemented in Figma. For instance, pressing Alt (or Option on Mac) could underline available shortcuts, like this: This would provide a more intuitive navigation experience and reduce the learning curve for users.Looking forward to hearing your thoughts!Best regards,

Steps to reproduce Click to add an “Open overlay” interaction. Two options will be shown: Close when clicking outside Add background behind overlay (see screenshot in the end) Existing functionality: “Add background” only has the option to add a color. Desired functionality: “Add background” also allows to add a blur effect to the layer on the background. Possible workaround Suppose Frame1 contains the overlay content Put Frame1 inside Frame0 Resize Frame0 to take the full size of the screen Make it so that “Open overlay” targets Frame0 instead of Frame1 Manually position Frame1 (the overlay content) inside Frame0 (the overlay) Add the desired background color and blur to Frame0 Problems with workaround The “Close when clicking outside” functionality is lost since Frame0 takes up the whole screen. Manually adding an on-click “Close overlay” interaction to Frame0 would not work as intended. This is because the entire Frame0 would respond to the click, not just the part

It would be great to have a way to store a ‘File’ or link to a file directly in the file system. This way, when organizing projects you can place a  Figma ‘File’ into a folder that would link directly link to a Figma project. This would enable ‘storing’ files in a standard workflow. This way, we say “You will find all project files in the project folder” 

Our team would like a feature where we can add a title to the layers panel without that title being an actual page a designer can click into. Is there a feature that exists like this already? In the screenshot I’ve attached you see where “components” page is? We don’t want that to be a page but rather just a title that a person cannot click into. Please let me know if more clarification is needed.

Just as there were requests for horizontal scrollability of the left menu, and the somewhat expandable right pane of tools. I need the libraries pane that appears while applying colors and such to be expandable or horizontally scrollable - or at the very least, hovering shows me the full name, like in the main tool pane to it’s right.In my use case, I’m creating a design system, and the naming conventions of those can become relatively long and the most specific detail in the name is at the end (e.g., hover, focus, default, etc)(Unless someone knows a way to see this)An image showing the problem:  

Current music is repeating. I get boring after listening in 30 minutes and open some lo-fi hip hop stream. Really want to use FigJam music. Please, add more tracks or direct audio stream from SOME lo-fi music stream. Sincerely, Mikhail.

From what I understand, currently there is no way to programmatically update the widget to the latest version when users interact with the widget. Users do not know that there is a new version, and the current version they use is old. They can manually right click each widget and see if under Widgets menu, there is Update to latest version option.It would be great to have updateToLatestVersion() or checkIfLatestVersion() so, the widget can prompt them to update.

why is there not a link to access open support tickets so that you can see when theres a response instead of having to check your email? its extremely frustrating having to comb through emails looking for responses from support, i feel like it would make things a lot easier and quicker if there was a way to view support tickets through our accounts [like in a chat/inbox] instead of through email. the ai chat feature will let you submit support tickets but once you submit it and close out of the chat its GONE. when you go back to reopen the chat window it just resets to the initial ai response, but if you chat with ai and close the window and go to reopen it the chat is still active. i feel like it also do that when contacting support, otherwise why even offer to contact support through the chat feature? 

This is MUCH needed. Our libraries contain already established typography and color styles that we use throughout our product and branding. Being able to link these styles with Slides presentations would GREATLY help our marketing and sales presentations look polished. The sales and marketing teams could focus more on the content and the branding and design teams can spend less time we styling everything once the presentation is done. Yes, components in libraries are not necessarily helpful here, but color/type styles/variables are critical.

This is probably more of a fringe scenario, but it would be nice to be able to change the day on which a recurring Figma subscription is processed.Our Accounts Payable team requires all expenses up to the 20th of each month be included with monthly credit card reconciliation, due for submission on the 26th. Our Figma subscription is processed on the 20th, but it often doesn't post to our expense management system until the 25th or 26th. If we could change this to process earlier in the month, we'd have more flexibility over submitting our report each month—without needing to hover over our expense management system on the 25th and 26th to see if the charge posted. According to the Support team, we purchased an annual subscription on the 20th of the month. From the date the plan is purchased, any seats used outside of what the annual plan covers are charged on the 20th of each month.I recognize this isn’t a Figma problem, but being able to change this billing date would help us manage t

I would love to be able to toggle on the ability to show hidden elements in the side bar when fusing ‘Find’ and ‘Find & replace.’It would be especially useful when trying to do file tidy up.Thanks!

Name speaks for itself, whenever I switch from “custom” to “libraries” when choosing colours I would love the search to be immediately active as I have hundreds of variables to choose from. I constantly start typing immediately and end up going to different tools that I did not intend to. Is that too much to ask? Secondly, why is custom the first option? Don’t we all use libraries more?

When you create a new file, it is automatically assigned a background color to the canvas depending on the selected theme. This ensures that you have the right background color for the selected theme. However, if you use “Theme = System Theme” as I do, the color of the graphical user interface will change but not that of the canvas. Therefor it would be nice to have the option to change background color of the canvas automatically depending on current theme

In design mode, components bubble up properties from inner sub-components. This makes components much easier to interact with.  In dev mode, the behavior is different. You only see the currently-selected component’s properties, and have to drill in to any sub-components to see their properties.  It would be really nice to have the same behavior for both (bubbling up properties) so developers could see all the properties set on the parent on down to any smaller atoms. 

I have a template design file I use as starting point for many designs. Let me copy the template design and paste it into the folder were I’ll be keeping the new design. Right now the workflow onerous. “Duplicate” the file then “Move file…” using the popup that does not let users browse folders.

When i hit CTRL-I the component window pops up as usual but sadly, after the last updates it is bloated with stuff that i don’t need nor want. When i lock in the option “Local assets only” it resets this option everytime i hit CTRL-I again. Generally speaking, the idea of integrating external libraries is not the best idea in my opinion It bloats the once so intuitiv and fluid application and makes it just slow. No real corporation will use these proprietary libraries nonetheless. But that’s just my 2 Cents here, still a nice product and no alternative in sight.

In light of all the recent issues with Material Theme Builder, I’m just now realizing that Figma Partner plugins do not have commenting available/turned on in Figma Community files. If I had known of the issues others were having with this particular plugin, it may have given me pause prior to incorporating it into my file. For the benefit and awareness of Figma users, commenting should be turned on for all plugin resources within the community.

What if we had Background Blur effect feature in Prototype Interaction Popup Which would like this: I needed background blur behind the popup dialog, and it seems like I can’t do it. Tell me this can be done differently beside pointing whole one screen to another. #Original

Same as Title. Stop change components width properties to [fill] when adapting Auto-layout on Variant Sets very first time. It’s very annoying work to check everytime i adapt Auto-layout on Variant Sets that i designed typical width size for a Variants. This issue makes me spend more time to double check the properties. Small detail can make users happy.

[> Please search for existing topics before posting! Press 🔍 at the upper right to search.] Hi there! I’m wondering if there’s a reason why the only option for a TV device frame is 1280x720 when the standard for TV app design is 1920x1080 (at least for Apple’s tvOS). 📺 I found that this question was discussed here in 2022, but the thread has closed and 1280 remains the only TV device frame size. I created an entire prototype (screen recording linked below) at 1280 because I wanted to present it to the client within the slick-looking TV device frame, but now our dev team has to scale everything up 1.5x. For the most part this isn’t a big problem; it just creates one extra step in the workflow that shouldn’t really be necessary. So does anyone know why Figma’s only TV device frame option is 1280? Is there some reason why TV apps should be designed at this size rather than 1920? Thanks! drive.google.com

Trust me I’ve searched for a plugin that does what I want to do - I simply cannot find one Which leads me to ask **Would it be possible to add a section / feature in the “Design” side menu similar to the “Selection Colors” section that pops up when selecting multiple frames or elements on a given page?.. ** Why? As of right now, we’re in the process of determining text style equivalencies for our web app that would need to use different text sizes as breakpoints increase. In the early process of creating our design system for this new project, it would be great to see, at a glance, all the text styles currently in use for one breakpoint to see if there are consolidations we can do prior to exploring the text style scaling or equivalencies for larger UI.

“Driven” variables for advanced prototyping Currently, when you link a variable to a UI property or component property (like the width of a frame), updating the variable in the variable panel automatically changes the property. In this setup, the variable controls the property. But what if the user could opt to reverse this relationship? Instead of the variable controlling the property, the property controls the variable. To enable this, we could introduce the concept of “driven” variables. A “driven” variable would update its value whenever the linked property changes. For example, if the width of a frame is linked to a driven variable, resizing the frame both editing AND prototyping mode would update the variable with the new width. Use Cases: Resizable objects in Prototyping Mode: With driven variables, properties like the width of a frame could become user-adjustable in prototypes, and the new size would automatically update the variable. Custom Breakpoints in Prototyping mode: