Share Your Feedback

Don't get me wrong, I love working with figma and I greatly appreciate what value this software has done for designers and business. However, I will never understand why such simple solutions as folders for pages or "CSS Margins" (the basis in HTML) have not been included in this software for many years. I understand the pursuit of money and the AI ​​trend, but don't forget who makes your business run. People are very willing to jump to an alternative as soon as it appears and offers what you haven't been able to offer for years. Don't make the same mistakes as Adobe.

Dear Figma Team,I am experiencing several issues with Figma Sites and would like to share some feedback: CMS Collection Export I would like the ability to export CMS collections so they can be imported into another file. For example, when upgrading to a newer version of a site, it is not practical to recreate all CMS content manually and fill every field again. Plugin Access in Figma Sites It would be helpful to have access to plugins within Figma Sites, particularly for accessibility checks and other quality assurance workflows. Figma Make Integration Figma Make does not seem to work properly within Figma Sites, especially when it comes to responsive layouts and responsiveness-related adjustments. Styles Management At the moment, I am unable to create, edit, or delete styles in a Figma Site file that I created myself. Interestingly, another Figma Site file that is already live works as expected, so the issue appears to be specific to this file. Are ther

The setup docs for Code Connect UI show the GitHub Install & Authorize flow, but they do not explain why the app requests repository write permissions such as administration, code, checks, and pull requests. Please document what each permission is used for, whether any repository settings are modified, and which permissions are required for specific features versus GitHub’s standard app authorization model.

Annotations are great for elaborating on designs. However, usually when I’m presenting designs to stakeholders, I hide the UI (“presentation mode”). But this also hides the annotations, which is a shame. Would it be possible to leave the annotations visible when hiding the UI?

Why did my design files disappear by themselves and I can't find them?

Senior engineer, 6 years in. I can read a codebase faster than I can read a Figma file.Every Design - Dev handoff is a different puzzle and you're the one solving it on the clock. Here's what's started bothering me more recently — it's not just a me problem anymore.My AI agent can't read Figma either.I've been using Claude for few months. It's fast, it's good, and it's completely blind to design intent. I paste in a component description and it hallucinates spacing. I give it a screenshot and it gets the layout roughly right but the tokens wrong. There's no file format that bridges "what the designer built" and "what the agent needs to implement it."What I actually want when I pick up a ticket:— A file that tells me the flex direction, gap, padding, and alignment of every layer. Not a screenshot. A structured file.— Token names, not hex values. color/background/primary not #6750A4. My codebase uses tokens. My agent should use tokens.— A u/theme{} block for Tailwind v4 I can drop straig

Hello,Have raised multiple tickets and having an enterprise paid subscription. Support is quite poor in responses with closure of tickets with no responses either. What’s the point of an enterprise subscription if we aren’t able to reach support?  

I’m working with Figma Buzz to create some social media post templates. My template includes an image nested within a mask. I would like to allow the rest of my team to use these buzz templates and provide them with a simple way to place images in the desired space.Using slots works almost perfectly in that it enables me to designate the frame within a mask as a slot and placing the image involves a simple drag-and-drop into the slot. With all other layers locked, this makes my template very easy to use.However, having the slot frame not locked makes it easy to accidentally move the slot altogether, which in turn ruins the layout of my template. Locking the slot prevents it both from being moved, but it also prevents the drag-and-drop functionality from working. QuestionIs there a way to lock the position of a slot frame without disabling the drag-and-drop functionality? Feedback on SlotsIdeally, slots nested within other frames/groups would work with the layer locking feature using a

Now that Figma is officially available and expanding in India, I’ve been wondering:Why are subscriptions still not localized for Indian users?Currently:pricing is shown in USD many local payment methods are unsupported international card payments don’t work smoothly for everyone currency conversion + taxes make subscriptions more expensive and confusingFor a lot of students, freelancers, and early-stage designers in India, this becomes a major barrier even if they genuinely want to pay for Figma.Why this mattersIndia has one of the fastest-growing design and tech communities:thousands of new designers every year startups heavily adopting Figma huge student creator ecosystem increasing use of AI + collaborative design toolsA lot of people want to purchase Figma subscriptions legitimately, but the payment experience still feels built primarily for international users.Things that could improve the experience1. INR pricingShowing plans directly in Indian Rupees would make pricing clearer a

