Share Your Feedback

Hi Figma Support Team,I’d like to share some feedback about the process of handing off a Figma file from a designer to a client.I’m a freelance designer, and I recently tried to transfer a completed Figma file to my client. In the sharing settings, the client is now shown as the owner of the file, and I have removed myself from the file access list. However, I still seem to have admin/editor access from my side, while the client, who is listed as the owner, cannot edit the file.The only request I can see from the client is a Full seat request inside my personal team. As I understand it, approving this would add the client as a paid seat to my workspace. That is not the result I need for a client handoff. I don’t want to add the client to my team. I want to hand off the file so they can own and edit it on their side.I also read that one possible flow is for the client to create their own workspace/team, invite me to it, and then have the file moved there. In practice, this feels too com

Please move AI the last in the list, personaly, I use the most often the Layers and the Assets. Now I have to make a jump.  

We've noticed several recurring issues after the latest Figma update, specifically within the update panel and related components. These bugs are affecting our daily workflow and reducing productivity for our team.Issues observed:Components in the update panel are not displaying correctly (misaligned, missing, or broken states) Certain component variants appear to reset or lose their properties after the update The update panel UI itself has rendering glitches (overlapping elements, incorrect spacing) Some interactive component states (hover, focus) are behaving inconsistentlyImpact:These small but frequent bugs interrupt design work and reduce confidence in the tool's reliability, especially when working with shared component libraries.Request:We kindly ask the Figma team to review the update panel and the associated component behavior introduced in the latest release, and to prioritize a fix/patch update as soon as possible to ensure a smooth experience for all users.Thank you for yo

Minor thing, but I noticed that I can only open the Check Designs settings if issues are found.Selection with issues:Selection with no issues: I think you could just keep the entire menu. I don’t mind seeing little 0s next to each category when it doesn’t find any issues. Regardless, the settings option should definitely show at all times when opening Check Designs.

Having the same amount of text on the layer as in the layout text box seems like a waste of resources. Perhaps just the first 30 characters would be enough..? 

There has been a new update that moved the publish button inside the assets tab. I work mostly in the files tab, where all the pages are and am used to publishing from that. Now it's been buried inside assets tab which I hardly even look when in the library file itself. Can the publish button just be in a place that it's visible at all times?  

Hello everyone at Figma, could you please fix very small alignment/sizing issue? because it just might make me blind.Thank you in advance.

I’ve noticed a usability issue in Figma around discovering updates/published files . Currently it’s difficult to tell whether anything has been updated or need to be published. There’s no immediate visual indication in the left panel, and users must actively open the Assets panel to check if updates are available.This makes updates easy to miss and adds unnecessary friction.Suggested improvement:Introduce a small notification indicator (e.g. a dot or badge) on the relevant menu item. This would give users an at-a-glance signal that something has changed and needs attention, without requiring extra clicks or manual checking. Thank you!

I know UI change takes time to get used to, but I am desperately missing the previous Files/Assets setup in the lefthand nav (pictured below). There is an agent trigger on every single frame on my workspace...I really don’t need a dedicated lefthand nav option for it as well. I don’t need Agents often enough to justify it being the second item in my lefthand nav, in addition to being on every single frame. What I do need, multiple times a day, every single day, is my assets panel.  

 I ran into a font issue while working with MCP use_figma and wanted to share it here. I have a font installed on my system (Pretendard) that works perfectly fine in the Figma UI — it shows up as "Installed by you" in the font picker. However, it's completely invisible to the Plugin API when running through MCP use_figma. listAvailableFontsAsync() returns around 7,600 fonts, but none of them are locally installed ones. It seems to only return Google Fonts.loadFontAsync() also fails, and trying to appendChild a component instance that contains text using the font throws a font load error — even into a non-auto-layout frame. Steps to Reproduce 1. Install a local font on your system (I tried both ~/Library/Fonts/ and /Library/Fonts/ on macOS) 2. Confirm the font shows up normally in the Figma UI 3. Run the following via MCP use_figma: const fonts = await figma.listAvailableFontsAsync(); const result = fonts.filter(f => f.fontName.family === "Pretendard"); return result.length; // 0 awa

Imagine writing an email knowing the recipient could see every draft as you typed it. Every typo, every awkward sentence, every idea you abandoned before finding the right words. How would that feel?Imagine sending a text message, but the other person could see every version before the final one. Not just what you chose to send, but all the thoughts you decided were better left unsaid.Imagine learning a skill where people judged you based on your first attempt instead of the finished result. Every mistake became part of the evaluation instead of part of the learning process.That is what Figma's current model feels like. It exposes the process instead of focusing on the outcome.Design is iterative by nature. Ideas are explored, tested, discarded, revisited, and refined. The rough work is not the product. It is simply how the product gets made.In almost every profession, people are judged on what they choose to present, not every imperfect step they took to get there. When the entire cre

