Share Your Feedback

Changing the Variables panel to be a tab along the side that takes over the view instead of a panel I can move around has impacted by design flow. I would often have the variables panel open side-by-side to my designs so I can view/add/update variables and build design simultaneously. Now I have to flip back and forth causing frustration and slower process.

The recent figma autolayout update has brought up conflicting emotions. From one point it’s great that the autolayout would work closer to code, but on the other hand for teams that do more complex projects than Web UI, this creates a loooot of issues. 3 things in particular, that I know for sure, will break what we've been using in case of complex layouts:"Padding now always gets the room it needs" - Often when necessary, I relied on the fact that you can set auto-layout frame size to 0 and add paddings inside to allow precise position of elements without affecting the size and position parent and sibling frames. Now that won't be possible. ⁠"Inside strokes counting in autolayout" - again pretty sure this will break layouts where inside stroke was used. ⁠"Stacks with gap set to auto no longer overlap" - A lot of cases it's better to have parent in the desired size than have the parent rely on the children. Then we will get uneven distances and paddings in some cases. All of this would

I’ve been thinking about how much difference good file organization can make when working on a design project.For example, how do you usually organize your Figma files and pages? Do you have a specific naming system for layers, components, and sections, or do you keep things more flexible?I’d be interested to hear what organization habits other designers have found useful, especially when multiple people need to work on the same file.

