Share Your Thoughts

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

Hello Figma Community 👋I wanted to raise a question regarding the monthly AI credit system and also share a suggestion that could benefit many users.Currently, on the Professional plan, we receive 3,000 AI credits per month, and as confirmed by support, unused credits reset at the end of each billing cycle and do not roll over.However, in real-world usage, credit consumption is not always consistent every month. Some months require heavy usage, while others involve lighter workloads depending on project timelines.📌 Example Scenario:Month 1: Allocated credits: 3000 Used credits: 1800 Unused credits: 1200 (expired) Month 2: Project demand increases Required credits: 4200 Available credits: 3000 only Result: Need to purchase extra credits, even though unused credits expired in the previous month.This makes planning usage difficult, especially for freelancers, small teams, and agencies where workloads vary.

Hi Celine- Are there any plans to remove this constraint? We have container frames with a handful of separate screen specs in them and would like to designate certain screens as ready, but not the entire set. It’d be great to not have to have the frame or instance top-level, but allow nesting and still mark contained elements ‘ready for dev’. Thanks!

My team and I are currently having the inconvenience of having to publish our library every single time we make even a small change (like a font size increase, color change, etc.) and then switching to the working file and manually updating the library. Due to the nature of the project we do this quite frequently and having to publish – switch file – update every single time to see the changes in our designs turns out very time consuming if you add it up. It would be amazing if Figma could integrate a shortcut for automatically updating a library and automatically updating the files it is being used on (like a cmmd+S shortcut!), of course not everybody might want to have this so it would also be nice to be able to turn this shortcut on and off.

You can currently set multiple stroke colours to an object, but they will share the same properties (thickness, position, etc.). My idea is that you should be able to set all stroke properties on each stroke: Make sense or am I missing something?

When I started sharing AI Skills with teammates, I expected teammates to be able to edit a published AI skill and republish their changes without requiring the original owner to make every update.Problem: published skills are shared for use, but ongoing maintenance is blocked when only one person can update the source skill.Impact: this slows iteration, creates ownership bottlenecks, and makes shared team workflows harder to manage.Desired behavior: teammates with the right workspace permissions can open the published skill in Manage skills, edit it, and use Publish changes to update the shared version.

According to Cursor, this feature API does exist but it’s not allowed. Until we fully trust and understand how AI tools can help us with our work, we need a way to revert back to our designs prior to having any AI tool update it. Client: Cursor + remote MCP (https://mcp.figma.com/mcp) Tool: use_figma API: figma.saveVersionHistoryAsync(title, description?) Error: "saveVersionHistoryAsync" is not a supported API Debug UUID from our attempt: 9e76fe30-de7b-4528-b50e-a337ac24dd14 Use case: named “before Cursor edits” checkpoints with the user prompt in the description

It would be great if dev could export without rounded corners applied and or have some export flexibilities

📣 Don’t make the same mistake we did in attempting to clean up some projects by taking advantage of nesting folders 🚨If you move a top-level folder from your “All folders” section into another folder, then realize you actually want it back at the top level (perhaps due to the inherited permissions not being suitable, or just because you re-thought your organization strategy) there is apparently no way to reverse this change.You would think you could drag the folder back onto the “All folders” option in the sidebar: Nope! Or perhaps up to the team name that shows at the top of the page… Nuh Uh! Maybe right-click > “Move…” on the folder will offer the “All folders” option, maybe even under the “All” tab Negative! We looked through all the documentation and best practices guides we could find and this appears to be a fully-unmentioned gotcha 😖The AI support agent “helpfully” suggested manually re-creating such folders back at the top level, reapplying permissions as desired, and fin

 The `list_shader_fills` tool can only reference built-in shaders. There should be a path to make user-defined shaders accessible via `list_shader_fills`.

It seems a little weird that you can’t copy a link to a layer within a component instance. I understand why this might be technically difficult, but it has been a real pain point for our engineers recently who would like to be able to point their AI coding tools to layers or frames inside components and who aren’t attuned enough to what’s going on inside the layer hierarchy to know why they can copy links to some things but not others.

Hi @Figma_support Issue If you choose unevenly spaced objects, Figma doesn’t allow you to enter a numeric figure to evenly space these. It does if the objects are evenly spaced though. Example Let’s say you have 3 objects on the canvas, each at different distances from each other and you want to set the vertical spacing between each object to 32px. You need to evenly distribute the objects first then then set the 32px spacing. Solution Cut the need to evenly distribute step by adding horiz and vert spacing inputs fields when unevenly space objects are selected. Mock up Thank you!

Hi Figma team, It would be very useful if it was possible to crop/zoom-in an image while using the fill option for responsiveness designs, and then deciding if it’s the width or height of the cropped image that should be the constraint. Here’s an example with a pink area showing what part of the image could be visible based on the selected constraint:  Current problem being a cropped image will be deformed if its container change size, which happens  when using responsiveness and auto-layout. Looking forward to see this improvement being worked on! 

Currently, when you draw any shape, the shape becomes selected. Makes total sense, since I would likely want to change the color etc of the thing I just created. But the same is not true of connectors. After drawing a connector, the previous shape is still selected. When I want to change the color of the connector I just drew, I keep accidentally changing the fill of the shape instead. It’s not only extra clicks to change the connector color, but also prone to user error due to the inconsistent design of the property bars and the inconsistent behavior across objects.

The recent update of the Make panel UI has seemingly removed the ‘Go to Source’ button when in edit mode. You used to be able to select an element in the app, then go to the source code.The code would be highlighted for you and you can then make manual edits without the struggle of scrolling and navigating through the code to find the element you want to edit. Please bring back this feature!!

I'm really enjoying the Actions menu! It would be awesome to have the option to access the Assets tab directly as well, just like we can currently access the Assets left panel with a keyboard shortcut. This way, we could set a custom shortcut to open the Assets tab directly from the Actions floating menu.  ​@Figma_Desktop🙏

Figma MCP should provide frame-to-image exporting as a tool. That way AI could export graphics in a page design as `.svg`s, `.png`s, etc... and upload them to our cloud bucket,or put them in our web assets folder.

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.