Share Your Feedback

With the strict enforcement of AI credit limits starting March 18, I’ve been looking at our organization's options for scaling usage. The current pricing structure for additional credits vs. adding new seats seems completely disconnected from reality for power users.Let’s look at the numbers for a Professional Plan (2026 pricing):Option A: Add a Full Seat. Cost: $16/mo. Cost/credit: ~$0.005 Cost for 3,000 credits: $16 Option B: Pay-As-You-Go (Overage). Cost/credit: $0.03 Cost for 3,000 credits: $90 Option C: Shared Credit Subscription. ​​​​​ Cost: $150/mo for 5,000 credits. Cost/credit: $0.03 Cost for 3,000 credits: ~$90

If you try to paste a component into FigJam, you can't set it as a thumbnail. You have to detach the component in Figma first, and then paste it into the FigJam. Then you can set it as a thumbnail.In the same way, if you add a library to a FigJam file (like for stickers) and use one of those, you can't set that as a thumbnail, even though the use case of making covers for clients or projects and being able to just drag and place those in FigJam is probably pretty common. I don't know why you can't set it, but it seems like that would be an easy thing to do. This ticket was closed after everybody gave up… but this seems straightfoward. 

I propose adding a contextual "Play" button directly on the selected frame's label, right next to the Dev Mode icon This simple addition would keep the workflow focused on the canvas and significantly speed up quick iterations. Maybe?

IMO in Dev Mode, the “Explore component behavior” button should be a primary button because nobody has seen this button while it could enormously helps a lot for the development Also, in the component behavior view, you should suggest the component behavior of the nested components

I keep punching in the same preferences for how files should be displayed in home/project/org view. It would be good to have a json or something that can just save the config. its kinda rediculous how unintuative the files and folders are set up, I get where this is comming from and what its aiming for, but at least offer option for a more intuative folders structure, easy renaming, maybe alias files, drag and drop/force open paths… cream if simply cli shell input somewhere, I mean what are we even doing? what legacy are you preserving with the lagged ‘starred files’ sidebar and million folders that can only have one parent and no children? I would even just opt out of your egosystem with the figma files intact… if that were possible. maybe you are working on the next big thing and this is just backseat driving, regardless, this has bugged be the fuck out since it launched and twise more with updates that made it even worse (you could at least in the beginning double click on folder

The design of websites using AI in Figma Site is quite ambiguous. While designing React applications with AI is relatively smooth through Figma Make, it remains complex and unclear on Figma Site.

I tried making an AI called “Flow” by having the AI design the basic UI and the basic code and asked it to be inspired off of CluadeAI. I asked the AI multiple times, and it kept on pointing out its mistakes over and over again. This was very poor work and I was kind of angry and frustrated that Figma markets it so well but then asks you for credits. Here is a screenshot I sent it.Screenshot that I sent to it as a base to use for the UI.And- here is what it made. Also note: this was made when my credits were about to end. What the AI made.Not only is this a copyright violation, it is horrible.

In my opinion, I think the position of "publish" isn't intuitive. Its new position is on the bottom of the left side bar, which is easy to ignore.

I have the preference “Use Scroll Wheel Zoom” enabled, and love that this option was added. But unfortunatly, it is very frustrating with the workflow.I use my mouse wheel to zoom in and out, and then click and hold my mouse wheel to pan around. This is just what I am used to in other software.My mouse wheel can also be pushed left and right for horizontal scrolling. If I accidently move the wheel left or right while clicking to pan, then Figma will switch to a “scrolling” mode. Now when I try and use my mouse wheel to zoom, it will scroll vertically instead until I do a single mouse wheel click.It would be great if “Use Scroll Wheel Zoom” was enabled, then horizontal mouse wheel scrolling would also be disabled. Or at least don’t switch it to a scrolling mode

The Issue: There is a UX "trap" when using the search filter within the Comments panel. If a search term is active, any new comments added to the canvas that don't match that term are immediately hidden. This creates the false impression that comments are not being saved or that there is a sync/connection error.The Experience: I searched for a specific term in the Comments panel during a meeting. Later, I began adding new comments to the canvas. Because my previous search was still active (but the panel was not my primary focus), every new comment I typed vanished instantly upon hitting "Post." Since I was focused on the canvas and not the right-hand panel, I didn't realize a filter was still applied. I spent several minutes troubleshooting my internet connection before realizing the search term was simply filtering out my new comments. Proposed Solutions:

I don’t know if positive feedback is allowed, but whoever made it possible to copy tables from excel to figma and make them editable? Yeah, they deserve a hug, a cookie, and a raise. 

Please before inserting new features resolve core issues:Optimising rendering of pages Optimising rendering of instances Optimising overall speed of platformDo not get me wrong, new features are always nice, but speed and efficiency of the application is the most important and Figma is becoming increasingly problematic in such things.As an example in December could not use the platform for a week because instances were constantly badly rendered and no workaround was possible. Today cannot use some files because interacting with them is impossible due to extremely low speed.If features are implemented but the usage of the application becomes more and more problematic in terms of performance, then what is the point of implementing new features?

[Problem ] I work at a creative agency and frequently switch between my company's organization and multiple client organizations within Figma.The biggest issue I face is accidentally creating a new file in a client’s workspace when it was intended for our internal use or for another client. This is a significant security risk.Because the Figma UI allows users to create files instantly via the "+" tab or shortcuts, it is very easy to lose track of which organization is currently "active." If I am working on a client file in one tab and decide to start a new internal draft, Figma often defaults the new file's location to that client's organization. Currently, there is nothing to prevent this. [What I am looking for]We are currently considering the following manual workarounds to mitigate this risk: Separating Windows: Opening each client’s project in a completely sep

In order for the component interactions I create in my design library to work in a file, I have to literally copy and paste the main component into the file I am working in. If I insert an instance, the interactions disappear. Am I missing something? Is this a feature on the way?  Current workflow: Insert instance → realize connections I set up aren’t working → open UI library file, find component → copy it → Return to other file → paste it.  Desired workflow: Insert instance. 

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 noticed that when I select images in Design mode, a new floating menu shows up above my toolbar with image-specific actions (see screenshot for reference). Some may find these options helpful, and more power to them, but they are not relevant for my workflow. The menu takes up a lot of space and feels a bit distracting to me, so I was wondering if there could just be a straightforward option via preferences to turn it off?Alternatively, is there a world where these options just live inside of the image fill options panel? I seem to remember them being there at one point, and that intuitively makes more sense to me, since it is where all the other raster-based editing options are.

I’m getting absolutely mad. Files with only 6 frames of 5 layers each, only 1 image each: Now the mere text edition takes ages or gets the page to crash. I just can’t work anymore. Please patch this absurd ubdate urgently.

All of my icons in the design system are part of a component set. When exporting them, the file names automatically include "name=" followed by the icon name. This creates extra cleanup work, as the "name=" prefix has to be manually removed from every file.

Don't change X field value when I change a shape's height or width.This happens when the “snap to pixel grid” is checked Before:X: 10.4, Height: 10 Change the height After:X: 10, Height: 9 If I am editing field A, don’t go ahead and change the value in some other field B.  Please understand user’s use cases instead of just assuming you should add some automated guardrail behavior.  

When you import an SVG to Figma, RECT tags get converted to PATHs. Mutating tags like this makes it a nightmare to work with Figma when developing SVGs.  Please stop mutating element types.

BLOG POST: Why does Figma deliberately add friction to the account upgrade process? 🤬 So I’ve been building start-ups for over 15yrs and the holy grail of any app is to convert a non-paying user into a paying one. But Figma has gone out of its way to deliberately make upgrading your account harder than it needs to be and violates every principle of UX in the process. The Problem:To use Dev Mode in Figma you must have a Full or Dev account. When I click the button to access Dev Mode I get a dialog that pops up that says “Upgrade to work in Dev Mode” and a button that says “Learn More” and a secondary button that says “Back to Design Mode”. Now if you’ve used the internet ever, you’d assume that the “Learn More” button will put you into a user flow where you can enter your billing info and access the premium feature you had just tried to access. But no, the geniuses at Figma have decided that this page should link to a sup

   AI’m going to have a really big problem when my AI points are being eaten up because of FIGMA stupidity… I asked it to create sql update files, and it did mind you however it didn’t use the proper naming convention, as it reused numbers that already existed. When I pointed it out, it recreated everything with new numbers… Essentially doubling my AI usage.  Another example, I asked figma to check for the usage of a background photo and was told NO, the rework and doubling of AI point usage is getting ridiculous. This is just 2 hours with of reasons why this is going to be a horrible change.  

I created a duplicate Project and wanted to delete it. I used the context menu and saw three options; Project context menuI was looking for either Delete or Move to trash. I would never have guess this would be under settings until my colleague mentioned it to me. Even a google search didn’t give me the right suggestions.Maybe adding an option for Delete to the context menu or having a different label for Settings could help with better findability.

Is there a way to stop options in the right panel from hiding all the time, it’s really infuriating. Like when I’m in the scale tool, I can’t change variants and various other things get hidden. I hate it so much. I also hate hunting for my tools that move all the time. The new UI is so terrible I can’t believe it’s in an actual UX design program.

While working with text styles, I noticed an inconsistency between the Styles view/edit panel and the UI used when applying text styles to text.The Styles view/edit panel has a strong visual hierarchy: Clear grouping (e.g., body → size → variant) Nested structure that is easy to scan Logical ordering that helps designers understand relationships between styles However, when applying text styles, this hierarchy is flattened. The lack of grouping makes it harder to: Quickly scan available styles Understand size and variant relationships Confidently choose the correct style, especially in large design systems SuggestionConsider using the same hierarchical structure from the Styles view/edit panel in the Apply text style