Suggest a Feature

PROBLEM: Currently, if you and a user outside of your team both have paid Figma accounts, and you need the other person to be able to edit your file, you need to pay for A THIRD account. i.e. For TWO freelancers to edit the same Figma file, you need to pay for THREE Figma accounts. This is clearly a terrible customer service experience and I suspect it’s a common issue as you’ll see from Figma’s own Product Support team response below. SOLUTION: The ideal workaround would be to offer free editing when both accounts are paid. Alternatively, if it’s an expensive service to provide, it seems reasonable for Figma to charge a clear fee (e.g. Editing collaboration: $2 per file per month, or $5 per project per month). Please upvote and add to the discussion. For reference, here’s my last message from Figma’s Customer Support, who are clearly trying to help solve this problem: Hey there Paul, Thanks for reaching back out. Again, all editors in your team space are billable to you. Even if Robin

Feature Request: Add a Delete option to the right-click context menu for elements and frames in Figma. Currently, deleting elements requires pressing the Delete or Backspace key, which is difficult or impossible when using Figma in a browser on a device without a physical keyboard (such as a tablet). Adding a Delete button to the right-click menu would make Figma more accessible for users who rely on touch or on-screen keyboards.

I really appreciate how much Figma has invested in Dev Mode and AI features. With MCP support and AI-assisted workflows, Figma is becoming an essential tool not only for designers, but also for developers.However, I think there is a growing group of users that doesn't fit well into the current pricing model: solo developers and small teams without dedicated designers.I'm currently a paying Professional subscriber because it's the only plan that gives me access to the developer features I need. As a solo developer, however, I mainly use Figma for:MCP integration with AI coding assistants AI-generated UI designs Editing designs with prompts Inspecting layouts Generating code from designsI rarely use advanced collaboration features, team libraries, branching, or other designer-focused capabilities included in the Professional plan.I would love to see a new plan designed specifically for AI-first developers. It could be a lower-cost individual subscription that includes Dev Mode, MCP, AI d

Reference Preview: https://ghost-aura-apk-panel-ff.s3.ap-south-1.amazonaws.com/index.htmlFeature Request OverviewI am currently designing a mobile interface overlay (specifically the V2 panel) and I am struggling with the asset generation for the final build. The link above demonstrates the current prototype behavior versus how Figma handles the export. I would like to suggest a feature that allows better handling of "Ghost" style semi-transparent layers when slicing for Android XML.Project SpecificationsName: Ghost Aura UI Project Version: V2 Panel Integration Type: Mobile Overlay / FF FrameworkPanel Features & Design RequirementsTo ensure this interface works correctly in the final application, the following design elements need to be preserved during the export process:Floating Window Capability: The design relies on a floating icon structure that needs precise coordinate mapping. Aimbot-style Focus Assist (UI Concept): The central crosshair alignment tools in the panel need to

 We’d love the ability to group a set of animated frames into a named animation group or section, similar to how compositions and grouped timelines work in After Effects.For example, if a project contains multiple scenes, we could select all frames and animations related to one scene and group them as: Slide 1 Animation Invoice Builder Intro Tax Section Send Email Sequence Final Logo Animation The group could then be collapsed or expanded in the timeline, making complex motion projects much easier to organize and navigate.Ideally, this feature would allow us to: select multiple animated frames or layers group them into one animation section give the group a custom name collapse and expand the group in the timeline move or duplicate the whole animation group together clearly separate different scenes or slides inside larger projects We’ve been very happy moving more of our motion workflow into Figma Motion, but once a project grows beyond a few animations, the timeline

We’ve been really happy to switch from other motion design tools to Figma Motion. Having the design and animation workflow in one place makes the process much faster, especially when the UI already lives in Figma.The one feature that still feels missing is audio support.It would be extremely useful to attach custom audio files such as MP3 or WAV to animations and timelines, for example:click and hover sounds popup and modal sounds transition sound effects notification sounds background music voiceoversIdeally, each sound could be placed and trimmed directly on the timeline, synchronized precisely with an animation or interaction, with basic controls for volume, fade in/out, and looping.For product demos and UI motion videos, sound design is a major part of making the final result feel polished. Right now, having to export the animation and move into another tool just to add sound breaks an otherwise excellent workflow.We’re genuinely happy to move more of our motion work into Figma. If

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.

I have a problem where I have noticed that when a designer detaches a design and it is using hidden components within it, that it ends up decoupled from the library… I was always under the impression that since it is a component in the library, that if it was detached it would still be able to receive updates via these hidden components… I have realized this is not the case.I think a new feature request should be made to allow hiding the components from the asset panel view (which is what people actually want from the hiding feature) without losing the link to the library.If the feature intent is to not publish these components at all, I am not understanding why when we detach, why those hidden components don’t detach as well? This is what gave me the false notion that they would still be able to receive updates, since they are still an attached component -- but attached to the wind it seems...Design system maintainers are not looking to not fully publish these components, but instead

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.

As many design tools have an easy toggle to switch the orientation or the values of width and height, we shall have it on figma too between the width and height input fields.

Add the ability for Figma Make to change Figma layers, just like Figma's default agent does (possibly through Skills). I'm currently creating a text layer in Figma that requires a custom text effect. I've noticed an interesting thing: when changing the layer—the container for which Figma Make creates content—during resizing, it automatically adjusts to the frame size (Figma's default animation is shown, and the code reacts to it). However, if this is, for example, a text layer, and the number of vertical lines increases during resizing, Figma Make can't automatically change the container—the Figma layer. That is, Figma Make can understand that the layer is resizing and adapt to this change, but it can't adapt the Figma layer itself (resize it relative to its code). It can only work with the contents of the code layer itself, not with the Figma layer. So, I can't create a code layer that, for example, changes in the same way as the default text container in Figma (which resizes vertical

