Suggest a Feature

I work in Figma primarily through shortcuts and keyboard navigation, and the growing set of on-canvas controls have become a real source of friction for me.I use keyboard as much as possible; to move between and into layers, switch tools, and manipulate objects rather than clicking around the canvas. The main exception is when I have to select or move something on the canvas outside the layer-tree that I’m currently in, as it’s faster with mouse. That's when I keep colliding with the on-canvas controls. For example the [+] button for adding variants to a component set, the auto layout padding handles that appear near frame edges, and the recent AI agent button beside selected elements. They are probably useful for many, especially new users, but for me they just cause mis-clicks and clutter the UI.I understand the rationale behind adding those elements. Making features visible on-canvas improves discoverability, which benefits a lot of users, and I'm not suggesting them to be removed.

Figma's current branching is a bottleneck. All branches must come from main.If one designer is working on Feature A (v1.1.0) and another is on Feature B (v1.2.0), the designer on Feature B cannot get updates from Feature A. They are blocked until Feature A is fully merged into main. This forces designers to either wait, or manually copy-paste work, which breaks components and causes errors. The Solution: We Need Git-Style Branching To fix this, we need three features that developers use in Git every day: Branch from Branch: Let me create a new branch from any existing branch, not just main. Update from Branch: Let me "update" my branch by pulling changes from any other branch (e.g., merge Feature A directly into Feature B). "Cherry-Picking": Let me select specific changes (like a single component update) from another branch and pull just that one thing into my branch. This would unblock designers, stop manual copy-pasting, and allow teams to work in parallel safely.

We have a range of team members using Figma, but admin users typically don’t log in regularly or use it day-to-day. As a result, when someone requests edit access, there's often little oversight or context around what approving means for the business.One key issue is that granting edit access automatically assigns a paid editor seat — and this cost gets added to our invoice immediately. Unfortunately, not all team members are aware of this. It’s easy to click “approve” without realising the financial implications.From what I’ve read on this forum, there’s no logical solution to this yet except to request a refund. This is giving ‘dark pattern’ vibes.We have people on the team who should never have Figma access such as executives wanting to modify designs.Suggestions: Add a clear warning or confirmation step when approving edit access that explains a paid seat will be created and billed immediately. Introduce a process for reviewing edit access regularly to ensure seats are still requ

I know it was suggested 5 years ago but with all the new stuff this is so basic to not exist yet.To have an inner stroke and outer stroke at the same time, you have to make 2 containers. 2 too many.Pls we neeeed this

Figma, I’m on my hands and knees begging you to allow us to add links to frames (NOT JUST TEXT), and for those links to be preserved when the file is exported as a PDF.  The need for this is DIRE. PLEASE. 

Hi! I’m currently working in the international company and i need to export some of the formats i’m doing for work in webp format, Figma is the best app to create and manage that frames, but it’s very uncomfortable for me that i have to use plugins to export in webp, because they are exporting all the stuff in zip and i need to put them in the folders (there are many many of them) myself, please add that feature, i’ve seen many people here are requesting it for years. THANK YOU!

Hi Figma team,I'm reaching out with a request on behalf of several developers on our team who use Linux as their primary development environment.Currently, the MCP (Multi-Context Preview) feature is locked behind the Figma desktop app, which is only available for macOS and Windows. This poses a challenge for Linux developers who are unable to access or use MCP due to the lack of a supported desktop app.We’d love to see one of the following: A Linux version of the Figma desktop app to unlock parity across development environments. An alternative way to run an MCP server without the desktop app, such as a standalone CLI or server binary that can be installed independently. This would greatly improve the development experience and make Figma’s workflow more accessible to cross-platform teams.Thanks for considering this request!

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

I can’t seem to find a way to Hide all lower levels of my mind maps. I click on the arrows, and nothing happens. It’s making a mess. I can’t use it for practical reasons, presentation-wise it’s kinda frustrating. Is there any viable way already for me to do it? If it’s yet to come, please do it 😍 it’s a game changer for me and many others who are still waiting for it

Our team has made the move to variables for spacings. While these are great for consistency and dev handoff, they are slower to work with than raw pixel values. For example, I could previously click into a padding field, and Shift+Up to big-nudge my way to the right size (I have my nudge set to 8, so I stick with our DS standards). Now, with variables, I have to hover over the field, and then select the new value from the menu. The speed of nudging is lost, as is the drag from field icon shortcut. When a field already has a variable, it would be great for nudge (shift+arrows) to cycle through the variable menu options, and the drag to work the same. When the field doesn’t have a variable already, it would be great to do those actions, but with a modifier key, to jump to the variable selection. Thanks for your time!

How can we specify the design component code that the AI should be using? In the Attributions.md file, it says:This Figma Make file includes components from [shadcn/ui](https://ui.shadcn.com/) used under [MIT license](https://github.com/shadcn-ui/ui/blob/main/LICENSE.md). We don’t want an AI’s transformation of shadcn components into what looks like our design components. We want to use our actual design components to limit the number of ways the AI can miss interpret the designs it is prototyping to reduce variation errors between prompts.For example, I can give the AI the same prompt, and it will give me different designs when it’s re-interpreting the shadcn→design components every time.Generating code that is already aligned with our design components is also more useful for engineering workflows to convert the prototype into PR’s.It should also import the guidelines file properly from the design library. I don’t think this worked for me. Between the attributions and guidelines bein

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.

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!

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

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.

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.

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 🙂

Great to see motion elevated beyond smart animate.Thanks Figma, Great job!Currently as I notice, Motion disables pen Tool,  allows only pencil.Trim paths works for strokes drawn from pencil tool,  open shapes like line tool.It doesn't work for closed /parametric shapes and arrow shape. So having a trim path displayed in its panel doesn't make any sense now.It would be nice to have closed shapes like rectangle to have its stroke animated so we can try gradient or coloured line tuning around it. Currently it's quite a struggle and not straightforward everywhere.Thanks!