Rolling out: Projects become folders 📂 ✨
Got a feature request or product idea? We're all ears!
Recently active
We’d love to hear what feature requests, ideas or improvements you have in mind for any of the Figma products you are using.Note: If you have feedback on an existing product or feature, head over to the category Share Your Feedback. Sharing product improvements and ideasOur teams look at ideas and feature requests across many different channels throughout the product cycle and it has truly helped make Figma a better product.With that said, we want to make sure we set some expectations for how feature requests, ideas and improvements will be handled in the forum.We cannot make any guarantees or promises that you’ll see your idea/feature request/improvement implemented into the product Our team will merge topics with the same/similar ideas to keep the forum organized Inactive topics that are 12 months or older may be closed or archived to help keep the community organized and healthy Voting on topicsAt the moment, it is not possible to vote on topics.This is a feature we are reviewin
Let us multi-select folders, to more easily re-organize after the new “Folder” implementation. Trying to sort all customers into “A” “B” “C” etc.. folders, and having to drag one-a-time is.. well.. not optimal. (this regards both click and drag + right-click and “move” option) While viewing “all folders” in list-view: Sorting gets refreshed everytime I move out and back in to “All folders”. From alphabetical to “Last modified”. Annoying. After moving x-amount of folders, it stops working. I need to go to “draft” and then back to “all folders” view and then “sort by alphabetical order” to start sorting them again. (bug?) First thoughts and experience with the new feature. Really glad to see folders introduced to Figma( finally! :) )
I would love the ability to set a background color in the layer list. I’d like to be able to set this on an individual layer or group of layers. I often have trouble finding important groups of layers. I’ve resorted to using emojis which helps. But imagine that we could color the background color of the label. I’d also like to edit the label name so that in my document “Blue” would represent to my developers that it’s grids.
Add the ability to add text-wrap: pretty and text-wrap: balance so that more options are available to ensure more flexibility to how text can flow/reflow and reducing hyphenations and word orphans.
With "Text-wrap: balance" headlines could be made more readable and visually appealing.Here’s how it could look:
When marking a comment as resolved, we are now automatically moved to the next one. I’m wondering if or how we can disable this behaviour?My work flow being to go from screen to screen of user flows, and not comments to comments, this is very disrupting as it can bring me anywhere in the file, and I need to find and navigate back to where I was. I understand this might be useful for reviewers that only goes through questions left by other people, but this probably not most users, so it would be useful to have the ability to disable this feature.
The branch review window is large but not resizable. When comparing two-up web/desktop screens, it’s hard to see all the details. I know you can zoom or use the overlay mode, but I have a 27" monitor and plenty of room I just want to make the window larger so the two previews will scale.
Hello,some feedback from my side regarding Folders, I like the options of a nestable folder, but I find it hard to navigate to the files I’m looking for. The folders are named, but the file thumbnails that were visible with Projects were a huge readability feature that I’m really missing now.I was searching for it in settings, but couldn’t find a way to set it. I actually added a description to a folder, but did not actually see not one place that the description was shown? This part is especially confusing.If I could make an improvement suggestion to a current implementation it would be to have a setting to show or not to show some folder contents thumbnails, similar to the previous implementation.Fingers crossed this can be done!
In Korea, web development projects are typically divided into three distinct roles: Designers, Publishers (UI/UIX Developers), and Developers. Publishers implementation the design into code based on the Figma files, but they usually only have "Viewer" or limited editing permissions.The Problem:In typical Korean web projects, a single Figma page often contains dozens of frames representing all the individual web pages within a specific category. When multiple publishers collaborate on such a massive page, it is extremely difficult to track the progress of each frame/screen. Right now, there is no native, at-a-glance way to see who is working on what, or which specific frames are completed.The Suggestion:I would love to see a Page Status Label feature that helps teams manage this workflow efficiently:Status Indicators: Provide visual labels on the page list (e.g., "In Progress", "Done") so that publishers can self-report their progress. Smart Update Notification: If a publisher marks a p
Feature idea:Add keyboard shortcuts for any of these buttons at the top. This will increase user efficiency when iterating on prototypes.→ Quickly copy designs→ Quickly enter/leave annotation mode→ Quickly enter commentsetc.
the problem i need as much real state as possible to view the designs and screens am working in a readable viewable way, if the makes sense. to come around this, i currently scroll around and zoom in and out, or hide and show the panels, most probably its a mix of both. either way it’s a annoying… or i need to buy another real big monitor, but i already have a 15" macbook pro, which is great and enough when i hide the panels. this might be a big problem for laptop users without a secondary big screen, or who are portable and don’t have a dedicated work space. this is specially evident when they need to widen the left panel in order to view and read the layers tree. (which is another issue maybe raised in another topic) suggestion make side panels modular (photoshop/illustrator kind of thing). assets, layers on the left panels can be separable and can be undocked and moved elsewhere separately. design, prototype, inspection on the right panel are also separable and can be undocked and m
You can currently set multiple stroke colours to an object, but they will share the same properties (thickness, position, etc.). My idea is that you should be able to set all stroke properties on each stroke: Make sense or am I missing something?
When aliasing a color variable to another (img 1), or using it directly on an element (img 2), we should be able to override the opacity without the need to create a variable for each transparency variation: Cant override opacity in the alias: Example 2 Cant override the fill opacity:
Currently, you are able to use the ctrl+B command on a text style to apply the bold font weight to a desired string of text without breaking the text style. However, if you want to apply other font weights like light, medium, semibold, or black, you must either create a entirely new text style (which can add up quite quickly) or detach the text style and manually change the weight. A way to apply various font weights without breaking the style (in the same vein as applying different styling like bold, underline, and italic) would be extremely helpful in increasing a design system’s adoption and flexibility.
If I move a configuration of shapes and words, and then realize it’s not what I want, I can’t undo and go back to how I had it set up. Add as much context as possible (screenshots, Figma files, mockups, etc.)
The recent update of the Make panel UI has seemingly removed the ‘Go to Source’ button when in edit mode. You used to be able to select an element in the app, then go to the source code.The code would be highlighted for you and you can then make manual edits without the struggle of scrolling and navigating through the code to find the element you want to edit. Please bring back this feature!!
It would be a great idea to add the ability to move annotations (сhanging the place). Right now, they’re fixed in place and can overlap other elements. And you cannot change it.What I mean is the ability to reposition an annotation freely while keeping the link to the target object intact.Annotations are a really useful feature—thank you! Previously, I had to create similar functionality using my own objects. Please do not move this offer to another discussion. 🙏Can we move the Figma Annotations (in dev mode) from one Figma project to another?These are different questions.
Hi Figma Team,Thanks for the amazing work on the new Motion mode! It is a great update to the platform.I wanted to share a small feature idea that would improve the workflow. Right now, when creating returning or looping animations (like a button scale up and down), it takes some manual work to flip the keyframes and invert the Bezier curves.It would be awesome if we could select keyframes, copy them, and then paste them in reverse order using a shortcut (like Ctrl + Shift + V) or via a right-click menu option.Thanks for considering this, and keep up the great work!
Scale is one of my most used properties when designing interactions and states. It would be great if we had true ‘scale’ as a property. No, I’m not talking about the scale tool. That’s fake scale that affects the width/height of elements. I want the ability to enter something like ‘1.5’ and change the scale of an element, respectively.
I have a recurring use case: I want to create a gradient that fades to zero opacity while using styles or color variables. Unfortunately, this isn’t possible in Figma. I can only adjust the opacity if I break the variable/style binding. Why is that?
When i move my design elements/frames/etc., I expect all the pinned comments to move with them – but they don’t. instead i’m left with a bunch of floating comments (that are not attached to anything), which requires me to manually re-read each comment and move it again to its correct place. this is frustrating and time consuming. but what’s worse is when another user forgets to move the comments after they move the design elements, so when i return to the Figma file it’s very difficult to decipher the floating comments because they are not pinned to anything so i have no idea what they’re referring to. please keep Comments pinned to design elements (so moving design elements automatically moves comments).
Hi Figma Team,I work extensively with interactions when building prototypes—sometimes having up to 50 different interactions on a single element. Once I have finished setting all of them up, if I realize I need to add another condition or check, I either have to edit each one individually or, if I'm lucky and they all share the exact same conditions, I can select them all at once to update them.To make maintaining interactions more flexible and convenient in general, a JSON import and export feature would be a massive help. It would allow users to build conditions exactly as needed, export them, and then easily apply them to a completely new element, or quickly insert a new query/condition across all existing ones.Best regards and thank you in advance,Reke Buchenau
This new bulk edit option is so painful for non designer marketing team memebers to edit on there own. The whole purpose of buzz make it simple for marketing team to edit content on there own. And with now with per frame editing option gone, it has become so difficult for anyone to update content now. Also this new bulk edit feature is too buggy and keeps crashing
Our Foundations file is published as a library, consumed by other design files and by developers via the Variables REST API. We need to test changes — including adding/removing variables, not just editing values — without those changes reaching devs or other files until we're ready.Current gaps:Branches can't be referenced as a library from another file, so we can't test a branched foundations file in a separate screens file. Extended Collections only allow overriding existing values, not adding/removing variables. Our only workaround is manually duplicating the whole file into a "sandbox" library and re-syncing it by hand whenever production changes — error-prone, with no diffing.Ask: A way to stage variable changes (ideally via branching) and reference that staged version as a library in a separate file for testing, while production and the REST API stay untouched until we merge and publish. A diff view between staged and production would also help avoid drift.
Figma Slides are missing basic embeds.YouTube videos are the only supported format, where pasting a link converts it to a playable video.If Figma Slides wants to win students, teachers, and everyday use caes then it needs to support the biggest platforms we as Gen Z use:TikTok Instagram XThis is extremely easy support to add! If you want I’ll vibe code it for you tonight! Gamma will win without this.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.