Share Your Thoughts

It would be helpful if pressing the ESC key could cancel an ongoing drag operation when a user accidentally clicks and starts dragging the wrong object.Currently, the only way to undo this action is to use Ctrl+Z, which adds an unnecessary step. Allowing ESC to immediately cancel the drag operation and restore the object's original position would make the workflow faster and more intuitive.This behavior is common in many other software applications, so users are already familiar with it. Implementing it would improve usability and help prevent accidental changes.

ProblemWhen a layer has constraints set to Bottom (MAX), the constraint only takes effect when the parent is resized. If you manually change the layer's height in the properties panel, the top-left origin is used — the layer grows downward, and the bottom edge shifts.This creates an asymmetry with the Left/Top (MIN) constraint. A layer pinned to the left at x=0 naturally stays in place when you change its width — x=0 doesn't need to move. But a layer pinned to the bottom at y=720 (in a 1080px parent) does need y to recalculate when height changes, and currently it doesn't.Expected behaviorWhen I set a layer's constraint to Bottom, changing its height should keep the bottom edge fixed and grow upward (y = parentHeight - newHeight). The same logic should apply to Right for width changes.Current workaroundThe only way to achieve this today is to wrap the layer in an auto-layout frame with a spacer above it. This adds unnecessary complexity to the layer tree for what should be a single-pro

Would be awesome to support a Webp file when exporting images like Sketch. (without using any plug-ins)

