Suggest a Feature

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

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?

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.

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

 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`.

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🙏