Suggest a Feature

This is a feature that would be amazing for a web image optimization processRight now there’s a lot of manual effort between Figma and Photoshop to resize images, then get them all exported as 80% jpgs or webp files

Hi! First of all-- congratulations on the release of CMS! I’m already super excited to create stuff with it and I’ve been playing around with it this morning. Hereby my humble feature requests for the future of CMS!Categories and tags with separate pages for their content. Search and date picker (for events) functionality. I would love to see component swapping supported inside CMS, so that I can pick a different component per CMS article if I want to highlight it on my list with a special component for example. (A feature like this would be ~ incredibly ~ powerful.) Or/and, the ability to change page variables in a CMS item, so you can for example change the colors of the page based on the variables set in the item. The ability to connect CMS fields to the SEO, so you can attach a meta description and social sharing image to each CMS article. The ability to hide CMS items from lists but still have them in your database and vi

Another nice addition would be to connect your FigJam files with related Figma files. So as not to rely on file naming. Creating links between the two would allow for easier navigation and discovery from others in the team.

Every time I open a file, comments are visible and I have to hide them manually with Shift+C. There's no way to set this once and forget it. A simple toggle in account preferences — just like the light/dark theme switch — would be perfect. Set it once, and comments stay hidden by default across all files.Also, visible comments noticeably slow things down, especially on older machines. Hiding them by default would make Figma feel much snappier day-to-day.

This has been mentioned here: Hide layer using variables - #5 by Andreas_Braendhaugen1 Invert boolean variable for layer display - #14 by Desislava_Slavkova Inverted Boolean Property - #2 by drewcovi_usb but those topics are all closed. I am looking for the availability to HIDE a layer when a Boolean variable is TRUE and SHOW it when it is FALSE. So, the inverse of the default/current behavior. I want to do this without using components. Use case: When a variable is true, show one frame. When that same variable is false, show a different frame. I can get basically this by using two different variables:

Hi When will sorting and advanced search for CMS elements be available?Is there any approximate date?Thanks!

I have successfully rasterized last Friday. But two days later, which is now Jan 13 2026, the Rasterize selection disappeared in object menu. I can only find it by searching Actions… Is there anyone can help me look into it, thank you so much!i use macbook pro 15-inch, 2018, Vetura 13

I created a component, with some variant and properties.This component is then used in a Buzz template. This is then used to create social media assets.  When I first copy-past the component into the Buzz template file, the properties are here (all of them), and as soon as I publish the templates, they di (see attached screenshots).Also, the nested properties work perfectly.This is weird, is there anything I’m doing wrong, I don’t get it.And I also noticed, that basically I cannot add Variant properties in a Buzz file, it just doesn’t work. Maybe there is a bug on and that is why it removes my orignal properties ?  

I have been doing more logos in Figma, but usually have to also provide an .eps file. The issue with exporting as an SVG and importing into Adobe Illustrator is that the font gets converted to Outlines. Then I have to re-create the font in Illustrator

In addition to having AI design the entire wireframe (which results in a lot of output that isn’t really relevant or useful to the user’s specific needs), Figma should implement a version of its AI tool that improves/beautifies user-created basic wireframes (eg. takes the text/button names/general layout that someone has already created and adds colors, changes typography, moves things around so they’re visually more pleasing, etc). This would allow users who have a general vision of what they want their product to look like to save time creating more detailed wireframes so they can more easily transition to the prototyping phase. 

Hi Celine- Are there any plans to remove this constraint? We have container frames with a handful of separate screen specs in them and would like to designate certain screens as ready, but not the entire set. It’d be great to not have to have the frame or instance top-level, but allow nesting and still mark contained elements ‘ready for dev’. Thanks!

My Figma files are growing with screens, especially example screens to showcase various states. I’d like to keep them organized by arranging them in separate pages, but the thing is, I need to be able to prototype from one screen to another, over different applications to showcase a complete user flow. Would there be a feature one day where you can prototype between different pages, like Excel for example, where you can refer to cells in other tabs or even files. Would be nice.

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.

