Share Your Thoughts

I don’t use Figma every day. I don’t want it to open every time I boot my computer. This is a very annoying user experience. I don’t want to have to remove it from system settings every time I Figma updates. Perhaps, you should stop adding it to my system settings every time there is an update. I don’t want Figma to open every time I boot my computer. You are forcing me to open an application that I don’t want open when I boot my computer. This is a terrible user experience. I know other designers are annoyed by this as well. Stop adding it to my system settings every time Figma updates. It’s just dumb that Figma does this. I will use Figma when I need it.

Please add the ability to group pages in Figma.For large projects with many pages — such as a UI kit — it would be much easier to navigate if pages could be organized into groups or folders.This functionality already exists on other platforms.  

Hi,I’ve encountered this bug testing out slots.  I’ve created a desktop component with a slot that uses components and both have variable widths for desktop and mobile. If I drag that instance with slotted components into a frame/section that’s set to mobile it will shrink down, but if I drag it out, the slotted components remain mobile size.Attached is a screenshot of the discrepancy.The instance functions perfectly fine if I manually set the desktop/mobile modes through the appearance panel though. Ps. I love the possibility of slots and can’t wait when it’s out of beta.

Native Dev Mode annotations are valuable sources of context that get lost for anything using the MCP. Measurements and props, too, although I don’t think that’s nearly as important. My response from Github Copilot:This is a limitation of the Figma MCP server that powers my Figma tools — it currently exposes the layer/node tree but not the annotations or comments API endpoints.

 Hi Figma Team,I’d like to suggest a feature improvement around managing shared design system files.Problem:In our team, multiple designers have edit access to the design system file. This sometimes leads to accidental or unintended changes, and it becomes difficult to track or control who modified key components. Even with version history, identifying and managing these changes is time-consuming.Suggestion:It would be helpful to have an option to “lock” a file (or specific pages/components) to prevent editing by default.Some possible approaches: Ability to lock a file so only selected users can edit Restrict editing of specific components/pages within a file Optional approval flow when someone tries to make changes Temporary unlock option for maintainers Why this helps:This will ensure better co

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!

I’d like to suggest adding a native option in Figma to mirror (flip) an image directly within its image settings.Currently, when working with components, if I need to mirror an image inside a card, I have to flip the entire card to achieve that effect. This becomes especially problematic when the card is a component, as it interferes with layout, constraints, and overall usability.As a workaround, I’ve been manually mirroring images outside of Figma (on my computer) before importing them back into the component. However, this adds unnecessary friction to the workflow and slows down iteration.Having a simple “flip horizontal / vertical” control within the image properties would make the process much more efficient, especially when working with reusable components and design systems. Thank you!

If I add an instance of a component that in its master form is set to fill, and I am adding it to a frame with auto-layout, I want that instance to be automatically set to fill. That instances are always added as fixed width when the master is set to fill is an annoying inconvenience, especially when nested components also get set to fixed, thus requiring a whole process of fixing widths.

We create and share our design system components with the whole company and we’d like to have a more rigorous process when we publish modifications of the Figma file. If the publish description would be required instead of optional, designers could not forget to add a description to their modifications anymore.

Sections are useful for organising the canvas. However, when I want to keep editing things within a section I keep selecting and moving the section accidentally. Therefore, I would like to be able to lock the section position without locking the elements within the section.

I’m often facing this problem. When I tried to resize the layers panel, it sometimes accidentally dragged the slide which is really annoying. Furthermore, the cursor hitbox for resizing the layers panel is too narrow (it’s really on the edge of the layers size) so that the cursor turns into vertical double-sided arrow. I hope Figma can figure out to fix the layers panel resizing issue. 

It would be a great idea to add the ability to move annotations (сhanging the place). Right now, they’re fixed in place and can overlap other elements. And you cannot change it.What I mean is the ability to reposition an annotation freely while keeping the link to the target object intact.Annotations are a really useful feature—thank you! Previously, I had to create similar functionality using my own objects. Please do not move this offer to another discussion. 🙏Can we move the Figma Annotations (in dev mode) from one Figma project to another?These are different questions.

Hi Figma Support,We are a SaaS Security Posture Management (SSPM) vendor that integrates with Figma to help our mutual enterprise customers gain visibility into their Figma environment.Current situation:We're integrating with Figma's SCIM API and need to clarify the behavior of GET /scim/v2/{org_id}/Users.Two questions: If an organization uses SCIM for provisioning, can admins still create/invite users directly in Figma (outside of SCIM)? If yes — does GET /scim/v2/{org_id}/Users return all organization members, or only those that were provisioned through SCIM? We need a complete user directory for security posture management. If SCIM only returns SCIM-provisioned users, is there any other API endpoint that returns all org members?Thanks!

