Suggest a Feature

Would be nice if the Figma desktop will pickup the fonts as you install them, without the need to hard quit the application each time you install a font. Hope the team takes this into consideration! Thanks!

Many times we use component level tokens. Variables like “card-heading-color” manages the color applied to the card component title. In Figma there is nothing that links these. The variables do not move with the component. It would be nice if a variables collection was named the same as the component then it would “link” those. Moving a component should also move it’s component tokens. There should be an option when adjusting a component’s properties should only show that components variables collection. So we can “scope” variables/tokens to a specific component.

I just gave a presentation to a pretty large group at my company. I had the frame that contained a component that was interactive. It was a bit buggy and had to resort to exiting presentation mode. Components within components and them all having prototype wiring seems to get funky.

This is on my personal account under all my Drafts. I have a paid Figma plan on my work account, so not sure why you’re trying to upsell on my personal account.

As an Spanish keyboard layout user, I often make the mistake of creating a new design file with ctrl+n, because in Microsoft Word, that is the command to convert text to bold. But all those files are empty and have the name “untitled” (i know it sucks, changing office language would make relearn excel altogether)

Hi. I’ve been working with booleans and variants and are a nice way to set a component state. What happens is that, if a component has several states, and all of them have hover states, I have to create a hover variant for each variant, and seems like not a good workflow, in my humble opinion, just for a hover state. So, what if through the interactions panel, where it says While hovering/Mouse enter, etc, there could be a way to apply a layer property, like size, opacity, or toggle show/hide? That way, just for the hover state, there would be no need to create variants, just applying logic through the interactions panel. Or maybe I’m missing a feature and this is possible in another way 😅. Well, that’s it, the possibility to interact with layers/objects through the interactions panel, like opacity, size, rotation, and, why not, modifying text. I believe UXPin does this, so hover states are just smooth, just that. I hope that my explanation makes sense. Thank you.

I have a QWERTZ keyboard. All shortcuts using symbols accessible through Shift+[Number] do not work. For instance CTRL + / .

I need to select anchor points on a shape or across multiple shapes In Figma, I hit Enter and go into Edit Mode. Currently, I can only use rectangular lasso options. I’d really prefer lasso style options, specifically a free draw lasso like in Illustrator. Shapes get bizarre and weird, and often a rectangular lasso just doesn’t cut it. Across the board, the lasso tool in Illustrator is the biggest reason I keep using Illustrator for shape editing instead of Figma. What are others thoughts on selecting anchor points in Illustrator vs in Figma?

It’d be nice if we had a way of playing image sequences on scroll so as we scroll down it seems like a video is playing and if we scroll back up the video rewinds, similar as the animations on the apple display site or the scrollsequence tool

Tôi rất muốn có một cái nút quay lại để khi làm sai đỡ mất công làm lại 1 cái khác khi có việc gấp, nếu cứ sai một bước làm lại một lần thì cứ cho là tôi bất cẩn nhưng quá nhiều nếu như lỡ tay một phá thì làm của tôi sẽ bị xáo trộn lên mất.

I work at a fairly large company with a big design team and it is hard to keep up with what is going on. It would be really great if there was a section in our ‘All Teams’ page where our Admins could post announcements, updates, and generally communicate with all the users in our team. For admins/design leads, this could be a great way to communicate big updates, product releases, big wins, and even team shout outs. For designers, this would be a great way to keep up with team wide goals, product releases, and big design changes. And for stakeholders, this could be a way to have greater high-level visibility into the team priorities and new product releases. Figma already has such a great communications system in the comments, but it would be great if there was a place external to the files where information could be shared.

Please refer to this thread. We’re looking for a template like MIRO boards which has the ability to add new nodes and shift everything else automatically. Add User Story Map template Template, plugin, and widget ideas Similarly to what I used in miro, I would love to have a User Story Map Framework template; It should have user Goals, tasks, and vertical lines for releases. Would be great if newly added tasks snapped automatically to some kind of alignment, so that it looks clean at all times, even if I move the bottom to the top and so on

It’s annoying having to click, show min, click show max. Every. Time.

