Share Your Thoughts

I think Figma's Brush tool has a lot of potential, but currently feels quite limited compared to dedicated painting tools.I'd love to see a more advanced Brush system that could include features such as: Adjustable brush size, hardness, opacity and flow Pressure sensitivity Stroke smoothing Spacing, scattering and rotation controls Custom brush shapes Eraser and smudge/blending tools The ability to create, save and organize personal brushes Brush presets and custom brush libraries Community Brush LibraryI think the biggest opportunity would be connecting custom brushes with the Figma Community.Designers could create their own brushes or brush packs and publish them to the Figma Community. Other users could then discover, install and use those brushes directly in their Figma projects.This could create a whole ecosystem around brushes, similar to other Community resources.For example, the community could create: Texture and grain brushes Ink and pencil brushes Pixel-art

I would like to ask: are there plans to introduce such a feature (tool) for Figma Draw as an eraser in the future? For example, it could easily erase unnecessary vector graphics down to the smallest detail. That is, I mean the eraser, which is have for example, in Adobe Photoshop and MS Paint.

Why did Figma choose to remove the type size from the panel.Not a good move. We create styles H3,H4, etc figma used to display: Body copy - 14pxNow… we have to click on style to see what the dimension. Not a good move. No one memorizes what size and line spacing H2 could be…You tried to make the panel minimal and ended up adding extra unnecessary clicks. Knowing a type size is crucial. Bring it back to surface please. 

Working in Motion I have to click back into Design to then get to Prototype but I work closly with Motion and Prototype so it would be great if I could stay in Motion and just click a Prototype button on the top to switch back and forth like I can when in Design mode. 

When presenting in Figma Slides, I would like the smart animate transition to be played even when going back to previous slide. Currently smart animate is only played when advancing to next slide, but not when going back to previous (then it’s just an instant change). This behaviour would not have to be the default, but having the option would be nice.

Hello! Is there a way where we can cherry-pick which changes made in the branch are going to be merged in the main file?

Since Figma introduced vector Pattern fill, it works pretty nice, yet there are some limitations and missing features. API/MCP supportClaude does really good work generating lots of patterns, yet it doesn’t understand well the underlying mechanism around it With further investigations, it looks like the API doesn’t support generating fill type `PATTERN`node.fills = [{ type: "PATTERN", sourceNodeId, tileType, scalingFactor, spacing, ... }] throws a discriminator validation error. PATTERN is absent from the accepted set, which currently lists SOLID, SHADER, the four gradients, IMAGE, VIDEO. Reads work fine, so the type round-trips as data but can't be written back. Even re-assigning an unmodified pattern paint read off an existing node fails. createPaintStyle() accepts the call and silently stores a SOLID instead. The silent degradation is arguably its own bug and worth mentioning separately, since it fails without erroring. clone() preserves pattern fills correctly, which shows the unde

Request: Through the Figma MCP, access contents of comments made in Figma Design file.Reason: Can provide context for designs, review bugs, etc.Current response from OpenAI Codex with direct link to comment:No, not the comment itself.What I can see from that link is the node it points to:file: XXXXXXnode: XXXXXXscreen: /sign-up-2 (iOS)That screen contains:nav title Sign UpEmail and Password inputsSign Up primary CTAContinue with AppleContinue with Googledivider OrAlready have an account? Sign inbottom legal linksBut I still cannot read the actual Figma comment thread or the #XXXXXX anchor content from this session.If you want, paste the comment text here and I can map it to this exact screen and tell you what change it implies. 

A great feature to have is text styles not breaking when a designer is using Cmd + B to bold a word or phrase. Currently it unlinks the text style and applies the bold to the underlying font. It would be great if there was a feature where when I use Cmd + B, it swaps to that text style in the library (where the style already exists) and updates in the property panel as well.

The bottom part of the icon feels too visually dense — all the elements blend together, which creates a lot of visual noise. This makes the icon hard to distinguish and difficult to find quickly among other desktop icons. I think simplifying this area or improving the separation between the elements would make the icon much more recognizable at a glance.

When I have a typography style applied, I want to be able to change to a pre-saved option as easy as I can do it for colors. Now if I detatch the typography style, I want to be able to apply another style right away. I think what can help is to show the “library” select component when clicking on the “apply styles” icon button. When I click there I expect to see Text styles I have saved. However, the ones that are shown on my image I didn’t create and the only one library added to this file is not he first option being displayed. It is so frustrating and difficult to find the ones I have save and added to the library. 

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.

So, with the new beta implementation of shaders, I had a question since, you know, typically shaders are coded (which I assume is the work that the figma agent is replacing in this case) Is there any plans to make the Figma shaders coded instead of generative?

I’m posting this as a former paying subscriber because the usability problems became frustrating enough that I cancelled my subscription.My main issue is not what Figma can do — it’s how unnecessarily difficult it is to continue existing work.I’m using Figma for an app project, and something as basic as reopening the same project, finding the correct working file, returning to Figma Make, and locating the AI prompt workspace has repeatedly been confusing.The biggest problems I’ve experienced are:Figma Design, Prototype and Figma Make feel disconnected. It is not obvious how to return to the same Make/AI workspace I was using previously. Similar project cards make it unclear which file is the real working project. Navigation changes depending on which part of Figma you are in. Important controls are hidden or difficult to discover. I regularly spend time trying to find my own project instead of working on it.A user should be able to open Figma, see their active project immediately, clic