First and foremost, thank you to the Figma team for introducing animation features it has truly been a game-changer for digital design workflows. As we integrate these tools further into our UI/UX design process, a few key areas in animation management and export fidelity require refinement: Enhanced Animation Layering Control: Improved control over animation layering logic would significantly streamline creating intricate micro-interactions and layered dynamic components. SVG Animation Export Issue (Glass Effects): When exporting icon styles or components with glassmorphism effects (such as background blurs, multi-layered fills, or stroke effects) to animated SVG format, the effect rendering breaks or disappears in the exported file. A fix ensuring background blurs and layer effects are preserved in animated SVG output is essential. Native / Enhanced Lottie Export with Effect Support: Native, full-fidelity Lottie export capabilities—supporting advanced layer effects (shadows, blur

错误：无法复制粘贴 Figma 环境中的交互：Windows，Figma 桌面应用 + Chrome 网页版 问题开始日期：2026 年 7 月中旬 重现步骤：1. 选择具有交互的图层 2.在原型面板内选择交互条目，或点击紫色面条连接器3。按Ctrl+C 4。选择目标图层，按Ctrl+V，结果：交互无法粘贴。它总是粘贴旧的剪贴板内容。预期：复制交互规则并粘贴到目标图层。我尝试过的排查方法包括：• 清除Figma桌面缓存 • 完全退出并重启桌面应用 • 硬刷新浏览器，无痕模式 • 验证浏览器剪贴板权限 • 在全新空白的Figma文件中测试 • 尝试分别选择noodle和原型面板交互行，所有尝试均失败。重要提示：这个bug存在于桌面应用和网页浏览器中，而不仅仅是网页版。

Far too often do I find myself having to change a component or other auto-layout layer between Hug and Fill Frame, and then double click and change its child, ad nauseum. This is very common in tables, where specific cases occur in which a cell component needs to be adjusted a certain way, and I would need to change from fill to hug, for example.It would be an enormous time saver to be able to cascade the sizing option down to all children in a single click. 

I often duplicate existing mocks to work on feature updates. Deleting previous annotations one by one is extremely tedious. It would be helpful if the tool could recognize when a frame has been duplicated and then allow bulk clearing of annotations.

Like many design systems, our current library uses placeholders + instance swap and we would love to switch to slots.The issue: While it’s possible to wrap placeholders in a slot to preserve content in existing instances, that content is no longer preserved when the instance swap property is removed from the original component. As soon as we remove the instance swap property from the parent component, all instances lose their swapped content.This means we have two options:Remove the property anyway and cause major breaking changes to hundreds of projects Accept redundant properties in the already crowded property panel for any component we switch from instance swap to slotsI’d be very happy if we could remove the property, or rather reassign its function to the new slot. 

現在、Figma AI Agent はコメントの読み取り（get_comments）は可能ですが、コメントへの返信（figma.comments.reply）や新規作成（figma.comments.create）がランタイム上では利用できません。デザインレビューのワークフローに関して、コメントを起点に修正を行い、対応内容をコメントに返信する運用を行っています。 現状では修正の実行はエージェントが対応できるもの、コメントへの返信だけは手動で行う必要があり、ワークフローが分断されてしまいます。具体的なユースケース：フレーム内の解決未コメントを収集し、修正方針を策定・実行した後、各コメントに対応する内容を返信する レビュー指摘への対応ログをコメントスレッド内に自動で残す

It would be extremely helpful to have a “Paste In Place” feature like Illustrator does!

Nice work including Typography and Gradients as variables! But I feel like the ability to use a variable for opacity when defining a color palette is missing. Which means the size of my color palette is double what it should be as you have to define each opacity as a separate variable.

Enhancing variables to have extra logic in place so that variables can be partially based off other variables e.g. Number new_variable = “{other_number_variable} + 4” String new_variable = “{other_text_variable} New Text” Colour new_variable = “{other_color_variable}, opacity 4” Boolean new_variable = “not {other_boolean_variable}”

In Figma, I can create a color variable like Primary/500,but there's no way to create another variable that links to Primary/500 with just a different opacity (e.g., 50%).This becomes a problem when I change the base color — I have to manually update every opacity variation, which is time-consuming and breaks the idea of dynamic design systems.🔧 Feature Request:Allow opacity to be applied on top of existing variables when creating new ones.

Please add the ability to add timeline markers to the Motion timeline. Like in After Effects

https://app.weavy.aithe only way i could be 

Hi! Please consider adding WebP to the native export options. It’s widely used for web performance, and relying on third-party plugins or external converters slows down the workflow. Having it built straight into Figma would be amazing. Thank you!

I often work across multiple pages within a single Figma file/project, and I’d love the ability to open different pages as separate tabs in the desktop app—just like I can open different files. Currently, I have to either open and close multiple pages many times to get what I need from other pages, use multiple windows or duplicate the file, which isn't ideal for managing design systems or multi-page projects.This would greatly improve workflow efficiency for designers managing large files or working across different sections (e.g., desktop vs. mobile layouts) simultaneously.Please consider adding support for tabbed views of multiple pages within the same file.

HiI have just used Figma motion for a quick animation and in general it works ok, but I have noticed a few things:Gif export is low quality even it’s set to High. Grey colours show pixelated. I tried to export it at 2x and resizing the file. It does help with image quality but it obviously increases the file size which is the reason for exporting as gif in the first place. Trying to scale or rotate a layer automatically creates a keyframe when I don’t want to, this doesn’t happen with position.  I can’t keyframe component properties, it would be really helpfulIn all, it’s a great addition to figma. However, I have experienced some glitches on the desktop app, I hope having all of this stuff added doesn’t affect overall performance. It seems to improve when I quit the app and restart again.  Thank you.

Would be great if the cursor chat function was enhanced to be able to easily type/add emojis. It’s possible to do so through a MacOS keyboard function but it’s pretty clunky to do it that way.I often find myself wanting to use the cursor chat to show a thumbs up/down or to simply express a quick reaction to something.

Hey There - your ‘squares’ in Figjam are not squares, but squares with rounded corners and not quite squirkles. For all of us who know what they’re doing, please provide full control over all objects so we can create in the way that is needed. Thanks

At the moment, as far as I’m aware, the only keyboard shortcut for switching between different UI modes in Figma Design is ⇧ + D. This toggles between Design and Dev Mode. Where it starts to feel odd is if you’re in Draw or Motion and hit ⇧ + D, it brings you to Dev Mode. If you hit it again, you’re now in Design mode with no keyboard shortcut to switch back to your previously active mode.However, you can switch to Draw via the actions menu, but there is no keyboard shortcut. There is no option to switch to Motion via the actions menu.I propose adding dedicated shortcuts for each mode. Possible shortcut options:Design: ⇧ + ⎋ Escape Draw: ⇧ + W Motion: ⇧ + J or ⇧ + O Dev Mode: ⇧ + D (keep existing shortcut) Cycle mode forward: ⇧ + ~ Cycle mode backward: ⇧ + ~I also think all of these should be added to the actions menu as well. Even better, customizable shortcuts for any actions menu command would be amazing.

Ew. No. 

I have a very distinct first and last name. My Figma profile uses my full name, which is important for our organization-- coworkers and partners in Figma need to be able to easily tag me in comments and see who worked on files. However, I would like a way to have a different display name and handle for the Figma Community. I don’t really want my questions about plugins, etc. to be publicly searchable if someone were to Google my name. I prefer to have a privacy option and keep my professional work and personal online presence as separate as possible.

A feature idea: "Spotlight My Pin." When navigating large Figma files, I often lose track of the area I was comparing. It would be great to right-click anywhere on the canvas and drop a temporary pin to save the current viewport, then instantly jump back to it later. This would be much faster than searching for frame names or manually navigating back across the canvas.