Suggest a Feature

I have a suggestion that I think could be really useful: allowing country flag icons to be added to Figma page names.Sometimes, designs vary by country, so we may need separate pages for each market, while in other cases a single page may cover multiple countries. Having country flags available as page icons would make it much easier to identify and organize these variations at a glance.For example, this is currently the best workaround I’ve found to represent the US and Canada.  It would be great if you could consider adding this option in the future. I believe it would be especially useful for teams working across multiple markets.Thanks a lot for the attention.

Everything is in the title, it would be amazing so when only one screens is ten foot long, your section can be small for all other screens.

Request: Through the Figma MCP, access contents of comments made in Figma Design file.Reason: Can provide context for designs, review bugs, etc.Current response from OpenAI Codex with direct link to comment:No, not the comment itself.What I can see from that link is the node it points to:file: XXXXXXnode: XXXXXXscreen: /sign-up-2 (iOS)That screen contains:nav title Sign UpEmail and Password inputsSign Up primary CTAContinue with AppleContinue with Googledivider OrAlready have an account? Sign inbottom legal linksBut I still cannot read the actual Figma comment thread or the #XXXXXX anchor content from this session.If you want, paste the comment text here and I can map it to this exact screen and tell you what change it implies. 

Buzz needs the ability to export higher bitrate. It currently exports at 4 Mbps, so any Buzz exports published on Instagram are extremely low quality and streaky. The platform needs at least 30mbps, or the ability to also export at 12mbps, which will account for Instagram’s native compression as well. At this point, Buzz is not usable as all exports are low quality when published to social. 

 I like outline view because it gives a really good overview of the structure and is helpful when debugging alignment issues. Where there’s raw (editable) text it becomes very busy – I don’t think this text needs to be outlined, I can’t edit the paths and it creates a lot of visual noise. Totally makes sense to have the paths visible if text has been converted to paths however.

We work in a large company with over 100k employees and have very strict rules on how to share content with clients. What we are missing are advanced sharing options for “only-view”. Sometimes, we want to share content as a ‘view-only link’ with the client to receive comments and feedback directly on the artboards. Other times, we want to share as a ‘view-only link’ but without the possibility for viewers to leave comments. This crucial option is currently unavailable for us, and it would be great if this feature could be added to the sharing options. Thanks! 👍

Hi, I came across a similar idea - Search results are not precise - we get 'similar words' instead of exact match but unfortunately in Figma still missing. I think the exact search by name is a “must have”. Furthermore, it would be very useful if it were possible to find instances of a specific component, according to the specified properties. I think both functions are quite essential for keeping documents in order. Do you plan to add them please?

Please add auto nested code block indentation to Specs in Figma, please, instead of having to indent manually. Manual indent for new lines for nested CSS/code blocks 

We have a design system set up with tokens (variables) to enable all components to switch between light and dark mode. For developers/viewers to see what a screen should look like in Dark mode, we have to duplicate that screen. But as an editor I can set the colour mode variable at the Page level to Dark and all screens on the canvas/page turn to dark mode. If developers/viewers could also do this, I could delete the dark mode duplicates of every screen and only have one copy of each screen, defaulted to light mode, and then just toggle dark mode as needed. This would be much more efficient on memory usage and maintenance.

Been playing around with the “expose nested properties” feature currently in beta. One of the great uses of variant properties is the ability to batch edit property values on multiple selected components. That use doesn’t carry over to exposed nested properties (yet I hope). Demo file to help When selecting one component instance exposing nested properties, said properties display fine. Add another instance of the same component to your selection (using Shift+Click), and the nested properties outright disappear from the right panel. I haven’t seen this issue raised elsewhere! Do you experience it too?

Today I tried to search a file in Figma and discovered that the search-by-team filter has been removed. We are part of a large organization and do all our work within one team folder; without the ability to narrow down my search to our specific team, we’ve essentially lost search. If there’s no room in the universal-search filters anymore, maybe offer a separate search function at the team level? Please bring our search back! I don’t want to have to go back to scanning files manually within folders for 2+ years worth of work.

I find the new Grid feature in Auto Layout really convenient for building tables. It’s easier and more flexible than it used to be, when you had to set up separate Auto Layouts for rows or columns, making it much more cumbersome to change the content later on.However, it seems that this approach makes it impossible to implement a hover effect across an entire row.The old approach is still an option, of course, but I design applications with many different types of tables, and I’d love to implement this behaviour system-wide, without having to create new components for every table.I realise this behaviour wouldn’t make sense for every type of Grid, but it could be an optional setting for each individual Grid, such as “Extend hover to entire  [ rows / columns ]”.I think this would require naming conventions for component variants, since there’s no way to know what the cells contain.What do you think?Thanks,g

Hey there,  we often Work with Images directly on our Boards (I bet most of you do). So if I want to create an Image Fill for a Frame, why can’t I just select the Image from the board (as we can do for Pattern Fills) instead of Uploading it or making one? Would be a very helpful Feature! Best From Austria.

