Share Your Feedback

Hi, I have a component that has a video (in order to play it in prototype mode). In today’s update, it’s displaying a “video” label and a big “play” icon on the canvas. While I think it’s nice to preview a live video on the canvas, I also want the ability to hide this elements (since they’re not part of the design specs). I was wondering if there’s a way to hide this? (the attached screenshot is a good example of specs that I often attach and I don’t want developers to think that those elements are part of the design).   

We just wrapped the big announcements at Config, and we know there’s a lot to take in.This thread is your space to share reactions, ask questions, and let us know what you're excited about (or still curious about) with regard to Figma Draw. Our team will be actively reading and sharing relevant takeaways with the product team. What we’d love to hear from you:What aspects are you most excited about — and why? Where do you still have questions or want more clarity? Anything that didn’t quite land for you yet? A few quick reminders:If you need help with a specific account or file issue, please get in touch with a specialist on the Support Team. A note on Community Guidelines: Posts that veer off-topic or become unproductive may be moderated to keep the focus on the product at hand. Keep feedback focused on Figma Draw — this helps everyone follow along.

 Can we merge all Figma skills into a single one? Otherwise there are too many skills in Codex, all of which are Figma‑related, and they take up too much space.

Greetings, I’ve been using an AI agent to develop a prompt to review figma concepts to cover the following: UX heuristic using NNg as the foundation, UI errors, and Grammatical errors. The prompt needs to be copied from the Ai tool and implemented in Figma Make. Figma Make has to recreate the reviewed design exactly before this prompt is implemented to review the design. This is a lot of steps to review a designs. Will Figma introduce a a feature to fully review designs on an artboard covering those items? UX errors, UI errors, and grammatical errors?

Currently, when we have many files open in Figma (which is not uncommon in a work context), we tend to lose visibility and access to some of them when trying to switch tabs.Intuitively, I try to scroll horizontally through the open file tabs with no success, which makes navigation quite difficult. As a result, I either have to drag the entire Figma window to the side to expand the view or feel forced to close files just to access others.Is there any plan to improve this usability?Thank you.

It is annoying when I have to libraries connected to my project, but it always autosuggests the wrong library when selecting another text style. I want it to show me the selection of text styles from the library that the text is already using – not text styles from the other library. This happens also when selecting color. This issue wasn't an issue before. As you can see in the video attached, the library I want based on the component selected is collapsed. I want to library that is already used for the object in question to be expanded.

There are several collections hidden behind the expand buttons without any clear indication in the UI.It took me a few minutes to find hidden collections. It’d be great to add more affordance somewhere so that a new team member knows there are hidden collections under “Variables” window.  

I was very excited to hear that grids were coming to Figma. CSS Grid was introduced years ago and brought with it many things that flexbox was incapable of doing, so I was hoping for a similar level of new capabilities here, and I genuinely cannot believe that this feature is being shipped in its current state (even as a ‘beta’). This is a very long post, but I feel like this feature has been implemented so poorly that it legitimately sows doubt in Figma’s capabilities to deliver features in the future.Inability to ‘hug’ contents Both rows and grids themselves are unable to resize themselves to match their contents (‘Hug”). Row heights must be either “Auto” (1fr) or a fixed height, meaning that if you want your rows to be sized per their elements, you’ve now manually defined each row height in px (not even a variable value), and instead of getting a clean CSS output, now you have however many rows defined in exact values, destroying any chance of scalability. This alone makes this fe

The latest update is erasing my color styles. This is ridiculous—what's the point of releasing updates that don't work????? I'm fed up. Why???????

Howdy, I’m a noob with dumb question. Where’s the dark theme mentioned on https://help.figma.com/hc/en-us/articles/5576781786647-Change-themes-in-Figma ? “Actions menu” doesn’t contain any of these: “Use dark mode”, “Use light mode”, “Use system theme”.And why should I, dumb user, even search this essential feature somewhere in sub-sub menus? Can you even find it yourself, intuitively, while your eyeballs are on fire?“Color profile” is not what I needed.

 Hi Figma team,I wanted to share some feedback based on my experience using the Organization plan, specifically around Dev seats, billing transparency, and external collaboration.1. Dev Seat Pricing vs Actual Charge (Proration Confusion)On the pricing page, a Dev seat is clearly listed as $25/month. However, when attempting to add a Dev seat, the upcoming invoice shows a charge of $175.89.While I understand this is likely due to prorated billing until the end of the billing cycle, this is not clearly communicated in the UI.Issue: The pricing page sets an expectation of a simple monthly cost The invoice shows a significantly higher amount without a clear breakdown Users are left confused and unsure if this is an error Suggestion: Show a clear cost breakdown before confirmation: Monthly price Proration period (e.g., “7 months remaining in billing cycle”) Total calculated cost Add a tooltip or inline explanation explaining why the price differs from $25 2. Lack of Cost

As the Admin in Figma I’m getting Dev or Collabseat requests frequently which are unintented. Figma makes it too easy for the people to request for a payed seat. This is a dark pattern and I do not expect this to see in such a business application. It’s very annoiny since I always need to double check if the request was intentionally (it never was until now). I expect figma to change that behavior. It cannot be that the most prominent button for a viewer is the “request” button. 

