Suggest a Feature

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?

Hello, it would be nice to have the option to insert floating components inside text (like Emojis). Use case would be for signs or infos in complex dashboards. Its a hustle to do this now manually and also set kind of boundingboxes to sync different heighs of text and component. Regards

Hello,some feedback from my side regarding Folders, I like the options of a nestable folder, but I find it hard to navigate to the files I’m looking for. The folders are named, but the file thumbnails that were visible with Projects were a huge readability feature that I’m really missing now.I was searching for it in settings, but couldn’t find a way to set it. I actually added a description to a folder, but did not actually see not one place that the description was shown? This part is especially confusing.If I could make an improvement suggestion to a current implementation it would be to have a setting to show or not to show some folder contents thumbnails, similar to the previous implementation.Fingers crossed this can be done!

The current seat upgrade request process does not provide users or organization admins with enough information to make informed decisions or manage temporary seat requirements efficiently.Three improvements would make the process more transparent and significantly improve license governance: Make the request explanation mandatory Users requesting a paid seat upgrade should be required to explain why they need it. The request should not be submitted if this field is empty.Ideally, the mandatory explanation would cover: The project, client, or internal initiative The functionality for which the seat is required The relevant team or responsible project lead This would give admins the business context required to assess the request and reduce the need to contact users individually for clarification. Explain seat functionality and cost implications The upgrade request interface should clearly explain what each available seat type enables before the user selects it.For every seat type, F

It seems that previously link previews were updated in slack to show what was being shared instead of the entire canvas. I missed that and now my links are just links, no preview. Which is better than previewing the entire canvas still.I have the same suggestion for link previews in Teams. Please stop showing the entire canvas in Teams previews and either show just what is being shared, or just don’t show anything.

It’s 2026, why are links (especially figma file links) being pasted as plain text? Notion and tools similar to it show a stylized container/preview by default when a link is pasted, with the option of a hyperlink or plain text link. Not having it in Figma Design is one thing, but not having it in Figjam feels especially lacking.

Organization admins currently have no direct way to send an organization-wide message to all members and guests from within Figma.For larger organizations, admins regularly need to communicate important information about topics such as: Changes to SSO, email domains, or login requirements License and seat-management updates File migration or account consolidation New governance policies, libraries, or templates Planned training sessions or administrative deadlines The current workarounds are to copy users’ email addresses from the People page and communicate through an external email tool, or to create a user group and mention it in a file comment. Neither option provides a reliable, centralized communication channel for organization administrators.It would be helpful to introduce a “Send announcement” feature within the Admin dashboard. Ideally, organization admins should be able to: Send a message to all organization users Choose between members, guests, or both Target re

Cannot use numerical emojis 1️⃣ 2️⃣ 3️⃣, these emojis are very useful in article typesetting, hope to receive support.

I’ll be straightforward and concise here, as you’ve probably seen in the title. My idea is to have a new option for the Frame size, where it resizes to fit the device screen. The options would include ‘Resize Height Only’ , ‘Resize Width Only’ , and ‘Resize’ (which adjusts both height and width). This feature is useful for testing responsiveness across different devices and platforms (such as mobile apps and desktop). You’ll find this option in the prototyping tab alongside ‘Custom Size’ . Perhaps we could call this option ‘Auto Size’ . Resizing only the height or width is beneficial when the page has vertical or horizontal scrolling.

# Expose stable component identity for instance swap properties in parserless Code Connect ## Problem When using parserless Code Connect templates, `getInstanceSwap()` returns an `InstanceHandle`whose `symbolId` represents a file-local component node ID. The same library component can have multiple local aliases in a consuming Figma file. For example,one icon may appear under these IDs: ```text5:154       Library component ID11221:2421  Local alias12041:6322  Another local alias``` Although all three represent the same library component, Code Connect only exposes the local`symbolId`. This makes it difficult to translate an instance swap into framework-specific code: ```tsconst icon = instance.getInstanceSwap('StartIcon');const iconName = iconsBySymbolId[icon.symbolId];``` A manually generated mapping must currently: 1. Download the source library and consuming Figma file.2. Match components using their stable component keys.3. Discover every local alias for each component.4. Generate a

Every time I exit Figma and come back, the previously selected sort order is lost, and it defaults to "Last modified" – "Newest first". Previously, the selected sorting option was always preserved.

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

Figma Motion is spectacular, but as a new tool, it still has a few workflow gaps.One I’ve encountered is that once an animation contains several layers, the timeline becomes difficult to scan because track order is fixed.I mocked up a concept that would let you drag tracks up or down in the Motion panel, similar to reordering layers, without affecting visual stacking or animation timing.The change is purely organizational. It would allow designers to keep related tracks together, make the timeline easier to read, and simplify working through complex animations.Here’s a quick animated mockup of the idea. Would this improve your workflow?  

Hi, the checkbox “Show in exports” in the “Fill” section is not controllable yet from the plugin API. It would be great if this can be exposed via plugin API so it can be automated in plugins. This would also allow Figma Assistant to use it, it currently can’t. My real world use case would be in automating tasks surrounding icon libraries. Thank you! 

