Share Your Thoughts

Hi,I could love to use figma draw but currently can’t since it’s not available on ipad / tablet. I sometimes draw quick prototypes on figjam, and instead could switch the entire prototype workflow in figma. 

Feature Request: Support for hierarchical page structures in the left navigation panel. Currently, pages exist in a flat structure without nesting capabilities.

Figma has been an essential tool for my daily work as a solo UI/UX designer. However, the recent bundling of AI Credits into the Professional plan has significantly increased the subscription cost, even for users who never use AI features.Previously, I was paying around USD 20/month for the Professional plan. After the Config 2026 changes, the cost increased to approximately USD 55/month because AI Credits are now included by default. There is currently no option to disable AI Credits or choose a lower-cost Professional plan without them.This creates a real problem for independent designers, freelancers, and small businesses. We subscribe to the Professional plan because we need features like:Unlimited design files Components and Libraries Variables Advanced prototyping Version history Team collaborationThese are the reasons we pay for Professional—not necessarily for AI.Forcing every Professional user to pay for AI, regardless of whether they use it, feels unfair. Many of us already r

Guys, would be great if Figma consider to add some or all of these features someday: A tab to see all itens from community that we liked, instead of only showing those that we saved; that gives even more meaning and usage to the like button. Have the option to pin the “view community profile” icon that appears on the top left of the app when we open up our community profile. Maybe add some “scrap page/book” so we can say something to the community members on their profiles just like Orkut did back there in that time

Hello Figma Team,I've been a long time Figma user and have relied on it extensively for website design. Unfortunately, over the past year I've found the overall experience becoming increasingly frustrating. Many workflows that were once fast and intuitive now require significantly more effort, and it feels like the focus has shifted away from the needs of production designers.Some of the issues I've encountered include:Copying a layer from one frame to another no longer pastes it in the same relative position. This used to be a huge time saver when working across multiple artboards. Selecting layers has become much more difficult, especially within nested Auto Layouts. I often find myself drilling through multiple layers just to select the object I want. Auto Layout has become overly complex. Small changes frequently produce unexpected results, making simple edits unnecessarily time consuming. Changing layouts, such as moving from a four column grid to a three column grid, often stretc

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

 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

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.

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.

Hi everyone,First off — Figma AI (Agent) has been an incredible addition to our workflow. Really impressed with how well it understands and interacts with design systems. Huge kudos to the team behind it!I've read through the article https://help.figma.com/hc/en-us/articles/38978644498199-AI-workflows-collection-Best-practices-to-help-Figma-AI-understand-your-design-system#h_01KKFV30GE7M7PH1YPBCNXG07W , and while it provides great foundational guidance, I'm finding it hard to translate those principles into a concrete restructuring plan for our own design system. The "what" is clear, but the "how it should actually look in practice" is still a bit ambiguous.We'd love to restructure our design system to fully align with Figma AI best practices, but we're missing a tangible reference to work from. So my question is twofold:Could Figma publish an official example design system file that demonstrates these best practices end-to-end? Something the community could open, inspect, and use as a

AI tools  like Figma AI are definitely changing the way designers work. It'll be interesting to see how this improves productivity and creative workflows over time. I recently came across a helpful resource about modern game UI design that explains some similar concepts. Great update!

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! 🙌

Information beforehand: i use the dev mode, so I have no access to the Motion Timeline to get Tokens.Our company uses the new motion mode to implement animations, and we have a token system to tokenize colors, spacing, and also animation duration etc.I noticed that as a Dev I am unable to see which tokens have been used. The automatically generated code infers the values instead of showing the tokens: The 4px should be a token in this case. I also don’t have a full seat so I am unable to even see the animations in the timeline: Feature Request: I think it would be great to have the option to read the animation here, even if you don’t have full access.Did anyone find a way to circumvent this?

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. 

I discover a functionality in Figma that help me to create animation. It is MOTION, an essential tool that is necessary and useful when you want to create something quickly. However, when I export a creation, the quality is poor as static and when is animated it sends me to a presentation web page, where I can see my design. I want to downloading the animation on my desktop and the quality to be clear. I am delight to know that this problem is taken in account and I am looking forward to this update to be implemented. 

I tried to make a grid with outline rectangles, I have make sure the position of the outline has been set to center, yet the result after I grouped or make them auto layout, the line doesn't well aligned instead it's curving. How to solve this issue?

I’m encountering an issue in Figma Motion.I want to animate a rectangle to grow from its centre (expand equally left and right). However, when I animate the ‘Width’ property, the rectangle always appears to grow from left to right, as if the transform origin is fixed to the left edge.The rectangle is constrained to centre/centre (in the design tab), and there are no auto-layouts applied to the parent frame.Not sure if it’s me or the product? Feels like a pretty basic feature to be missing!Edit: It seems like the origin is set to centre if you manually drag to resize while holding the ⌥ key... not ideal

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