When setting up components for prototyping, the ability to ignore/exempt certain items from the components persistence with prototyping would be a great feature.

I would like a component or layer with auto layout to be in fill but fixed in the place I need, for example in a side menu, that remains fixed but is filled with the height

Hello! I’m a UX/UI designer based in Korea, and I’m an avid user and fan of Figma. The prevalence of Android users in Korea is significant, with seven out of nine people using it. Moreover, with over 3 billion active Android devices worldwide as of 2022, this number is expected to have further increased by 2024. However, there are several aspects of Figma’s devmode that present challenges when designing for Android screens. I believe Figma would garner even more affection if it could seamlessly generate images in various Android densities such as hdpi, mdpi, xhdpi, xxhdpi, xxxhdpi, and xxhdpi, ensuring no deviations on the screen. Currently, for Android projects, designers often resort to using other less intuitive services due to the limitations in Figma’s devmode. They wish for Figma to provide a more seamless communication channel between designers and developers. Thank you.

Let’s do copy name of font! Like Adobe products

Why does “Constrain Proportions” do absolutely nothing? Why have this at all if it only works in one limited use case? I create an SVG. I plop it into my design, and want to scale the parent frame up/down using variables. When I do this, the SVG (which has constrain proportions turned on) ALWAYS gets smooshstretched to fill the parent frame… the exact opposite of what constrain proportions should do. This has been an issue for years, and remains off the radar. Please fix this.

I’m a developer that works from Figma files. Our design team uses emojis at the start of the file names to add custom favicons and organize their work. This is useful for them but creates confusion for me when trying to find the Figma tab among the other tabs I have open for my work. Chrome extensions I tried aren’t able to solve the issue, presumably because they set the favicon when the page loads and Figma then overrides it afterwards. I’m suggesting a user preference option to only use the default Figma favicon instead of the prefixed emoji from the file name. I’ve emailed Figma and they suggested to post here as well so here I am. Have a lovely day everyone! 🙂

Ability to customize the favicon in a design file, prototype, or FigJam file. It could be changed to a logo, color, or first initial to identify which tab is for which workstream more easily. It would also greatly help with the scanability of any pinned tabs, which today the user is only able to see which file it is on hover preview, or knowing the sequential order of your pinned tabs. Please Figma I beg you 🙏

Be able to save locally a copy of all our files every certain period of time. I dont want to relay soly on Figma for back up, what happens if they get hacked?

One of the challenges we frequently encounter involves the management of comments attached to specific designs when those designs are moved from one page to another within the same file. Currently, when designs are moved, any associated comments do not automatically move with them. This creates a disconnect between the designs and the feedback provided, potentially leading to confusion, overlooked suggestions, and a disjointed review process.

I am the Figma admin (full-time UX Designer) for a university. I currently have three part-time student designers working on projects. These projects benefit all students, staff, faculty, and I work with our student designers to work through concepts, prototypes, building a design system, and collaborate with managers and developers. On one project, we have one full-time developer and 2-3 part-time student developers who work on these same projects. There is no easy way to have student workers on an educational plan mixed with our paid plan teams/projects. Ideally, we would want the ability to have educational plan Design Seats and Dev Mode Seats working on project under our paid Org plan. Paying for Designer Seats for part-time students might make sense for a few designers but the cost for part-time students using Dev Mode doesn’t make sense for developers. We really would like students to get experience with real-world collaborative experiences in Figma. They are learning much more t

This might probably has been suggested before but it would be a great if FIGMA add’s freeform gradient feature built into the gradient section, in addition to “Linear”, “Radial”, “Angular”, “Diamond”. (Just like Adobe Illustrator)

We were pleased that the new typography tokens allow us to offer a default mode (base size 16 for accessibility) and a dense mode (base size 14 for table-heavy applications with reduced accessibility on request). But for this to work with Figma right now, we would have to create separate tokens for each text style so that we can change them with the modes… This just seems not feasible. Because in code it works by changing 1 single variable - the base size - we would have to create a BUNCH of extra design tokens just for Figma and then hide them from publishing so they do not appear in our documentation.