Share Your Thoughts

In Figma prototypes, elements set to Fixed are automatically rendered above scrolling content. This makes sense for common UI elements such as fixed headers, navigation bars, or floating buttons — but it prevents other very common web design patterns.For example, a background element may need to remain fixed while the page content scrolls above it. Currently, this requires workarounds with nested viewport and scroll frames.I suggest separating scrolling/positioning behaviour from layer order, similar to how this works on the web with CSS position and z-index.A simple option for Fixed and Sticky elements could be:Always on top – current behaviour Respect layer order – the element remains fixed/sticky but retains its position in the layer stackThis would make it possible to prototype fixed backgrounds, overlapping sections, layered sticky elements and other common web interactions much more naturally, without restructuring the entire prototype.In CSS, position: fixed or position: sticky 

Hello Figma Support,Please route this maintenance suggestion to the team responsible for the Figma plugin skills distributed for Codex. This concerns instruction discovery and packaging, rather than a Figma document or a demonstrated Plugin API failure.Environment: Codex desktop on macOS. Installed component: figma@openai-curated-remote, version 2.0.21. Observation date: 2026-09-14.In skills/figma-use/SKILL.md, the description at line 3 begins with mandatory prerequisite warnings and puts the actual capability and triggering objects later. In a display with limited description space, the warning is more likely to remain visible than the scope. The installed entry point has 34,998 characters and 435 lines. This is a static discovery concern, not a measured automatic-selection failure rate.Suggested English description:“Create, edit, or inspect nodes, components, variables, and layouts in Figma files using use_figma JavaScript. Read this skill’s API and execution requirements before call

I want to present a full page prototype in Figma Design where most interactions are built in Design, but more advanced sections are built in Figma Make. Today, a Make embed can be shown on the canvas, but not as part of the actual Present/prototype mode flow. I would like Make content to render as an embedded block inside a scrolling Design prototype, so advanced interactions can be presented in context together with the rest of the page.

  Hi Figma team,I'm writing to suggest adding Simplified Chinese as an official UI language. Here's why it matters:1. Huge unmet demandChina has hundreds of thousands of UI/UX designers and an even larger number of PMs and developers who collaborate in Figma daily. Many currently rely on third-party Chinese localization plugins, which frequently break after Figma updates and pose security risks. An official solution would immediately serve this massive user base.2. Competitive pressureLocal competitors like MasterGo and JS Design (即时设计) have captured significant market share in China largely by offering native Chinese interfaces and local server infrastructure. Official Chinese support would help Figma defend and grow its position in one of the world's largest design markets.3. Better cross-functional collaborationFigma's core strength is real-time collaboration across roles. In Chinese product teams, PMs, engineers, and stakeholders often have varying English proficiency. A native Chi

This has been mentioned here: Hide layer using variables - #5 by Andreas_Braendhaugen1 Invert boolean variable for layer display - #14 by Desislava_Slavkova Inverted Boolean Property - #2 by drewcovi_usb but those topics are all closed. I am looking for the availability to HIDE a layer when a Boolean variable is TRUE and SHOW it when it is FALSE. So, the inverse of the default/current behavior. I want to do this without using components. Use case: When a variable is true, show one frame. When that same variable is false, show a different frame. I can get basically this by using two different variables: but it would be more convenient to be able to do it with just one. Just give me a Boolean toggle when the variable is used to say if the variable should be inverted or not.

Hi, where I can find the prototype mode in this new UI? and also the absolute position in auto-layout is also missing?

For an product I’m working on, the design team has a system used by all designers. We hand-off designs both in english and arabic. So all components and pages need to support switching the initial english (left to right alignment) design to arabic design (right to left).Currently, I handle this in the following way:English font is [x] and arabic font is [y] → add the font names as typography variables to switch between Text direction, english [ltr] and arabic [rtl] → manually handle or use a plugin like RTL layout Components for english [ltr] and arabic [rtl] view → eg list, checkbox, header → add layout direction variants to change multiple elements direction to right for arabicThe problem with all of this is that it’s a lengthy process which is not scalable. The ideal solution would be that when a language is identified and set as a property/variable/setting, then on each element/frame figma smartly set the right rtl expectation → text direction right aligned, set font and it’s sizin