Has there been any consideration to changing how API rate limits are applied? Here is our situation, which seems like a pretty common one:We are a software dev shop. We have a Figma Professional Plan for our organization, Full seat licenses for our developers. We rely heavily on the Figma API for connecting our tooling (AI coding tools, etc) and pulling directly from Figma files. The rate limits are perfectly sufficient for how we usually work with one HUGE caveat…We work with a design shop outside our company. They have their own Figma org, Pro Plan, and Full seat licenses. Projects usually start with them creating Figma designs. They share these files with us, but they live in their org. If we access the files directly, we hit API rate limits almost immediately because we only have guest access to these files.The main work-around we have now is to make a copy of the Figma file into our org. Then we can access it with the API limits under our licenses. But this defeats the entire purp

Took me a minute this morning to find the new placement of the publish button for figma make prototypes. This is an action I am frequently doing as I push changes/updates to those who have access to the designs. I liked the old placement of this much better which wasn't buried two levels deep. With this latest change, putting it under the share button > publish > 1st line item - it is less clicks to change the URL of the prototype which is share button > ‘update’ icon, which is an action I would never want to do. If anything updating the URL of the prototype should be several levels deep; not publishing changes. 

After a late switch from Sketch to Figma about six months ago, here is my conclusion regarding the UX of Figma:While Figma has many great features that Sketch does not have (dev mode, way more capable prototyping, variables,…) the general UX of the tool is just sooo bad! Here are the things that annoy me most:Visibility of functions: There are so many functions hidden below a small icon that has no label. Much stuff is hard to find. And what drives me really nuts: When a function is not available, then its UI element (or entry in context menu) is hidden – not disabled! I’m using Figma for UX Design, and it just feels so wrong to use this tool that does not handle UX basics correctly itself.   Library management – publishing components: You can do this from the book button on the top left where you usually update components from other files, but publishing is mixed in here if you click on “This file”. But then you can only publish all changes. If you want to publish only a few changes,

Hi Figma team and community,I'd like to suggest reverting (or making optional) the loading animation behavior during AI image generation.Current behavior: When generating an image with AI, the Frame displays a dark blue gradient animation while waiting. This completely covers the canvas area and blocks visibility of all layers above the image layer.Previous behavior: The loading state used to show a transparent checkered background, which allowed me to continue editing other layers and making layout adjustments while the image was being generated in the background.Why this matters: The dark blue animation blocks the entire work area during generation It's no longer possible to edit or inspect layers above the image while waiting This interrupts the design workflow, especially for longer generation times Suggested fix: Revert the loading animation back to transparent, or Add a user preference to choose between the two behaviors Thank you for considering this!

When I open the plugin, a connection error is displayed, and registration/login is unavailable.Help me!

Dear Figma official team,Hello!We are a formal enterprise located in Chinese mainland, and we intend to purchase your Figma enterprise version service. Now we consult you about invoice related issues:Can your company issue formal valid invoices for enterprises in Chinese mainland? What types of invoices can be provided? Can it be used for domestic enterprise financial reimbursement and account entry? What are the specific steps and requirements to apply for invoices after payment? Can the invoice be issued with our full Chinese company name and complete enterprise information as the invoice title?Please tell us the relevant detailed rules of invoice issuance, so that we can complete the subsequent payment and financial procedures.Looking forward to your reply, thank you very much!Best regardsYour nameCompany nameContact information

This is really strange to me. I have a “Team”, apparent only from the URL, none of the UI elements show whether or not I’m dealing with an organization or a team. This team has members, whom I pay for, and the seats are set up for each one of them. They are all listed under the URL “…..team/<id>/team-admin-console/members...”, and show up properly.When I access “...team/<id>/all-projects….” and press the small down-arrow next to the Team name, and select “show members”, only my account is visible.The experience is this: all of the people in the team(shown under the team-admin-console) need to be manually approved/invited to each file for editing, even though they have been invited and accepted into the team.According to the documentation: “For example: if you invite someone to a team, they’ll have access to the projects and files in that team, based on the permissions you give them (can view or can edit). If you invite someone to a specific file, but not the team, they get