Figma Motion introduced the ability to set the anchor point (origin) of elements, but this property is not reflected in prototype mode. In prototype mode, the defined origin is ignored. Quick win: make prototype mode recognize and use the element's defined origin to rotate them correctly.  

I would really like to have the option of adding more than one tag to an annotation. For example now i’m adding QA annotations by categories, but I would also like to add another tag for each one which states the urgency of the annotation.  Two more options that might work are either adding a fill color option to the annotation, or add a customizable status drop down to each annotation. 

Love the new Typography Variable release, but it falls short for our use case. Our goal is to use variable modes to switch styles between our 3 brands. 2 of those brands use all caps for headings, the other brand uses sentence case. We need to be able to bind a variable to the case of a character style (As typed, Uppercase, Lowercase, Title case, Small caps). Without this capability, when switching modes from brand 1 to brand 2 for example, we are getting the default case for the character style (sentence case coming from brand 1). We would then have to go through our designs and manually type in all caps for all instances of headings in brands 2 and 3. Certainly not ideal and will lead to inconsistencies / places where manually typing in all caps are missed if we went this route. Until binding a variable to the case of a character style is an option, using typography variables isn’t feasible for our use case.

Description: Currently, Figma allows switching between different Modes (e.g., Light/Dark) within a single variable collection. However, there is no built-in functionality to switch between entire Variable Collections dynamically. This limitation makes it challenging to manage multiple themes efficiently, especially in large-scale design systems where different themes (e.g., Default, Gaming, Minimal, Custom) share a common structure but require separate sets of values.Proposed Feature: Collection SwitchingWe propose adding an option that allows users to switch entire Variable Collections in the same way they can switch Modes. This would enable designers to define multiple themes and toggle between them seamlessly without needing to manually update Aliases or duplicate components.How It Would Work:Collection Selector: Similar to the Mode switcher, users can select a Collection (e.g., Theme 1, Theme 2, Custom Theme) from a dropdown in the Variables panel. Automatic Updates: When switching

Firstly great job Figma Font variables are here!!! Figma tutorial: Variables for typography The only thing missing is the use of percentages in the line-height property. You can not use a percentage in the line-height as it only accepts variables that are a number type. Although the variables for line-height caters for pixel (absolute) line-heights (10,12,14)- it does not accommodate relative line heights. In other words you can’t use percentage variables for line heights that are a percentage of the font size (100%, 120%,150%). Interestingly …You can use a variable for letter-spacing ( which accepts a number variable - but reads it as a percentage) - the challenge remains that line heights by default are absolute not percentages - even though you can input a percentage. Percentages allow greater flexibility and less calculations Word around would be to allow formula in a variable e.g. =[variable] * 1.5 Or figuring out a way for the line height to be toggle between absolu

Hello Figma Community 👋I wanted to raise a question regarding the monthly AI credit system and also share a suggestion that could benefit many users.Currently, on the Professional plan, we receive 3,000 AI credits per month, and as confirmed by support, unused credits reset at the end of each billing cycle and do not roll over.However, in real-world usage, credit consumption is not always consistent every month. Some months require heavy usage, while others involve lighter workloads depending on project timelines.📌 Example Scenario:Month 1: Allocated credits: 3000 Used credits: 1800 Unused credits: 1200 (expired) Month 2: Project demand increases Required credits: 4200 Available credits: 3000 only Result: Need to purchase extra credits, even though unused credits expired in the previous month.This makes planning usage difficult, especially for freelancers, small teams, and agencies where workloads vary.

Hi Celine- Are there any plans to remove this constraint? We have container frames with a handful of separate screen specs in them and would like to designate certain screens as ready, but not the entire set. It’d be great to not have to have the frame or instance top-level, but allow nesting and still mark contained elements ‘ready for dev’. Thanks!

My team and I are currently having the inconvenience of having to publish our library every single time we make even a small change (like a font size increase, color change, etc.) and then switching to the working file and manually updating the library. Due to the nature of the project we do this quite frequently and having to publish – switch file – update every single time to see the changes in our designs turns out very time consuming if you add it up. It would be amazing if Figma could integrate a shortcut for automatically updating a library and automatically updating the files it is being used on (like a cmmd+S shortcut!), of course not everybody might want to have this so it would also be nice to be able to turn this shortcut on and off.

You can currently set multiple stroke colours to an object, but they will share the same properties (thickness, position, etc.). My idea is that you should be able to set all stroke properties on each stroke: Make sense or am I missing something?

When I started sharing AI Skills with teammates, I expected teammates to be able to edit a published AI skill and republish their changes without requiring the original owner to make every update.Problem: published skills are shared for use, but ongoing maintenance is blocked when only one person can update the source skill.Impact: this slows iteration, creates ownership bottlenecks, and makes shared team workflows harder to manage.Desired behavior: teammates with the right workspace permissions can open the published skill in Manage skills, edit it, and use Publish changes to update the shared version.