Hello! I noticed that in the Figma article What is Human Computer Interaction?, the author writes:Dialogue. Use clear and concise language to communicate task completion, like  “Purchase Confirmed” pop-ups after completing an online order. On Shneiderman’s website, he writes: Design dialogs to yield closure.Sequences of actions should be organized into groups with a beginning, middle, and end. Informative feedback at the completion of a group of actions gives users the satisfaction of accomplishment, a sense of relief, a signal to drop contingency plans from their minds, and an indicator to prepare for the next group of actions. For example, e-commerce websites move users from selecting products to the checkout, ending with a clear confirmation page that completes the transaction. I understand that they are variations of the same word but I would argue that in this context, it is important to use dialog because Schneiderman is referring to the importance of the graphical interface  (li

Looking to better understand gradient behavior in Figma.The example below shows a setup for a Skeleton loading layout/animation. The gradient sits above a background layer with a light grey color.skeleton reference I want the gradient to provide a small white highlight wave, animated across the background layer. It has stops of 0%, 24%, 48%, and 100%. Three of the stops are fully transparent (to match the CSS). Even when set to fully transparent (#00000000), a fill color is present in the transitional areas. This should transition from white to transparent.Currently, Figma requires setting the transparent color to match intended visual styling, here requiring setting the transparency to match the background layer. This feels like an unexpected setup step, and clunky.Is this intended? How does this align to CSS?  

On the vertical bar on the left (as per screenshot) how can I swap the 'Agent' button to the 'Assets' one so it's under 'File' instead?    

Hi, and apologies for posting a new question – it may well have been asked before. To be honest, I can’t be bothered to look it up. Besides, the more questions on a single topic, the better the chances of success.I’m not really sure how or what to write here, so I’ll just set out my ideas and suggestions – things I keep coming back to whilst working in Figma.Feature request: Responsive Component Swap Based on Container WidthIt would be extremely useful to have a way to automatically switch a component variant or nested component based on the width of its parent frame or container.When designing responsive interfaces, components often need to change significantly between desktop, tablet, and mobile layouts. Auto Layout handles resizing well, but sometimes resizing is not enough — the component itself needs to change.For example: Width > 1200px → Desktop Navigation Width 768–1200px → Tablet Navigation Width < 768px → Mobile Navigation Ideally, we could define breakpoint rules d

A bit meta, but found a bug in the Forum here 😅The emoji picker gets overlapped with the reply input:...also, it would be a nice-to-have feature to have a search in the picker.

 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

It is impossible to annotate a parent frame that has multiple frames in Figma. If an auto-layout frame is made up of 3 nested frames, we can press “Y” and annotate only the nested frames. We can’t click on the parent frame to annotate the entire frame. See attached screen recording for reference.Annotations are an important feature for the dev mode that Figma charges a bomb for. This simple annoyance ruins the user experience. Does anyone know an easy way to annotate the parent frame?

Por favor, parem de mudar o layout sem aviso prévio. Mudar algo que já passamos por uma curva de aprendizado e ficou estabelecido como modelo mental e de repente vocês mudam ferra o nosso lado aqui. Primeiro, foi a mudança do menu, depois a sidebar (mais de uma vez). Algumas foram boas mudanças, outras criaram fricções. 1. Eu tenho que parar o que estou fazendo no meu dia a dia para aprender um novo comportamento.2. Preciso de um segundo icon "close" que feche o painel quando eu estiver em assets, porque toda vez, cometo o erro de clicar no icon "book"e abro o ds publicados. Por que estou condicionado a clicar quando estou na aba file. Joga um posthog aí ou similar que é provável que mais usuários passam por isso. Enfim.

The Figma agent isn't reading comments. I used to use the Figma agent to change text in the layout; it was convenient when the agent would read a comment and replace the text automatically. Now, it just says there are no comments, even though there are actually plenty of comments in the frame. The agent doesn't see them—have you encountered this situation?

So this is a question and a conversation as well, in the recent update of figma where it changed it's Ai image generating model from GPT Image 2.5 to GPT Sunburst, it genuinely sucks bro. Previously GPT Image 2.5 was the best it was generating images accurately as per the prompt but now this Sunburst is annoying, and why do figma even have those nano banana models, nano banana 2 is good but why do we even have Nano banana mini? Please help I'm stressing out my self I don't wanna buy Chatgpt Plus now to generate images 

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.

It appears as though the higher resolution a Figma Motion export is, the more compression is applied, which greatly affects color reproduction. Without being able to set a consistent compression, color is constantly changing in exports, which makes the exports unreliable for evaluation and deliverables for production. If the compression is indeed adaptive, targeting a certain bandwidth cost or file size limitation, it's a big flaw in Figma motion exporting. We need a way to maintain the color space consistency in exports.

I have a shape element (a message bubble), I cannot flip it against it’s vertical axis to create a simply dialogue visual for my project. 2 people having a conversation….the message bubble has to be flipped.I don’t understand the logic of principle with building a tool like Figma that is highly precise and detailed, but then building it’s sister app “FigJam” with bare bone features.As designers, I still want the ability to manipulate elements. Why is there only 2 thick levels for lines?This type of experience makes me want to abandon FigJam entirely and make my documentation in Figma original or use a different tool like Miro.I understand and respect wanting to simplify the workspace, but believe you guys have over-optimized in this direction and consequently limiting the creative aspect of designing visual documentation for teams. 

When I’m just ideating on a new design and don’t want to use auto-layout yet, it would be really nice if there were a button that allows me to quickly move an object to butt up against another object. Something like the alignment buttons, but I don’t want to align the object to the sides of the frame. 

My Figma Learning Journey 🎨✨I’m starting my journey of learning Figma and exploring the world of UI/UX design. My goal is to understand the fundamentals of design, improve my creativity, and learn how to create clean, modern, and user-friendly interfaces.Throughout this journey, I’ll be sharing my learning experiences, design experiments, challenges, and progress with the Figma community.I’m excited to learn new skills, connect with fellow designers, get feedback, and grow as a designer one step at a time.Let’s learn, design, experiment, and grow together! 🚀#Figma #LearningJourney #UIDesign #UXDesign #DesignCommunity #FigmaCommunity

In the new UI, the color options have been changed to buttons that you click on to open the color picker:I now need multiple clicks to get to a text field that I can edit or copy the value of. The old UI (still used for Selection colors) was much more accessible: I could even paste a non-hex value into the field and it would recognise it correctly!Can we please bring back the old input or an alternative/faster/easier way to quickly edit/copy color values?

As stated in title. It’s wasteful, unnecessary and removes personal agency from the creation process. 

User StoryAs a Figma administrator, I want to access files in Trash, filter them using the available criteria, user, and previous location, and permanently delete multiple items at once, so that I can manage deleted content efficiently and keep Trash organized.Acceptance Criteria The administrator can access the Trash section from the Figma application. The administrator can view deleted files and relevant information, including file name, user, and previous location. The administrator can use the existing filtering criteria. The administrator can filter files by user. The administrator can filter files by previous location. Filters can be combined, and the list updates according to the selected criteria. The administrator can select one or multiple files from the list. The administrator can permanently delete the selected files in bulk. The administrator can permanently delete all files displayed in the filtered list. The administrator can select an option to empty t

Hello Figma Support,Please route this maintenance suggestion to the team responsible for the Figma plugin skills distributed for Codex. This concerns instruction discovery and packaging, rather than a Figma document or a demonstrated Plugin API failure.Environment: Codex desktop on macOS. Installed component: figma@openai-curated-remote, version 2.0.21. Observation date: 2026-09-14.In skills/figma-use/SKILL.md, the description at line 3 begins with mandatory prerequisite warnings and puts the actual capability and triggering objects later. In a display with limited description space, the warning is more likely to remain visible than the scope. The installed entry point has 34,998 characters and 435 lines. This is a static discovery concern, not a measured automatic-selection failure rate.Suggested English description:“Create, edit, or inspect nodes, components, variables, and layouts in Figma files using use_figma JavaScript. Read this skill’s API and execution requirements before call

Hi, where I can find the prototype mode in this new UI? and also the absolute position in auto-layout is also missing?

Hey guys, I want to share this idea.I work with different companies that, for NDA reasons, each want me to use their own email and account. So I need to switch between accounts all the time.The situation is that Figma is great software, I love it, but regarding user accounts, it's a total mess.Maybe instead of adding an account to the app and creating confusion by having multiple files open from different accounts at once, a simpler solution would be to let users open another Figma instance.That would be helpful to drag and drop between windows and share some components between different projects.

It would be helpful if the playhead snapped to time increments as well as existing keyframes. Right now, it’s difficult to position the playhead precisely when editing because it’s not clear whether it’s aligned with the intended time.