Share Your Feedback

Is Figma ever going to allow us to collapse/expand pages in the sidebar? What about text-wrapping layer names?

I just used up 300 credits for it to try to use the fast apply tool and fail and then tell me to do it manually - This was just a find and replace of a field name across a few data files. With the 3000 monthly cap - ill get 2 days worth of work.  

Figma, Auto jump to next comments when previous comment is resolved is frustrating to use. Most of the times when we resolve a comments we tend to look and ponder on screen if we want to add any new comments. When it auto-jumps we need to search for the section again which is really bad experience. Please look into this. 

Artificial intelligence is no longer limited to simple automation or rule-based systems. Today, intelligent systems can observe, decide, and act on their own. This is where the concept of an AI agent comes in. Understanding the AI agent definition helps businesses, developers, and marketers see how modern AI systems actually operate in real-world environments.AI Agent Definition Explained SimplyAn AI agent is an intelligent system that can perceive its environment, make decisions based on that information, and take actions to achieve specific goals. Unlike traditional software that follows fixed instructions, an AI agent can adapt, learn, and respond dynamically.In simple terms, the AI agent definition refers to a system that: Observes data or surroundings Analyzes situations Takes actions independently Improves performance over time AI agents are widely used

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

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.

   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.

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

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

I often work with Figma files that look great visually, but SEO performance sometimes drops after development.What best practices do you follow to ensure proper heading structure, clean HTML, fast load speed, and SEO-friendly layouts when converting Figma designs into live websites?I’ve been documenting my workflow for SEO-friendly development here:Rupak ChaulagainWould love to hear how others handle this during handoff and development.

I believe that previously, comments sent to a file were notified on the desktop and in the Slack app, even when the file was open.However, recently, it seems that notifications are no longer received when the file is kept open. (Apologies if I'm mistaken.)When a tab for another file is open, notifications appear to be delivered normally.I often operate other browser apps while keeping the tab for the file I want to receive notifications for open in the desktop app, so in such cases, I often don't notice the notifications even if the file remains open.I would like you to consider either allowing notifications to be received even when the file is active on the tab, as before, or providing such an option.

One of the things I used to love about Figma was collaboration. I have a paid Professional plan and my partner has another Professional plan. The thing is that we cannot collaborate in a same file. If I want to do that I have to paid another seat for her inside my team which is ridiculous because she is already paying for Figma.With that beeing said, the first time I fell into the trap and added her to my project. Nothing in the UI told me that I was going to be charged with another full seat (really bad UX and dark pattern from you Figma). There is only a button saying ‘Approve’, that’s it! I lost almost $80 because I added several friends to that single file. Figma, you robbered me.So, Figma, you are losing us, I saw this several years ago with Sketch and the community choose Figma. Now I’m open to explore other tools that allows me to work collaborative with other paid members (I’m not saying that I don’t want to pay).I used to love you, you changed! :(

Is it possible to obtain a free subscription to the Professional package for non-profit organizations, and what evidence is required for this? Thank you for your response!

Its just confusing that we have a +1 that is not interactive and a very similar one that you can press and increment it. Would be nice to differentiate the interactive because people often just put the non-interactive one that is not desired

When working with both Design view and Figma Make view, editing local components becomes difficult and noticeably slow in Design view especially while typing or making text-level edits.If I’m exploring or generating an idea in Figma Make and then switching to Design view to refine it or prepare a handoff, working inside the same local component across both views feels friction-heavy. Text input and real-time edits lag significantly, which disrupts the flow of iteration. Performance drops and context switching makes it hard to work efficiently.This becomes especially challenging during handoff, when ideas generated in Make need to be quickly refined, adjusted, or structured in Design. The slowdown during typing inside shared local components makes even small refinements feel cumbersome and breaks momentum.Suggestion / opportunity:A smoother interaction between Design and Make when editing l

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.

Its beyond frustrating that to view annotations you have to have a Figma license. People like BA’s and PO’s just need to see annotations but do not need to edit or review the files merely look at the designs and see the annotations to get an idea of the functionality. Our organisation has many licenses as we have a large team of designers and developers all who have licenses. The annotations feature should be made viewable to people you share a file with without having to purchase a license. To get around this we have created an annotations component but the built in one is so much easier to use. Figma please make the new annotations feature viewable to all. I understand the licensing aspect for editing etc but to view an annotation makes no sense that you would need to purchase another license so someone can view a note.  

hi, im encountering condition where my file in figma make get warning of high memory usage, and it seems not because the amount of code that generated, i think it’s the cause is the chat is to heavy. any idea why this is happening?if the chat is the cause, i think add a chat deletion feature will be helpful, thanks

I’m building a stable prototype with Figma Make, and the credit model is a practical blocker. I’m already at ~500 prompts/executions on this project. Figma’s own positioning puts 3,000 credits/month at ~50–70 Make prompts (~43–60 credits per prompt on average). If my workflow needs ~500 prompts, that’s ~21,500–30,000 credits, or ~7–10 months of the included allowance. I’ve also seen 4,250 credits disappear without reaching a usable prototype outcome. The main problem is that because Make is agentic, the cost isn't fixed per prompt and you can't accurately predict it before running. What the agent chooses to do (actions, files, iterations, model) determines billing. Because you can't confidently plan or iterate, it's a budget black box.Make only seems feasible for small demos at the moment, or if you manage to iterate with almost no reruns. Sometimes it is not enough even for a small prototyp

Hello, good day.I’m experiencing serious issues with the new Figma UI update. Many essential tools — such as padding controls — are missing or hidden.Please do not enforce this new version. The previous UI was much better, clearer, and far more efficient for designers.This new version has no advantages, feels confusing, and makes our workflow significantly harder.

This is a regression in Crop behavior.Previously, it was possible to adapt a 16:9 image to a fixed 1:1 (768×768) exportby symmetrically pulling the left and right crop edges toward the center.The content itself was not edited, only the visible area was adjusted.This workflow exported a correct 768×768 image without empty paddingand without cutting important text.Currently, Crop enforces strict aspect ratio behavior.When adapting 16:9 → 1:1:– using Fill crops important content– using Fit / Scale results in empty bands (letterboxing)This removes a previously available and widely used workflowfor preparing fixed-size marketing assets where content cannot be modified.This is not a design request but a regression.There is currently no way to reproduce the previous behaviorusing Crop, Mask, Frame + Clip content, or Image Fill.Please consider restoring the previous Crop behavioror providing

SVG is often treated as a simple export format — click “Export as SVG” and move on.In reality, SVG quality depends heavily on how the vector is generated, especially when starting from raster images like PNG or JPG.Over the last months, while working on SVG conversion workflows, I noticed a few recurring issues that designers and developers run into.1. Why raster-to-SVG conversions often look badMost automatic converters try to trace everything: noise gradients shadows anti-aliased edges This results in: overly complex paths huge file sizes SVGs that are hard to edit in Figma The key insight: clean input matters more than the tracing algorithm itself.2. Pre-processing before vectorizationBefore converting to SVG, it helps to: