Suggest a Feature

The feedback/suggestion is pretty much summed up in the title. I wish the colors showing up in the ‘Selection colors’ would also include the shadow effects. That way we could also change the color in that effect without having the need to select individual elements where that effect applies.

The new in-built animation tool  is an amazing upgrade. Ive already started to animate my hero sections and layouts further down the page.  one thing would be absolutely amazing is if you could set the animation to start playing as it came into view. This way we could directly show clients scroll animations in the design stage. Atm you have to set the animation to loop and hope it’s at the start when someone scrolls down to it.

I don’t use Figma all the time, I don’t want it to run anything on startup. It’s frustrating to manually remove Figma from Login Items, since it automatically adds itself there again. It would be nice to have at least an option to disable it in settings, or even better - remove that functionality at all, since it’s not user friendly. I want control over what and when the apps do at my workstation. P.S. If it’s needed for updates check - I’m more than okay to update on app start

Feature request: Add a built-in “Filter by Reviewer” option for comments Currently, comments can be filtered by manually entering a user’s name (as described here: https://forum.figma.com/ask-the-community-7/filter-for-comment-13462). However, it would be much more efficient to have a built-in “Filter by Reviewer” option, similar to Adobe Acrobat.For reviewers, it’s common to revisit only their own comments to verify that feedback has been addressed or to continue a review. A dedicated filter would make this workflow much faster and more intuitive, especially on files with a large number of comments. This would be a valuable quality-of-life improvement for anyone involved in design reviews.

Hello, I’m a UX Designer working in the public sector and love the new extension tool! However, I think it would be more valuable if it allowed users to enter the URLs of the pages they would like captured instead of capturing one screen at a time. Also, it would be time saving if users could select the screen sizes for the captures (e.g. mobile, tablet, and desktop).  I hope you can consider these updates!

To reduce component weight, my design system team has been exploring using variable modes to toggle between different “variants” of a component, rather than just using variants. The benefit of this is that for these “style” specific properties, where just styles are changed like fill and stroke, using modes significantly reduces the weight of a component in the system. In this example I use a Badge component, and variables to change between the colors of the badge.However, my component code still has a “color” prop. Because I don’t have a color prop on my Figma component, but rather a “BadgeColor” mode that controls this property, is there a way in which CodeConnect can still map this to the correct code property? Currently it doesn’t seem like CodeConnect can read anything that is not a property. Realistically all I need is the CodeConnect to be able to read the string value of the mode, and map that to the actual code prop.

Hi, Thank you for Figma Motion it’s great !There is one thing I can’t figure out : once I have set motion on the components, then add them to my website frame (desktop, mobile...) how can I set a trigger for the motion to begin ?For now, it appears that they all run at the same time, when the page is loadedIn AE, we can work on different elements (as we do here on components) and then add them to a precomposition so we can choose when to start etc…Can we add this on Figma Motion or on Prototype but the trigger won’t be a timing but a scroll ?Like, you have your full page : Header, Hero, Editorial whatever, and I would like the animation on the Editorial section to start when the user scrolls 10% on itThank you for your help !

Hi there!Really enjoying the new Figma Motion feature. Been waiting for this one for a really long time. Genuinely one of my favorite features from Config 2026, including shaders.That being said, here are a few things I'd really love to see improved:Timeline UI segmentation: the current UI feels really unstable, with all layers & settings blending into one low-contrast mass without any visual clarity. Layer color swatches: adding color accents per layer would make navigation and visual separation significantly easier. Preview FPS setting: no option to control preview playback FPS right now. Having a dedicated input separate from export would make it so much easier to feel-test animations at different rates. Inline property preview + animated property count indicator: this might be the most controversial one, but the keyframe bar space feels genuinely wasted right now for no good reason. Showing the property name and value range inline (like Opacity 0 → 100), plus a small dot indica

The animation capabilities are absolutely fantastic, especially being able to export as an animated SVG. It would be ideal if we could export as a MOV file because videos with transparent backgrounds mean we can create lower thirds and multiple different video assets. It would prevent us having to use After Effects or any other video tool 

Hi,The addition of annotations and measurements to Design mode is such a great decision.However this is rendered almost useless if the annotations and measurements can’t be made visible to View Seat users.Often annotations are used for communication with a range of stakeholders, not just designers and developers. It’s not viable to upgrade every stakeholder to a Full or Dev seat to engage with this content.

Figma should support rendering drop shadows on both the inside and outside of strokes on closed paths without requiring Outline Stroke.Right now, if I have a circle with an inside stroke and drop shadow, Figma only renders the shadow outside the closed path. Apps like Sketch, Affinity, and other vector drawing apps render the shadow on both inside and outside of the stroke, which creates the expected inner shadow while keeping the circle editable.Same editable circle, inside stroke, and drop shadow setup. Figma doesn’t render the shadow inside the closed path, while Sketch creates the expected inner-shadow without outlining the stroke.Outline Stroke is a workaround, but it’s destructive. It’d be much better if you could keep the circle editable and still get the same visual result.

Hi Figma team,We build a Figma plugin that renders user artwork into product mockups. With Figma’s newer video support, we want users to place a video fill/layer directly inside a Figma mockup frame, then run our plugin to render/export the final animated mockup.Today the Plugin API exposes VideoPaint.videoHash and figma.createVideoAsync(bytes), but we cannot find a supported way to read an existing video fill back as bytes, a Blob, a URL, or decoded frames. Images have figma.getImageByHash(imageHash).getBytesAsync(), but video appears to have no equivalent.Are you planning to add one of these?figma.getVideoByHash(videoHash) video.getBytesAsync() video.getUrlAsync() a REST endpoint for video fill URLs a plugin-safe frame sampling API for video fillsThis would unlock video mockup rendering, video compositing, video export plugins, and parity with image fill workflows.Thanks.

Hi Figma Team,I am writing to suggest the addition of a native Masonry Layout feature within the current Auto Layout system, specifically as an extension of the "Wrap" property.1. The Current Problem: The current Auto Layout "Wrap" feature is incredibly helpful, but it only wraps items horizontally (Rows). When designing interfaces with cards of varying dynamic heights—such as complex enterprise dashboards, product catalogs, or dynamic data grids—we cannot automatically create a vertical masonry effect.The current workaround requires manually dividing items into separate vertical columns (Vertical Auto Layout) and grouping them in a horizontal parent container. This method is rigid, time-consuming, and breaks the logical flow when rearranging elements or demonstrating dynamic data flows in prototypes.2. Proposed Solution: Introduce a "Masonry" (or "Vertical Wrap / Pack") behavior option when Auto Layout Wrap is enabled. This feature should allow elements (with Hug contents height) to a

Please add YAML to FigJam code blocks. Others languages are also welcome in addition to this.

In order to help guide a client or stakeholder through a design when my team isn’t available, we use comments to explain our decisions. We recently noticed that anonymous viewers of prototypes can no longer view comments without having an account. In our use case, users won’t need to respond to comments as they’re used as a guide, which makes signing up only to read them very inconvenient and a big friction point. It would be great if there were a way that those anonymous users can be allowed read access to the comments in the file. If they wish to leave a comment, then they could either sign up/login to an account, or use something like the solutions offered in Easier access for commenters. Without this, we will be forced to find a new solution to guide users through our decision-making process without needing them to watch/skip around a long screen recording or us having to remake all pages and comments in a PDF or Invision.

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 Code ✓- Codex ✓- etc.OpenCode is not on this list, so Figma's authorization server rejects the OAuth flow. DiscussionFigma's approach breaks the core promise of MCP - that any client should work with any server. This creates v

I've been really enjoying the new Motion features in Figma. The experience feels intuitive, and creating animations has become much faster and more enjoyable. Even in its current state, Motion shows a lot of potential, and I'm excited to see how it evolves.While testing, I came across a few areas that could significantly improve the workflow: Nested Layers in the Timeline When working with nested layers, child layers currently appear individually in the timeline alongside their parent layer. This can make the timeline cluttered and difficult to manage. It would be helpful if the timeline supported nesting similar to the Layers panel, with expandable and collapsible groups. Dedicated Clipping Mask Workflow Motion currently lacks dedicated clipping mask support. A masking workflow similar to After Effects would make it much easier to create and animate reveals, transitions, and other advanced motion effects without relying on workarounds. Dedicated Alignment Controls Motion currently

Please can we get percentages for variables? We can use percentages manually, but we can’t create a percentage as a variable. This would speed up my design to dev process tenfold, and considering we can already use percentages in the design, why disallow it in variables?An example is I want store values for line height and letter spacing as percentages which behave responsively/dynamically, so when creating type variables I don’t have to do manual calculations, store 10+ letter spacing/line height values based on which font size they will be used with and hope I never change the font size variable in the future.

When aliasing a color variable to another (img 1), or using it directly on an element (img 2), we should be able to override the opacity without the need to create a variable for each transparency variation: Cant override opacity in the alias: Example 2 Cant override the fill opacity:

Hi! I’ve created a dialog component in one Figma Make file and I want to use it in another file.What’s the best way to import or copy it over? Should I copy-paste it manually or is there a better way to reuse components across files in Figma Make?

There’s no visible scrollbar in Figma prototyping mode. Yesterday we’re having user testings and once again this same topic popped out. Some of the users didn’t thought that they could scroll prototype because scrollbar wasn’t visible. One of the user was using laptop’s touchpad and he wasn’t able to scroll with only using touchpad. Guiding user how to use prototype during test can harm testing situations. Atleast it’s sure that if user thought that he can’t scroll it leads to biased feedback about product. If there’s some reason not to have scrollbar it could be atleast optional feature that designer could turn visible scrollbar on from options. It’s not only who has came across with this weakness in Figma. Here’s old Spectrum thread about same topic but Figma hasn’t done anything for this yet and I hope this get more attention here.

Figma motion does not currently have the ability to play and export video fills, so video objects are treated as static images. The ability to incorporate video objects into the timeline would be extremely helpful. Exposing the current frame of a video as a keyframeable property be a great solve. 

I’d like to move assets to the top since it’s the main feature I use.It would be cool if we could add, remove and move widgets so that each user can have its own custom toolbar. Personally i’d like to add the library analytics there, for istance.Thank you 🙂

Select matching layers (with shortcut ⌥⌘A) is not working on layers inside Slots.The option is greyed out in the command menu (image below).I’ve double-checked that both layers have the same structure & naming.It would be extremely valuable to have this option available inside Slots, since most screens I'm working on take advantage of slots for reusability.