This is so annoying! Each month I need to search for the invoice in your unfriendly interface. Seriously now! Better unsubscribe the service than getting such frustration.

Can Figma generate Flutter source code?  Yes — with the help of plugins and AI-powered tools, Figma designs can now be converted into Flutter code much faster. It helps developers speed up UI building, reduce repetitive work, and turn design concepts into functional mobile app layouts more efficiently.

I spend far too much time deleting that blurb when all I want to do is point Claude to the correct URL from the MCP. I have better prompts.Either make that bit go away, or let me copy just the URL.

Are customer inquiries or bug report requests originally this easily ignored?Is it because I can't speak English and translate it?Simple inquiries come in response, but reports and handling of bugs are ignored without reply, even though only manual answers are provided and additional answers are continuously requested.Is it always like that? I've raised the issue in Figma Make where I keep going back to the previous version of work and keep using credits repeatedly, and I've sent 3 additional requests for answers since the last message 22 days ago saying I'll look closely, but I'm being ignored.

Figma has been a pain in a**. The entire Figma feels shit. Figma never fails to disappoint me everyday. If you are giving big a** boxes then it should be entirely clickable why do I’ve to stick my cursor to text. It happens everywhere in layers, design panel, variables. For each select I’ve to press at least 3 times then it selects fully and that too when I hit that small clickable text area. Everything is so irritating. And after making components why the hell does it need to add useless “State=” word in it. I cant even batch rename it. The rename box should be expandable so I can see the entire name if its big. The color picker should’ve pin feature. Thousand time I’ve to click that color to open it. And in variable when we are adding colors it comes in the way of variables.  If I’ve created H1 regular Text Style and want to create H2 Regular Text Style, the duplicate option adds the same style inside the H1, it should create some H1’ or H2. Cause only two change are needed, and I’ve

I have noticed a regression on text property function in components. In the past, I was able to apply different text colors across variants, but this is no longer working. The text property now overrides styling in a way that prevents variant-specific color adjustments. In another case, the text property does not properly handle different variant states. For example, when creating an accordion component with open and closed states, the text property does not adapt correctly even though the text layer on the header remains the same. This limits the ability to manage dynamic components effectively and requires manual text update when designing variation of screen sizes and states. The text property was introduced to simplify updating text across multiple variants, but the current behaviour makes this workflow more difficult. At its core, this feature should allow users to update text values regardless of styling or variant differences, as long as the text layer is assigned to the propert

I’ve found slots incredibly buggy right now unfortunately. I love the idea, but they’ve been rather frustrating lately.I’ve had two bugs that seem related I have repeatedly had, but am unable to set up a test file for these. Slot sizes not adjustingSomething like this hierarchy. Despite the fact the two components are bound in an autolayout with gutter, it doesn’t seem to paint properly. I often have to double click the children components individually.Component >↪ Slot↪↪  Rows [Autolayout]↪↪↪ Row [Autolayout]↪↪↪↪ [Component]↪↪↪↪ [Component] Slot content not refreshingSometimes a colleague uses my account on their computer to check something. When checking an instance of a component with a slot, sometimes they see the default content and not the content I’ve put in there. Despite it being saved. I have found no solution for this except detaching the instance. 

The Problem: When using the Auto Layout grid feature (e.g., creating a 3x3 product card layout), the actual dimensions of nested objects like buttons or text layers are hidden in Design mode. To see the exact width or height, you are forced to hover over the resizing dropdowns in the right sidebar.When a nested element is set to Hug or Fill, its absolute W and H values disappear from the right sidebar entirely, leaving only the X and Y coordinates visible. Furthermore, the dimension tooltip does not appear under the object on the canvas.Why this is an issue: It disrupts the workflow and feels inconsistent. The dimensions of the parent grid container are clearly displayed right below the bounding box on the canvas when selected, but for any item nested inside, this information is completely hidden. It would be much more convenient if the actual rendered dimensions of "Hug" and "Fill" elements remained visible at a glance.Here I can see sizes:Here cannot:  

Before: you could type a text style in the search and if it was the only result, hitting Enter would just apply it to the selected element. This still works fine for color styles/variables by the way.Now: you have to search, arrow down to select it, then hit Enter, even when there's literally only one result.Completely unnecessary extra step that breaks learned workflows.Please revert.