Proposing (but might just be me)I use the Paste to Replace shortcut a load. It’s one of those little but massive time saving shortcuts.  However, the shortcut Shift+Command+R is very close to Shift+Command+T (Open Recently Closed Tab). So I keep opening tabs which annoys the dooky out of me. I don’t know whether opening a previously used tab is such as common action that it deserves a hotkey. But if so perhaps it can be Shift+CTRL+Option/Alt+T.  Dunno. 

Hey guys, I want to share this idea.I work with different companies that, for NDA reasons, each want me to use their own email and account. So I need to switch between accounts all the time.The situation is that Figma is great software, I love it, but regarding user accounts, it's a total mess.Maybe instead of adding an account to the app and creating confusion by having multiple files open from different accounts at once, a simpler solution would be to let users open another Figma instance.That would be helpful to drag and drop between windows and share some components between different projects.

I’d to request support for using variables within prototypes for animation properties such as duration and easing. We’re working to systematize motion in our design system, and the ability to define duration and easing as variables would make motion much more consistent and reusable across files and teams. This is important because these values are foundational to how motion feels in the product, and they should be treated with the same level of structure and control as other design tokens. Right now, there’s a disconnect between how motion is defined in code and how it’s represented in Figma, since animation values can’t be managed in the same systematic way. Supporting variables for prototype animation properties would help bridge that gap, improve alignment between design and engineering, and make motion easier to maintain at scale.

Hey Figma team and community,Is there any chance we could get native support for WebP and WebM exports anytime soon?Right now, exporting web assets feels a bit outdated. We’re still relying on giant PNGs or super heavy GIFs, only to manually run them through external conversion sites before sending them off to dev.Having native WebP for crisp, lightweight images and WebM for smooth UI video clips (especially with transparent backgrounds) would be a massive quality-of-life upgrade. It would make the design-to-code handoff so much cleaner.Upvote if you’re also tired of using 5 different file converters every day!

It would be helpful if the playhead snapped to time increments as well as existing keyframes. Right now, it’s difficult to position the playhead precisely when editing because it’s not clear whether it’s aligned with the intended time.

It would be amazing if there was an advanced clipping option that would allow designers to choose what edges clipped content and what edges let content run over it. I am working on complex enterprise software where I have dropdown menus with menu items with hover states as well as icon buttons in the menu items with their own hover states. And on top of that I need to show tooltips on some of the icon buttons and allow clicking to open a new modal. (There is a lot going on) We have workarounds for the overlay tooltip but the issue we’re running into is everything is in a scrollable container and that requires clipping to look decent. It would be nice to decide what edges get clipped. In our scenario we need clipping at the top and bottom of the scrollable container but the left and right don’t need it so that absolute positioned items can spill outside of the scrollable container.

It would be nice if I could quickly open pages in my design file in a new tab. Often pages contain designs that would be useful to view side by side with the current page you are working on. It would be nice if I could quickly open them in a new tab / new window instead of having to go back to files, open the file, wait for it to load and then navigate to the page.

Realized when going back to a Tool that I subscribed to that there’s no way for me to pin it or save it anywhere for quick access. The only mechanism seems to be Recents. Seems like a total miss here. Way too many tools to assume Recents would be suffice.

Feature Request: Git-like Version Control for Figma BranchesCurrently, Figma allows us to create a branch from each file, but this limitation makes it difficult to manage complex design workflows — especially for teams working on large design systems.Git-like branching would make version control in Figma far more powerful and flexible. With this approach, designers could create multiple branches from existing ones — functioning much like environments (e.g., test, staging, production) in development.Attempt at elucidating through a flow diagramAs a design system maintainer, this would be a huge benefit. For example: Components that need additional review or testing could be safely designed in separate subbranches. Compatibility between different branches could be tested before merging changes into the main file. It would reduce merge conflicts and ensure higher quality and consistency across the system before releasing updates. Allow for other users to expand on branches through t