If you’re looking for dependable scientific instruments with international delivery options, check out ADAS Instruments (https://adasinstrumentsonline.com/). They offer a wide range of lab equipment — from analytical instruments to educational science tools — with detailed product descriptions and support. Their site makes it easy to compare items and place orders directly.

I think that when there are only two options, a drop-down menu is unnecessary; instead, we could opt for other options that speed up the process, as they don’t require two clicks to make a selection.

 The current libraries styles search is a fuzzy search in which it shows close matches like different colors of green when searching for green. This is nice for being able to see similar results to the search parameter but is frustrating when typing an exact variable name and it returns another variable that is related but not match. The example I’m providing below if from a color library that has both the color ‘lime’ and ‘green’. If I search for green my results show the ‘lime’ results first and I have to scroll for the exact match of ‘green’.  I have run into the same issue with ‘indigo’ and ‘purple’.This interaction could be improved by rearranging the results to show exact match results at the top and the fuzzy matches below. If someone takes the time to type a keyword that matches their variables they shouldn’t have to scroll for their result. Top results when searching for green. Would expect my exact search result to be the top result rather than the fuzzy match of lime (green)

Hi Figma. Really trying to give Slides a go, as I’d rather use anything over powerpoint, but I keep running into features stripped from the Figma Design that remaking it impossible to continue. For one, I cannot understand why I can’t access the variable library. My slides were imported from a file that had a deprecated library, with colors and modes that are totally unused by the assets I imported. There simply does not seem to be a way to remove those… at all. They’re permanently stuck in this presentation unless I want to start from scratch. Currently I’m making a table but I’m unable to vertically center text within a cell. This is a hard requirement for making tables that look good that use the type styles I'm defining elsewhere… otherwise I have to manually set the line height to match the table cell height which is nuts. I also created a symbol that consisted of a text box and rectangle to act as an off-center highlighting. I was unable, fully unable to tie the text in that symb

 Beware of this, people. This is such a hidden scam.

Hey folks,Figma's latest color tokens search update has added a new behavior to searching. I use my Primary token a lot, and I'm used to searching for "prima" for it to show up. Since this last update, searching for that makes my Disabled (#AAAAAA), token show up first, due to it having "A" in it's hex color code.My personal view is that it should weigh my search content in order to decide which content is shown, since I'm most likely not searching for "Disabled". Nonetheless, loved the other improvements that came with this update.Would love for you to share your opinion about it! Color token search panel, searching for "prim" and "prima" 

It’s quite annoying when every time I select any component or shape etc, I need to click at the “show more properties button”, it makes me fill time

I have seen a lot of posts on reddit, linkedin and here all complaining re: Figmas opaque billing practices being so dark pattern-riddled it would put most scam sites to shame. There are countless posts across the web as old as 5 years complaining about this but I’ve yet to see any meaningful change. Adding seats and over-subscribing is way too easy with few guardrails, but reducing your subscription is far more unclear and difficult.What will it take for Figma to actually do something about this? Why is nothing being done?I keep having additional seats added to my plan accidentally. This has happened to my organization at least 3 times now. Every single time I fix the issue I go through the labyrinth of admin billing settings and think I have all my bases covered, but this system seems to be designed explicitly to funnel users into higher billing. The latest is because “Seat approval settings” was set to “Manual unless seat is available” (I had an unused seat, which was added because

I was in the process of handling my offboarding and role handover. While managing user permissions, I first removed my own Annual Full Seat access and then assigned an Annual Full Seat to another person.However, when I reviewed the billing, I noticed that I was still charged a billing adjustment for Monthly seats. After checking multiple times, I found that I still had individual edit access to a project within the team, which resulted in a charge of $10.32.I would like to request that Figma revoke this unexpected charge caused by my accidental operation.  

Using Claude Code connected to the Figma MCP Server, when asked to implement a screen with various different buttons, only some of the buttons were implemented as pressable (as buttons). Although the buttons looks different, they all had default and pressed variants and had the word button somewhere in the name. Looking into this further, Claude Code reported back that, “The MCP tool's code generation is inconsistent — it renders full state branching for some components and only default-state code for others, depending on how complex the Figma component is.”Question is, why is the Figma MCP Server not generating the full code, and is there anything that can be done on the Figma side to help with this?

We just wrapped the big announcements at Config, and we know there’s a lot to take in.This thread is your space to share reactions, ask questions, and let us know what you're excited about (or still curious about) with regard to Figma Make. Our team will be actively reading and sharing relevant takeaways with the product team. What we’d love to hear from you:What aspects are you most excited about — and why? Where do you still have questions or want more clarity? Anything that didn’t quite land for you yet? A few quick reminders:If you need help with a specific account or file issue, please get in touch with a specialist on the Support Team. A note on Community Guidelines: Posts that veer off-topic or become unproductive may be moderated to keep the focus on the product at hand. Keep feedback focused on Figma Make — this helps everyone follow along.

Right now, I’m loving slots. They’re great and exactly what I’ve been missing, but there is one quark that is causing me extra time.I’d love to be able to prescribe a child height/width behaviour for any elements that are added to the slot. I’d love to be able to say “I want any child added to this slot to have width property set to fill by default.”An example where this is annoying. Right now, anytime I drop a container in a slot in my modal component, the I have to prescribe the height/width behaviour for the container instead of it snapping into place in the available space. In Menus, every time I add a new menu item or a divider or a heading, I need to select them all and say their width should be set to “Fill”. Its a small thing, but it adds up over time.

I love Figma, and it’s the first tool I open every day. Recently, I have been getting a figma session time out error every day. My teammates has reported the same. It’s making me login via Browser (SSO login) every single day for the past 2-3 weeks. It’s not been the most delightful way to start my day, as the first thing I do as a product designer is to open Figma. It use to just work. Is there anything I can do to fix this? Thank you!