Figma: If you’re used to working in another design tool, you may find it strange that your text styles in Figma don’t include traits like color or justification. Although it could take some getting used to, hopefully the benefits of this approach will quickly become clear. Well, no it didn’t. And strange indeed. In addition to getting used to, it takes a lot of time to to change the color every single time I create a new text element, because our text color is not black. Having a default color saved with text styles would be SO. MUCH. EASIER. I see no reason why the color can’t be in there and also be changed when using the style, if necessary.

Hi,“Hide prompts when sharing a Make prototype” seems extremely straightforward, but is not yet possible, thus this feature request.I love working with Figma Make and want to integrate it into the prototyping workflow. Unfortunately, sharing Make prototypes turned out to be a real headache. But without being able to share a prototype externally (and temporarily), the whole Make prototyping workflow doesn’t make sense, since copying the prototype pages into design doesn’t copy any interactions or animations. The goal: Share the Make full-screen preview with external viewers, without showing the AI chat history # Problem 1: Prototype viewable for logged-in users onlySharing did not work for not logged-in users, for whatever reason. Figma support couldn’t help either, thus it might be a bug.Workaround: Create a free account for the viewer, then share the full-screen previewTo shorten and speed up the wh

Hi all,Have you considered adding a feature to the auto layout “gap” feature that could allow a user to set a minimum gap i.e. 8px and a maximum gap i.e. 40px?I’ve recently needed this function for building bar graphs. I need to make them responsive without getting too small and overlapping on each other or too big when expanded.

Give Figma the ability to display an artboard(s) of one Figma file to another Figma file. So, rather than copying and pasting between two files (detaching it from its source of truth), the designer can “insert/link” the artboard to be displayed on another Figma file. Then, if the inserted artboard is updated, it will also update in the file where it is inserted (or any other instances). Very much like components work today but w/out the need to turn the entire artboard into a component.

An edge case however I’d love to see this update eventually. I have a segmented button component that contains nested button component variants. This segmented button component lives in many different places in my UI, utilising the different forms of the nest button component (text , icon, icon and text) I’d like to be able to set a min width to the nested button components inside my segmented button component instance WITHOUT having to set the min width to the master button component.

The title case isn’t accurate. As it also capitalizes: articles (such as “a,” “an,” and “the”) conjunctions (such as “and,” “but,” and “or”), and prepositions (such as “at,” “by,” “of,” “to,” and “on”). In my opinion, the better naming would be “Capitalize”. Figma team can also consider adding “Title Case” and “Sentence Case” options separately.

I happened upon this quick action: “Debug broken fixed-scrolling layers”. I searched Google and this Forum, and I can’t find any documentation or mentions of this feature at all… Figma team, I would love to see documentation for quick actions! It would help in scenarios like this (I found a quick action and I want to learn more about it). It would also help Figma users discover useful quick actions! I’m sure there are tons

You can embed YT videos into Figma Slides, but appears to lack Vimeo support. Also, we can’t change the Embed settings (turning off suggested videos, etc.) Would love support for these!

It would be really helpful if you could add a setting to Components that allows for “Scale Strokes & Effects.” Doing it at the component level would allow icons to be made with strokes rather than fills which is way more versatile and agile for making updates and modifications. Right now you have to use K Scale to “scale” them which is unfortunately NOT intuitive. It’s all about consistency and efficiency - this would help a lot.

Organization would be immensely helpful if we could create folders for our drafts. I want to be able to organize my drafts into different categories (such as UI kits, Ideas, Wireframe kits, iOS, Android, etc…) so I can find files easily. Right now, the drafts page is a huge jumbled mess and I can’t create Team pages for everything. Maybe something as simple as being able to add ‘tags’ to each file, similar to Zeplin.

We use pages as rounds of revisions, so it would be nice that in the page. We could just section out the frames we presentation. I know it’s not best practice to use design file as slides function, but it’s just faster to design in design file than the slides. And there are some archives slides in the same page that I don’t want to show in presentation mode of the page, but it could not be done unless I remove them or hide them. So could we have a function to manage what slides to show and hide based on the section, and use section as the prototype link?