Suggest a Feature

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

Hi, as I’m always on the lookout to work more efficiently, I’ve been surfing the web looking for a specific answer to my question which I haven’t found so I’m guessing I already know the answer, but here goes. I need to make an editable form in PDF which my client can open and fill in, in PDF. I can make up the form in PDF, either from scratch or from an existing PDF (exported from Figma), but the latter doesn’t work because even if I add form fields to my Figma file, Acrobat doesn’t recognize them. I found a plugin called Pitchdeck Presentation Studio which is great but it doesn’t say anything about fillable forms. I’ve tried the plugin CopyDoc Textkit which is also amazing but nothing on fillable forms. The only option I see now is to make the file in Figma without formfields, export it to PDF and add the formfields in Acrobat afterwards. Does anyone know a more effective workaround? Thx

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.

Currently, when exporting images for print, I have faced unfortunate results with poor image quality, which has caused inconveniences with printers. In addition, the export capabilities for the web could be optimized in terms of weight-to-quality ratio. I suggest the implementation of an Advanced Export Manager that would allow users to adjust the quality and size of images according to their specific needs in each context. Desirable features for the Advanced Export Manager: Pixels per Inch (ppi) control for PNG and JPG formats, allowing to select at least 300ppi for print and 72ppi for web. But ideally, the user can set the desired dpi. Option to choose the image size in pixels, providing flexibility in defining the width or height and thus resizing the image. Indicating the weight of the resulting file with each setting, facilitating performance optimization. Output format selection, including RGB and CMYK to suit specific color needs. Additional features to consider: Real-time pre

I like to show all (or most) properties of a component in my design library to make changes easily. However, this means toggling off a bunch of properties every time I use that component in a file, as many of them are more rare in use. Alternatively, I hide the properties within the library, but that means unhiding every time I want to make an edit. Sometimes I forget to unhide after, which means unwanted changes flowing through all my files. Am I missing something? If not – it would be great to separate library property state and default. See mockup.

I have a lot of projects on the go, but sometimes use projects like large folders. When I have these projects favourited, they’re on my sidebar neatly, but in the team view favourited and unfavourited projects are jumbled together and can only be sorted alphabetically or by last edited. My suggestion is letting you sort by favourites in the Team view (or even hiding them!) so you can scroll past them without problem. If I wanted quick access, I would use the sidebar.

Ugh. Just wrote a long comment that disappeared before I sent it because I checked something on another page in the file before sending the comment. I was about to click send, but wanted to be sure of something so I clicked on a different page in the page menu on the left. When I came back to the original page, my unsent comment was gone. Sigh. I usually copy unsent comments before clicking on anything just in case, but not this time. Suggestion: Seems like a draft comment should be saved in this case, and the comment thread would be in an unsent/draft state. Or, at least maybe warn the user if the comment is about to be erased. “If you go to a different page your comment will be lost. [Go anyway] [Stay here]” I’ve also lost unsent comments by just clicking out of the comment popup. Usually they shake when you click away the first time, but I’m pretty sure there have been times when the comment just vanishes on the first click outside of the popup. It really interrupts your flow.

Hi Figma Team, Since designers work on long-term projects, thus many design decisions can be forgotten, I suggest you create an Annotation Feature, unlike the comment feature, this one is hidden, where only designers can have access to it. The objective of this feature is to know why, as a designer, I decided to use this pattern instead of just recalling the reason. I’ve been working on a project for a year so far, and revisiting some screens, I can’t remember why was something done the way it is.

I feel that Figma’s Homepage can use some love! Starting with a ‘Search’ I cannot search my Figma files - much needed! I sometimes loose time in trying to find the right file because I often juggle a few tasks at the same time. The star & pinned are nice but I still loose time making sure it is the right file. Also, the card view preview doesn’t update properly which doesn’t help in my search. Maybe more zoom options in the Card View. But a ‘Search’ would be the most helpful to start with!

It would be nice to have the ability to resize elements using integers since decimal points are not ideal for web development. For example, using the command + shift + mouse drag combination to resize by integer values, instead of just shift + mouse drag.

Right now, I’m working on a plugin that needs to reset some of the styles on an instance so that they match its mainComponent. Through the UI, we have the option to “reset all overrides”, as well as resetting fills, strokes, etc. However, I don’t see that option in the Plugin API. It would be really helpful if we could add this so that we had a more fine-grained way of resetting instances that matched what the Figma UI is doing!

Much like sketch, sometimes I just don’t want anything to happen when resizing a Frame/art board. Usually this is a length issue and I just want to drag it down. Sometimes the user doesn’t want to assign full responsiveness/layout to components/objects at the start. Not having this can also be harmful to beginners who also have to go figure out all of auto layout/responsiveness. They don’t have the option to work/start without it. This “adjust content on resize” functionality can be turned off in sketch, Just looking for the same. It’s also a massive PITA, to go back have to check every object for size/resize because you didn’t even notice/forgot that you resized a few pixels, and now everything is off by 4.6 pixels for example. The default behaviour should be OFF, as typically users will setup a page/component before getting into responsive/interaction. This way, there’s no accidental sizing issues as mentioned above. This happens in sketch still, because they have resizing ON as the

Hi Figma team, It would be great if we can write description before merging branch to the main file. This is useful to keep track what’s new, what’s changed in the branch. Thanks!

Please add an additional function to Comments that notifies the author of the comment that their feedback or change is ready to be REVIEWED. There is ALWAYS a review step within our workflow. Never is it assumed that the designer has interpreted and executed the feedback or change in the correct way. By only having the “Resolved” function, it misses this critical review step, not to mention the Resolved function deletes the original comment with no way see what was originally asked for.