Has anyone found a way to have a color variable for bulk create in Figma Buzz? For example, I have an ad. I want to make 5 variations with different background images. I also want each ad to have a different font and button color. Do we think there will be an update down the road to make these edits in the google sheet for bulk create or will it need to be done manually after creation? Am I missing something? Thanks!

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: but it would be more convenient to be able to do it with just one. Just give me a Boolean toggle when the variable is used to say if the variable should be inverted or not.

Figma motion does not currently have the ability to play and export video fills, so video objects are treated as static images. The ability to incorporate video objects into the timeline would be extremely helpful. Exposing the current frame of a video as a keyframeable property be a great solve. 

I just want to adjust the page settings for each page “frame” so to speak so I can make it wider. It’s not clear that this is possible.

SummaryAdd an option to prevent variables used in published components from being detached in consuming files. ProblemWhen a component library is published and used in another Figma file, consumers can detach variable bindings, potentially breaking the intended design system consistency. For libraries that rely on variables to maintain component integrity, this can lead to unintended overrides and make it harder to ensure consistent usage across files.Proposed SolutionIntroduce a setting in the variable's Details panel, such as “Prevent detaching in consuming files.”When enabled, this setting would prevent consumers from detaching that variable when it is used within instances of published components in other files, while still allowing the variable to be used normally elsewhere.Ideally, this restriction would apply only to the variable's usage within the relevant published component, rather than globally across every component or property that references the same variable.Why This Mat

This seems like a very large design oversight in Figma Slides. The help article says that “Published changes only apply to new slide decks that are made with the template.” Doesn’t this defeat the entire purpose of having a custom template where you can edit a style and have it apply to your entire presentation, instead of needing to manually tweak a header style on every slide? I expected this to work the same way instances update in Figma Design when you make a change to the main component, but even after publishing changes to a custom template in Figma Slides, my existing slide deck that pulls from that template isn’t updating colors & text styles. The published template changes would only apply to brand new slide decks, which means I’d have to define the template first and then create my slide deck. That completely goes against the general approach to how many of us create slide decks. For example, I don’t make the template before I start the slide deck. I make my slide deck fi

Hey folks, first of all I love the new variable function. Within the setup of spacings I want to reference my base value (“8”) and do calculations, e.g. (spacing-base)*2". This works fine and the value is calculated properly within the input to add a new variable. But I expected not that the calculation string changes to the absolute value. With this behaviour I loose the connection/ reference to my base value and the calculation is some how obsolete. Does anybody feel the same? Will there be an update? Thanks

The desktop app keeps every open file tab fully loaded, each in its own renderer process. With ~12 file tabs open (design system libraries, UI kits, product files), Figma uses 7–9 GB of RAM on my 18 GB MacBook (M3 Pro). That pushes macOS into 8 GB of swap, slows the whole machine and drains the battery. Quitting and reopening doesn't help, because all restored tabs load again right away.The usual advice (close unused tabs, restart, clear cache) works, but I lose my tab setup, and the tab bar plus the native menu bar are the main reasons I use the desktop app instead of the browser.The interesting part: the desktop app already has tab discarding. Its config is delivered as the dynamic config desktop_tab_discarding and ends up in ~/Library/Application Support/Figma/settings.json:"desktop_tab_discarding": {  "default": {    "tabInactivityThreshold": 172800000,    "discardCheckInterval": 3600000,    "minTabThreshold": 5,    "minNonDiscardedTabThreshold": 3,    "gracePeriod": 1800000,    "i

When adding components to a Slot and attempting to surface nested properties I see a message that nested properties can not be surfaced with Slots. This severly limits their usefulness to us since we are creating multiple composable components using sub components with properties and having to drill in to each instance in a multi-item Slot is very time-consuming.

Description: As a designer with many years of experience, I do almost all of my design work in Figma, including print and packaging projects. However, working with print layouts in Figma currently faces two major bottlenecks: Pixels-only constraint: The lack of physical units (mm, cm, inches) and DPI settings forces us to constantly calculate and convert print dimensions (like 300 DPI) into pixels manually. No CMYK color profile support: Because of this, we still have to switch to Adobe Photoshop or Illustrator for final print preparation. Proposal: If Figma added support for physical dimensions and CMYK color spaces, it would eliminate these workflow gaps and become the ultimate all-in-one tool for both digital and print design.

Feature Suggestion: Custom Folder ThumbnailsWe all know that folders currently display thumbnails based on the files inside them. While this is useful, it would be even better if we had the option to set a custom thumbnail for each folder.For example, imagine I'm working on products for Meta and have separate folders for WhatsApp, Instagram, and Facebook. Instead of showing file previews, I could set the WhatsApp logo as the thumbnail for the WhatsApp folder, the Instagram logo for the Instagram folder, and the Facebook logo for the Facebook folder. This would make folders much easier to identify at a glance and help improve organization, especially in large projects with multiple brands or products.It would be great to have a "Set Folder Thumbnail" option that allows users to upload an image or choose a file frame as the folder cover.If you'd find this useful too, please leave a comment or like this suggestion so the Figma team can consider it. Feature Suggestion: Custom Folder Thumbn