The current seat upgrade request process does not provide users or organization admins with enough information to make informed decisions or manage temporary seat requirements efficiently.Three improvements would make the process more transparent and significantly improve license governance: Make the request explanation mandatory Users requesting a paid seat upgrade should be required to explain why they need it. The request should not be submitted if this field is empty.Ideally, the mandatory explanation would cover: The project, client, or internal initiative The functionality for which the seat is required The relevant team or responsible project lead This would give admins the business context required to assess the request and reduce the need to contact users individually for clarification. Explain seat functionality and cost implications The upgrade request interface should clearly explain what each available seat type enables before the user selects it.For every seat type, F

It seems that previously link previews were updated in slack to show what was being shared instead of the entire canvas. I missed that and now my links are just links, no preview. Which is better than previewing the entire canvas still.I have the same suggestion for link previews in Teams. Please stop showing the entire canvas in Teams previews and either show just what is being shared, or just don’t show anything.

It’s 2026, why are links (especially figma file links) being pasted as plain text? Notion and tools similar to it show a stylized container/preview by default when a link is pasted, with the option of a hyperlink or plain text link. Not having it in Figma Design is one thing, but not having it in Figjam feels especially lacking.

Organization admins currently have no direct way to send an organization-wide message to all members and guests from within Figma.For larger organizations, admins regularly need to communicate important information about topics such as: Changes to SSO, email domains, or login requirements License and seat-management updates File migration or account consolidation New governance policies, libraries, or templates Planned training sessions or administrative deadlines The current workarounds are to copy users’ email addresses from the People page and communicate through an external email tool, or to create a user group and mention it in a file comment. Neither option provides a reliable, centralized communication channel for organization administrators.It would be helpful to introduce a “Send announcement” feature within the Admin dashboard. Ideally, organization admins should be able to: Send a message to all organization users Choose between members, guests, or both Target re

I’ll be straightforward and concise here, as you’ve probably seen in the title. My idea is to have a new option for the Frame size, where it resizes to fit the device screen. The options would include ‘Resize Height Only’ , ‘Resize Width Only’ , and ‘Resize’ (which adjusts both height and width). This feature is useful for testing responsiveness across different devices and platforms (such as mobile apps and desktop). You’ll find this option in the prototyping tab alongside ‘Custom Size’ . Perhaps we could call this option ‘Auto Size’ . Resizing only the height or width is beneficial when the page has vertical or horizontal scrolling.

# Expose stable component identity for instance swap properties in parserless Code Connect ## Problem When using parserless Code Connect templates, `getInstanceSwap()` returns an `InstanceHandle`whose `symbolId` represents a file-local component node ID. The same library component can have multiple local aliases in a consuming Figma file. For example,one icon may appear under these IDs: ```text5:154       Library component ID11221:2421  Local alias12041:6322  Another local alias``` Although all three represent the same library component, Code Connect only exposes the local`symbolId`. This makes it difficult to translate an instance swap into framework-specific code: ```tsconst icon = instance.getInstanceSwap('StartIcon');const iconName = iconsBySymbolId[icon.symbolId];``` A manually generated mapping must currently: 1. Download the source library and consuming Figma file.2. Match components using their stable component keys.3. Discover every local alias for each component.4. Generate a

Figma Motion is spectacular, but as a new tool, it still has a few workflow gaps.One I’ve encountered is that once an animation contains several layers, the timeline becomes difficult to scan because track order is fixed.I mocked up a concept that would let you drag tracks up or down in the Motion panel, similar to reordering layers, without affecting visual stacking or animation timing.The change is purely organizational. It would allow designers to keep related tracks together, make the timeline easier to read, and simplify working through complex animations.Here’s a quick animated mockup of the idea. Would this improve your workflow?  

Figma Motion introduced the ability to set the anchor point (origin) of elements, but this property is not reflected in prototype mode. In prototype mode, the defined origin is ignored. Quick win: make prototype mode recognize and use the element's defined origin to rotate them correctly.  

I would really like to have the option of adding more than one tag to an annotation. For example now i’m adding QA annotations by categories, but I would also like to add another tag for each one which states the urgency of the annotation.  Two more options that might work are either adding a fill color option to the annotation, or add a customizable status drop down to each annotation. 

Love the new Typography Variable release, but it falls short for our use case. Our goal is to use variable modes to switch styles between our 3 brands. 2 of those brands use all caps for headings, the other brand uses sentence case. We need to be able to bind a variable to the case of a character style (As typed, Uppercase, Lowercase, Title case, Small caps). Without this capability, when switching modes from brand 1 to brand 2 for example, we are getting the default case for the character style (sentence case coming from brand 1). We would then have to go through our designs and manually type in all caps for all instances of headings in brands 2 and 3. Certainly not ideal and will lead to inconsistencies / places where manually typing in all caps are missed if we went this route. Until binding a variable to the case of a character style is an option, using typography variables isn’t feasible for our use case.

Description: Currently, Figma allows switching between different Modes (e.g., Light/Dark) within a single variable collection. However, there is no built-in functionality to switch between entire Variable Collections dynamically. This limitation makes it challenging to manage multiple themes efficiently, especially in large-scale design systems where different themes (e.g., Default, Gaming, Minimal, Custom) share a common structure but require separate sets of values.Proposed Feature: Collection SwitchingWe propose adding an option that allows users to switch entire Variable Collections in the same way they can switch Modes. This would enable designers to define multiple themes and toggle between them seamlessly without needing to manually update Aliases or duplicate components.How It Would Work:Collection Selector: Similar to the Mode switcher, users can select a Collection (e.g., Theme 1, Theme 2, Custom Theme) from a dropdown in the Variables panel. Automatic Updates: When switching