The gapVariable mode inheritance only works within a single collection. A mode cannot be derived from anything: not from a variable, not from an alias, not from a component property. This means that in any composed component, the mode of a nested component must be set by hand on every instance. Concrete caseAn Alert has two sizes, driven by modes in an `Alert size` collection. It contains a Button and an Icon, each with their own size collection. What I need to express is a mapping:| Alert size | Button size | Icon size || --- | --- | --- || small | Small | 14 || large | Default | 18 |There is currently no way to state this relationship anywhere in the file. Setting the Alert to `large` leaves the nested Button at whatever mode it happens to carry. Why the existing workarounds don't hold upOne shared collection.This requires the scales to align on two axes. They don't. My icons have five steps (12/14/16/20/24) and my buttons have three (Default/Small/Large). Forcing both into one mode

It would be great to have an option to save filters in the Recents tab.Every time I open Figma, I have to manually filter my files to show only Design files. I’d like Figma to remember my filter selection, so that it persists after restarting the app or reopening Figma.

Would love it if you could paste a screenshot or image into a sticky note.It’s obnoxious to paste an image onto the whiteboard, move it to align with a sticky note, and then group the two elements together. Takes more time than it should :(

The default settings (at least in my Figma) load a percentage for letter-spacing, but this is not allowed in CSS. For a less avid programmer this may be confusing, when trying to get it to work. Either set the default to a px value, or add a warning inside the Inspect code

new AI agent “describe your idea” icon/text box feature when i click on an instance/frame in my design is a bit intrusive - little star icon gets in the way when i’m trying to adjust my design manually. maybe limiting it to the right click menu or simply creating a new hotkey would be better? also, telling this agent what to do is a miserable experience that usually just frustrates me back into doing the design myself as it is literally faster than typing it out. have seen a lot of feedback similar to this as well here.

Figma is no longer used only by designers and developers.In many real-world projects, designers share Figma files or prototypes with external stakeholders such as clients, managers, marketing teams, legal teams, and other non-design users for review and approval.These viewers did not necessarily choose Figma themselves, and many of them may not be familiar with Figma or comfortable using an English interface.This creates unnecessary friction in the review process.The intended journey should ideally be:Open shared link → Review the designBut in practice, it can become:Open shared link → Understand an unfamiliar English interface → Figure out how to navigate the prototype viewer → Review the designThere is another common scenario where this becomes even more problematic.After a client receives a prototype or shared file, they may need to share it with other members of their internal team. At this point, they have to interact with Figma's sharing interface themselves.This interface involv

When overriding a single element inside a slot in a component instance, Figma marks the entire slot as overridden. As a result, updates made to the main component no longer propagate to any elements inside that slot — even if only one element in the slot was actually changed. Expected behaviorOnly the modified element should be treated as overridden.All other elements inside the slot should remain linked to the main component and continue to receive updates.

Hello,When a user holds both admin and regular user roles on Figma, notifications get mixed together: license requests, AI budget overages (admin) and comments (user) all appear in the same feed, which makes them hard to read through.We currently have 3 tabs: All / Request / Unread.Would it be possible to add a dedicated tab or filter for comments, so that admin-related items (license requests, AI credits) can be clearly separated from day-to-day usage items (comments)? This would make it easier to prioritize and ensure nothing is missed depending on the context we're reading in.Thank you in advance for your feedback on the feasibility of this improvement.

Allow designers to create an AI-powered project space where the agent can use project-specific sources and default memory to understand the design context.Designers can upload or connect sources such as brand guidelines, design systems, UX documentation, product requirements, or tone-of-voice guidelines. The AI agent uses these sources as the primary context when generating, reviewing, or modifying designs.Inside the AI agent panel, designers can configure the project's context and choose which sources the agent is allowed to use.Example ScenarioA designer creates a Nike Brand Campaign project in Figma.They add:Nike brand guidelines Typography guidelines Color specifications Logo usage rules Brand voice guidelinesThe designer then sets the AI Agent's project context to:Sources✓ Nike Brand Guidelines ✓ Project Design System ✓ Default Figma Memory ✕ Other ProjectsThe agent can now generate or critique designs based specifically on the selected project sources.For example:"Create a campai