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

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.

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

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.

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.

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? 

Same as in Slack or Outlook, would like to not trouble my commentees at odd hours and just send the comments I make outside of hours , inside office hours!

Hello everyone! I think having a shortcut to open/close the local variables would be very helpful. For example in cases where I’m prototyping and need to access the local variables to ensure the accuracy of the variable names or values that I’m assigning in the interactions. Currently, if I want to do this, I have to switch between the prototype panel to the design panel in order to open the local variables, check them and then go back to prototype. Note: I am aware that it is possible to keep the local variables window open, but this often leads to numerous bugs in the prototype. For example, when it is open, I am unable to drag the prototype interactions to reorder them.

Text weight should be allowed as a component property. Not as overrides or manual variants but simple text weight or size switch. I want to stop creating multiple duplicate variants within a component just for a font size change or a font weight change. I don’t think there’s any feature like this yet unless I am missing something.

Whether you search from the left side bar or press Shift + I, the thumbnails are too tiny to display details. Some of the assets would look similar from afar but if we’re able to resize the thumbnails as well as the window, it would reduce time dragging the wrong component.

There should be a way for Figma Admins and Workspace Admins (and potentially Team Owners) to be able to communicate Figma-specific news and information to members of specific projects/connected projects, teams, workspaces, or the entire organization (and groups, if they are ever added)Currently, organizations have to use email, slack, Microsoft Teams, or other tools to communicate about Figma topics, and these messages are easily overlooked since they are outside of a Figma context.It would be helpful to have a way to message discrete groups from within Figma. Examples of things that need to be communicated:We made a major design system upgrade New sticker sheets/templates are available We have deprecated holiday colors. Please remove any hard-coded holiday colors in your active designs. We have a new Workspace for xyz New reference designs are available in your Connected Project. Please check the comms portal for more ab

I'd like to be able to select a component and see all instances of use in the file. Sometimes my files get so large that I lose place of where I am using certain comps, or I am jumping into someone else’s file and it can be super confusing, if I don’t know where they are using that component. 

I’ve had multiple dev’s ask me where to find the core token to a second-order token value for a color when referencing mocks that use our design system. They are unable to see you can hover over to the more icon, and the only “actionable” thing they appear to be able to do is “copy” the variable name to their clipboard. Just asking to leave the “more icon” visible by default, there’s no real reason to hide it. 

it’s different from just using history. we are working on a file that was ongoing for years, some of the frames are old, some are new. we want to see what is the age of each screen to understand the timeline of our work. we could scroll back in time and see, but then we would had to jump between times, trying to discover and guess when a screen was created, rather then the possibility of just clicking on it and see the date of the creation

It would be nice if there was a way to set the default layout guides when you push + between two slides. Now it’s always set to one column and one row.

Hi,When designing screens for our platform we use 2 design systems within one frame and even within the same component. We have:Our own design system with light and dark theming Either Material Design or IOS 26 with light and dark themingCurrently it is, to my knowledge, not possible to use these two efficiently in tandem. For example:I can switch both to dark mode but then variables used from one design system used in components of the other design system will not change. To illustrate this: I use the tab bar from the IOS 26 library but override the text labels with variables from our own design system. Now, when I switch to dark mode these overwritten values will not change.Is there a solution that I am not aware of to tackle this issue? If not, perhaps a universal switch that works across libraries would be an idea?