I don’t understand why Figma AI is so restricted right now. The cost of a full seat is already on par with what many AI tools charge every month, sometimes even higher. Still, we get a handful of AI uses and then it stops working.AI should be part of the design flow, not something we have to save for special moments. If running it is that expensive, raise the seat price a little but make it unlimited for paying users.It’s frustrating when you’re in the middle of a creative session and have to think about whether you’re about to hit a limit. Figma should help us explore ideas, not ration creativity.

You should start from scratch and hire a UX designer to rebuild Figma so that it’s user friendly and not the least intuitive design program.

It is far too easy to click the preview button when zoomed out in Figma sites which is a common thing that I do with such a large site. Furthermore, once I do that, I have to wait over a minute to close it, which is quite frustrating. I don’t want it to be so easy to accidentally open the preview. When I do, I want to be able to easy go back without waiting for the page to load. 

Figma, in my humble opinion, started as a design tool that rivaled Sketch. It eventually took over the market, and now almost everyone has abandoned Sketch. Figma has become the most widely used product design tool.What has happened since then, however, seems to be a lot of sidestepping and creating offshoots that move away from what the product was originally intended for.FigJam — why? Users are already using Miro and other tools that do this better. FigJam feels oversimplified, and in the end, I just use Figma itself to run workshops. Assuming that people who don't use Figma are going to come in and adopt FigJam is a mistake. Most people who don't use Figma don't enjoy using it.Slides — why? Most businesses are still using PowerPoint. It doesn't matter how much you push Figma Slides; it almost always ends up back in PowerPoint. This feels like a major departure from what Figma is supposed to be.Coding? What in the world? There are already so many tools out there that write code. Why

Just going to complain because who ever is behind the wheel at Figma, from a product experience point of view, is not thinking about good UX and is instead just making things harder for users. You used to be able to open a plug-in, then save it for easy access. There are many versions of the same plugins, even paid ones and I would like to be able to quickly jump to those especially after trying a few that aren't what I need. Instead I have click about 2 to 3 times, then enter text to search for it, then use it, then wonder where it went or even have a hard time finding it again. Now the ones I paid for are hard to find too - these are ones Im paying for and should be easily accessible. Please, make it easier to jump to a list of plugins users use often or have paid for 

I can’t use the site design feature without clicking a “get started” button with fine print that does not clearly state the breadth of the privacies waived. So much for free.

When using the AI image generation/editing feature, the "Cancel" operation is bound to the ESC key. Since I often perform other operations (like switching windows, using shortcuts for other tasks) while waiting for or working on edits, I frequently press ESC accidentally. This immediately cancels the ongoing process, interrupts my workflow, and even causes me to lose unsaved progress. It’s very frustrating to restart the entire generation/editing process repeatedly due to unintended key presses. I hope the team can optimize this interaction: 1. Remove the ESC key binding for Cancel, or 2. Add a confirmation prompt before canceling the task, or 3. Change the shortcut to a less commonly used key combination to avoid accidental triggers. Thank you for your attention!

It’s very inconvenient and slows things down when you add an additional fill with 20% opacity. You have to go into the opacity settings every time and set it to 100%.

I’ts so freaking annoying that you can’t collapse the assets panel! 

Hey everyone,This has been driving me (and apparently hundreds of others) crazy since 2021: there is STILL no native way to properly move or duplicate an entire page from one Figma file to another.Copy-paste or “Select All” destroys page background/grid/rulers, breaks prototypes, loses comments, turns library styles into local duplicates, and forgets locked/hidden layers. Duplicating the whole file then deleting pages is the only “workaround” — but it’s a nightmare with 50+ page files or design systems.I’m a fellow designer who’s fed up and seriously considering building a free Figma plugin called PagePort that would let you:Export any page (or batch multiple pages) with 100% fidelity (layers, auto-layout, constraints, page props, prototypes where possible) Import into any other open file in one click Choose Move (delete from source) or Copy Smart remapping for styles/variables/libraries + basic prototype reconnection Progress bar for large pagesWould this solve the problem for you? Wh

The system is showing that AI credits are still available, but AI features remain unavailable and display an “out of daily AI credit” message. This creates a mismatch between the user’s remaining credit balance and the access state shown in the product.  

I last used Figma make a month ago, and whatever change was made to the default LLM made it unusable. The default selection picks an LLM that can’t produce even the most basic protoype and is unable to follow instructions. It was a powerful tool that I highly recommended but I’d be embarrassed if someone tried to use it with the current default LLM. A lower token cost doesn’t matter when the tokens are wasted by failed outputs. 

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