I have a numeric input field as a component, and its value is set as a text property called value. Pretty simple stuff, right?For prototyping reasons, I want to bind this field's value to a number variable, so I can add/subtract to this value when I press a button somewhere else on the screen. Also pretty simple stuff, right? Well, apparently not. Turns out I just found out that we can't bind number variables to text properties for whatever reason — they don't even show on search results. And since there's no component property of type number, this simple prototyping scenario I'm trying to achieve appears to be impossible. Meanwhile, if I simply remove the value property from my component, then select the plain text layer with the value and try to bind it to my

My userflow is large, when I make it in FigJam then export it took 45k x 4k pixel to Figma, Figma design cap it on 4k for exporting image, so my imported png looked pixelated into oblivion. Could you Figma team make it seamless to add connector in Figma design like it was in FigJam? I just want to show my userflow in my portfolio in Figma design before upload it into Figma site.

When working with more complex auto-layouts in Figma, I find myself accidentally changing frames/instances from Fill to Fixed or Hug by double clicking on the edge. In some cases I don’t catch myself and only discover later that parts of a prototype are not responsive. Is there a way to disable this or change the behavior to require a key modifier or something? 

I want to be able to lock a component on the page for everyone except myself. 

The Figma MCP server fails to authenticate when using opencode, returning a 403 Forbidden error. To Reproduce1. Configure Figma MCP in opencode.json:{  "mcp": {    "figma": {      "type": "remote",      "url": "https://mcp.figma.com/mcp",      "enabled": true,      "oauth": {}    }  }}2. Run: opencode mcp auth figma3. Error received: HTTP 403: Invalid OAuth error response: SyntaxError: JSON Parse error: Unexpected identifier "Forbidden". Raw body: Forbidden Expected behaviorOAuth authentication should succeed, as it does with other MCP servers like Context7, Sentry, etc. Root causeAccording to Figma's documentation (https://help.figma.com/hc/en-us/articles/32132100833559), Figma only supports a pre-approved allowlist of MCP clients:- Claude Code ✓- Cursor ✓  - VS C

Hi Figma Community!  I couldn’t find anyone else having this problem, so it’s probably “just a me thing.”  Whenever I duplicate a style, I always edit the ‘old’ version by accident, thus throwing off the entire design system. Any chance that the powers that be could tack on the text “copy” or “duplicate” ?  But it would have to disappear when edited.  Thanks for reading! 

Currently, in Figma, smart animate only works on opacity, color fill, stroke, position, width&height. The options at your disposal when making an interactive prototype are pretty limited. It would come in handy if Figma can expand the supported animatable properties to include: Radius, Effects (shadow spread), VectorNetwork, Polygon Ratio, Ellipse Sweep, Dash, etc.

Smart Animate needs some TLC from the Figma team.I am lucky enough to work in an industry that is not averse to using more interesting animation in our UI, however I can’t create proper examples of interactions because of how Smart Animate works.Animation is directly tied to prototyping flows and that creates issues as animations are not ‘pages’ and exist outside of a page-to-page framework. Smart animating between 2 frames inherently means that all animations start and end at the same time, of course that is exactly how it supposed to work but this makes certain types of animations completely inaccessible - such as cascading items (multiple objects loading in on slight delays). Nested Animations can’t trigger on page load don’t work and they take forever to make so there is no real work around for this. There have been a few posts on the subject, but I believ

Took me a minute this morning to find the new placement of the publish button for figma make prototypes. This is an action I am frequently doing as I push changes/updates to those who have access to the designs. I liked the old placement of this much better which wasn't buried two levels deep. With this latest change, putting it under the share button > publish > 1st line item - it is less clicks to change the URL of the prototype which is share button > ‘update’ icon, which is an action I would never want to do. If anything updating the URL of the prototype should be several levels deep; not publishing changes. 

It would be really helpful to be able to use a variable to set a Type Style’s Letter Case (under the Type Settings meatball menu). It could be a String Variable, and the options would be “As entered”, “Uppercase”, “Lowercase”, “Title case”, and “Small caps”. I personally use modes to switch between different brands, and some brand styles require uppercase while others don’t allow it. This suggestion may be a small feature in the grand scheme, but I wonder if others would also find it useful.

I love Figma, I’ve finally been able to get rid of Illustator.However, Illustrator had a very useful function when working with a large artboard or a large number of artboards. I could zoom out to view the project, select any object(s) I was interested in, and then zoom+ in to or zoom-to-fit (focus) the selected objects.Currently, the zoom in Figma is always focused on the centre of the screen, meaning I need to reposition the viewing window as/before I zoom in to work.  

Hi,I’d love to suggest improving the experience of working with Color Variables in Design Mode.Right now, copying a variable name (color token) takes several steps and interrupts the workflow. In contrast, Dev Mode has a really smooth pattern — you can simply click on a variable color line and instantly copy its name.It would be great to bring the same interaction to Design Mode:One-click to copy the variable name One-click to copy the hex valueOur team recently migrated from Color Styles to Color Variables, and this has become a noticeable pain point in day-to-day work. We often need to quickly copy token names (for documentation, communication with developers, etc.), and the current flow feels slow and cumbersome.This small improvement would significantly speed up workflows and make wor