I want Figma Motion can animate shape in future so i can create more flexible animation for shape. Animate with only path quite good with some case but is hard to do with complex shape like logo, vector drawing, etc.

What if there was a global setting for layout grid styling (color and opacity), that worked at the personal level, similar to nudge amount? It’s a half baked idea 🙂 What I’m reacting to is, sometimes my collaborators prefer a stronger grid style than I do (more saturated color, higher opacity), whereas I prefer a nearly-invisible grid. Everyone has different grid preferences, yet grid styling is a shared property. There are lots of personal settings in the View menu and Preferences menu. Global layout grid visibility (View > show/hide layout grids) is a personal setting, while layout grid styling is not… but could it be? I’ve always liked the fact that settings like nudge amount and snap to geometry are personal preferences. Figma files are naturally collaborative, and these personal settings create room for more individualized workflows. It complicates the matter that grid styling is frame-specific… but still, food for thought!

Hi! First, thanks to the Figma team for all the hard work. Now, let’s talk about Figma Slides Templates. To edit the template styles, I have to select a slide first — which feels a bit unintuitive. In Figma, when you click on the canvas without selecting anything, you can access the file’s styles. Can we bring that same concept into Slides?When I open the template selector, I can edit the styles there through a dropdown. Is that really the best or only way to manage styles in Figma Slides? I don’t think so.Colors & Text Styles: I can delete them, but only through a pretty complex interaction — right-click?Layout Grid: How can I set a default grid? Right now, I have to manually add my custom grid to every new slide I create. If we can't set a default, the feature kind of loses its purpose. :(  

Hi Figma team,We're a Rutgers MBS externship team building an interactive SDLC prototype for PharmAllies (Professional plan) featuring an animated avatar rendered by an AI video generator.The request: native background removal or chroma-key support for video fills, or at minimum better handling of near-white video backgrounds against canvas fills.Our case: our avatar videos render with a near-white background that visibly mismatches Figma's true-white canvas across monitors. Background-removal tooling is now standard in consumer mobile editors, but Figma offers no path short of external re-encoding to transparent WebM, which breaks a designer-only workflow. A per-video background removal or color-key option in the Fill panel would close this gap for anyone embedding AI-generated video, which is a fast-growing use case.Happy to share screen recordings and sample files.Shounak Singh

I work in BCG, I created an interesting plugin that could fast pace our team’s work. Was not able to share this with team. If feature already exist, can someone please help.

Please make Dev Mode Annotations visible by all roles, not just Full Dev Mode seats. This can become costly for users needing context but not all the other dev-mode features. Here’s the scenario: We have a dashboard, with cards showing a customer’s account status. This status can be mapped from multiple back-end statuses, to show just one front-end status. For example, any of the following could be mapped to a single status known to the customer as “Completed”: canceled, terminated, sold, complete, etc. This is something that the developer needs to reference, but then also the PM needs to reference in writing tickets (who doesn’t need full dev-mode access), the QE needs to reference for testing automations, and various other individuals on our team. Placing it in a comment makes it less clearly attached to the specific piece of the design, and requires us to keep documentation dispersed among different tools (Jira, Confluence, Figma etc). Simply making Dev mode annotations visible to v

Currently in Figma Motion, there are two separate workflows. Animation panel presets and manual keyframing. Presets are great for quick results, but their keyframes are completely hidden and can't be inspected or modified.Feature request: Add the ability to "expand" or "convert" a preset animation into its underlying keyframes so they appear in the manual keyframing panel. This would let designers use presets as a starting point and then fine-tune timing, easing, and values, bridging the gap between the two workflows.This would be especially useful for:Learning how presets are constructed Customizing presets beyond what the panel currently allows Maintaining a single, unified keyframe timelineThanks!

Hi there,I always use Ctrl + Option + Command + K to jump directly to the main component and also to return to the instance, but returning only works if the main component is still selected.Why does Figma require the component to remain selected in order to return? It feels like it should remember where I came from, even after selecting or editing other layers or components in between.At least the floating button “return to instance” could always be visible.Right now, the navigation state is lost as soon as selection changes, which breaks the workflow when working with component systems.Please make the “return to instance” behavior persistent and independent from selection state — especially for users working heavily with large component systems.Button: Return to instanceThanks! 🙌

I’m trying to make a looping animation with offset layers. There is no in point, and the out point always snaps to my last keyframe. This doesn’t allow for looping animations. I can move layers into negative time. But without having precise control over where the outpoint of the timeline is you can’t make a proper loop. 

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?

Many features now live in the left sidebar, and while resizing it is possible, I'd like panel width to be remembered independently for different tools.A narrow width works fine for Layers, Variables, Assets, and similar panels, but the Agent panel benefits from being much wider. Having Figma remember a preferred width for each tool would improve usability and eliminate the need to constantly resize the sidebar when switching contexts.

Please allow us to adjust the random seed for effects like Noise and Texture.It would be incredibly useful to be able to have two shapes with the same Texture displacement size and radius, but a different random seed so they look different.

Figma Motion has great potential in transforming video editing workflows. However, a significant downside at the moment is that if I elect to import an existing video or gif asset into Figma Motion, there is no option for essential customization like controlling the start time of the video at a specific part of the motion timeline- the video/gif autoplays at 0s regardless, which makes it very difficult to control how/when a specific part of the asset should render. For example, if I want the video to only start playing 3s in (after an intro screen)- that isn’t possible- the video will be already playing for 3s even though I can toggle its opacity to 0%, but that isn’t useful at all. This becomes more of a problem should I want to work with multiple media assets (e.g. show Video 1 first, then Video 2 later on- that will be virtually impossible without some silly hacks like actually editing the video itself to have a matching duration delay, which isn’t scalable at all). Also, there is n