Suggest a Feature

Hi Figma team and fellow designers!I would really love to see native video export (MP4/MOV) become a feature in Figma.As a graphic designer, I use Figma extensively for everyday advertising production, including Google Performance Max, Meta ads, display banners, and digital campaigns.Honestly, I find Figma's interface and workflow better than any other design tool for this kind of work. It's intuitive, flexible, and makes managing multiple formats, sizes, and creative variations incredibly efficient.I know many other graphic designers who use Figma in exactly the same way, beyond UI/UX design.The one thing that's missing is the ability to export animated designs directly as video files. Currently, having to move designs into another application just to produce an MP4 interrupts an otherwise seamless workflow.It would be fantastic to have: Native MP4/MOV export Basic timeline and animation controls Frame-based animation and transitions Export options suitable for social media and

When I published a batch of changes to my component library, one component had a property error (only when I select the component I can see the exclamation mark after the property). Figma skipped it by default, but nothing told me its changes weren't published. I only noticed the error after I selected that component (even just select the component set, not the instance or the variants).That led to a confusing situation:I assumed everything had been published. Instances in the consuming file kept the old text variable bindings. If I copied an updated instance straight from the source library, it had the right bindings, but accepting the library update changed it back to the old ones.It looked like a library sync bug, but the real cause was a skipped component that was easy to miss.What would help:Show a warning at the publish entry point, like "3 components have changes that can't be published", and make it look different from "No changes to publish". In the publish panel, list the ski

Figma's current branching is a bottleneck. All branches must come from main.If one designer is working on Feature A (v1.1.0) and another is on Feature B (v1.2.0), the designer on Feature B cannot get updates from Feature A. They are blocked until Feature A is fully merged into main. This forces designers to either wait, or manually copy-paste work, which breaks components and causes errors. The Solution: We Need Git-Style Branching To fix this, we need three features that developers use in Git every day: Branch from Branch: Let me create a new branch from any existing branch, not just main. Update from Branch: Let me "update" my branch by pulling changes from any other branch (e.g., merge Feature A directly into Feature B). "Cherry-Picking": Let me select specific changes (like a single component update) from another branch and pull just that one thing into my branch. This would unblock designers, stop manual copy-pasting, and allow teams to work in parallel safely.

I've recently started trying out Figma Specs for writing PRDs alongside my designs. I really like the direction this is going. Having requirements and designs in the same place could save a lot of time, especially when working on complex enterprise products.After trying it out, there are a few things I feel are missing.1. A table of contentsThis is the first thing I noticed. Specs supports headings, but there's no document outline or table of contents, even in full-screen mode.For a longer PRD with multiple sections, it's difficult to navigate without scrolling through the entire document.It would be useful to have a collapsible sidebar that automatically lists headings and lets you jump between sections.2. Revision history and change notesPRDs change frequently during reviews and development.I'd like to be able to add a short note when making changes, explaining what was updated and why. It would also help to compare versions, see who made changes, and restore an earlier version when

Currently, if you copy + paste a figjam flow into a Design file, the Connector Lines stay fully functional – they stretch and adapt as you move their origins and destinations around the canvas, and you can move their origins and destinations to your frames, components, etc. I’ve been using this to show user flows within my UI designs, not only for ease of sharing with other teammates (no need to give in-depth walkthroughs), but also for easily identifying missing states within a flow. It would be great if a) the Connector Line was added as a tool to Figma Design, or b) basic lines and pen vectors had the option to act as connector lines – attaching to anchor points on objects and components, scaling when the endpoints were moved, and able to be adjusted with mid-line handles.

It would be really nice if I could pop out the variables into their own window. Currently I can only have it as a dialogue in Figma, which means it always overlaps over my design and especially on smaller screens this becomes quite the issue. I often need to see variables and my design at the same time, so moving it to a second monitor (or even on a laptop quickly switching with alt + tab between the two) would be very helpful.

90% of the time i use custom stroke borders is for sides / top & bottom strokes but it is slightly finicky to use and would be faster if it was just an option so I can do it much faster.  

Why not let people attach comments and annotations to any element in specs, the same way they do everywhere else in Figma? It would make collaborating around specs more natural, and it could give AI better context too.I framed this as a “what if,” but it’s a pain point not having the comment/annotation sticky.Best regards

There are keyboard shortcuts for most text adjustments, size, wieght, line height & letter spacing. But if you’re working with set text styles any adjustment breaks the style. Often I find myself needing to bump text styles up or down in size, having to select te correct text styles is unnecessarily complex. I tried creating a custom plugin for cycling up and down in the predefined text styles, it works, but requires setting API access and manually adding keyboard shortcuts via system settings. So my suggestion is to add a native shortcut to cycle up and down in the predefined text styles with Control + Option + ⌘ Command + > and Control + Option + ⌘ Command + <

I really enjoy using Figma's AI Agents. One improvement I'd strongly suggest is an AI credit estimator: before running a request, the agent would show roughly how many credits it expects to use, and I could approve or cancel it.Recently, a quick request ended up costing me 2,298 credits for a single question. If I had known the cost up front, I would have changed or narrowed what I asked for.This could live right in the AI Agent panel. It wouldn't need to interrupt every request. It could ask for approval only when a request is expected to go over a set amount, such as 100–300 credits. Even better, users could set that threshold themselves, or turn the prompt off entirely.This would make credit usage more predictable and help me use the agents with more confidence. Thanks for considering it!

We have a design system set up with tokens (variables) to enable all components to switch between light and dark mode. For developers/viewers to see what a screen should look like in Dark mode, we have to duplicate that screen. But as an editor I can set the colour mode variable at the Page level to Dark and all screens on the canvas/page turn to dark mode. If developers/viewers could also do this, I could delete the dark mode duplicates of every screen and only have one copy of each screen, defaulted to light mode, and then just toggle dark mode as needed. This would be much more efficient on memory usage and maintenance.

Please, for the love of God, add a keyboard shortcut for superscripting and subscripting. When I copy legal text over from an outside source, the superscripted trademark and copyright symbols do not carry over as superscripted. It is tedious to have to redo this in Figma and open the menu every time instead of using a keyboard shortcut.

We would like to have a programmatic integration with Figma via API, with our cost accounting systems.  We'd like to be able to pull all the members of a billing group, along with their seat license types.  Very much like the CSV download that is currently available via the UI, but we're trying to avoid "click-ops"

As per this discussion - How to disable 'observe' mode - #5 by Dave2 - I think it would be useful to be able to turn off ‘observe mode’. It is very annoying being watched while I work, unless I specifically am trying to share/demonstrate something. It is the digital version of someone looking over your shoulder. I dont want to have to remove people’s permissions from the file just to stop them digitally stalking me.

We have an enterprise workspace and organise client work into teams to control access. There are 40+ teams, and they were named using an old system, and I want to update the team names to the new system, but there is no easy way to do this. It would be great if there was a bulk rename feature, or even a way to rename teams without having to open each one individually and then double click the title and make the update etc.

Hi! I’m trying to create an “author credit” component to document a design system. The component has a link to the original resource. All text will be set using component properties. Is it possible to create a property so the link URL is filled in the instance instead of using overrides?

Hey there,  we often Work with Images directly on our Boards (I bet most of you do). So if I want to create an Image Fill for a Frame, why can’t I just select the Image from the board (as we can do for Pattern Fills) instead of Uploading it or making one? Would be a very helpful Feature! Best From Austria.

Our team uses Codex with Figma to build and maintain a shared component library. Multiple designers work with their own agents, each with different tasks and context. Developers may also have their own coding agents working on the corresponding implementation.We can already see other collaborators’ agents and their working status in Figma. That made us wonder: could these agents collaborate with one another around shared design assets, with their owners’ permission?The gap we encounterAn agent can inspect a shared component, but it may not know why another designer made certain decisions, which business constraints apply, or which questions remain unresolved. Today, we have to copy context and questions between separate conversations, relay the answers, and reconcile the results ourselves.A workflow we would find useful1. A designer’s agent updates a component and shares an approved brief describing the goal, changes, constraints, asset version, and open questions.2. Another designer a

I am using Figma from almost 2 years. It’s a great tool. Previously I was using Windows 10 yet recently switched to Linux(Ubuntu). Figma doesn’t have any official release for Linux. There are some Unofficial desktop versions but they are “BUGGY”. I request you guys to release an official Figma desktop app for Linux.

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 everyone,I'm using Slots in my design system and noticed that the AI "Rename layers" action never renames layers placed inside a slot. It skips them completely, so I end up with "Frame 427", "Frame 428", "Text"... inside every slot.Steps to reproduce:1. Create a component with a slot (e.g. a Card with a "Content" slot).2. Insert an instance and add a few frames and text layers into the slot (keep default names).3. Select the instance (or the layers inside the slot) and run Actions > Rename layers.Expected:Frames and text layers I added inside the slot get renamed, like any other unnamed layers.Actual:They are skipped. If I select only the slot content, I get "No layers need renaming".I understand why this happens. The Help Center says Figma AI won't rename layers nested within an instance, and slot content technically lives inside the instance tree. But slot content is different from instance sublayers: it's content I added myself, not the component's internal structure. It shoul

Dear Figma Support Team, I am writing to inquire about the current support for color fonts in Figma. As a designer, I greatly appreciate the versatility and creative possibilities that color fonts bring to my work. I have recently been experimenting with various color font formats, such as OpenType-SVG and COLR/CPAL, which allow for intricate multi-colored typography. However, I have encountered some challenges when attempting to utilize these fonts within Figma’s design environment. It appears that Figma currently lacks full support for color fonts, as I have experienced difficulties with the proper rendering and editing of these fonts within the platform. It would be immensely beneficial if Figma could extend its capabilities to fully embrace color fonts, enabling designers like myself to fully explore the potential they offer. Color fonts have become increasingly popular, allowing for more expressive and engaging designs across various mediums. With their ability to incorporate vibr

Layout grids currently can’t be bound to variables, so building responsive grids means maintaining a separate grid style or manual override for every breakpoint.Request: Allow layout grid properties (column count, gutter, margin, offset, and column width) to be bound to variables, with support for modes.Why it matters:Column counts and gutters could switch automatically when a frame’s variable mode changes between breakpoints (e.g., Mobile = 4, Tablet = 8, Desktop = 12). It would make the grid part of the design system, driven by the same tokens as spacing and sizing. It would reduce duplicated grid styles and make updates easier to maintain. It would align Figma more closely with how responsive grids are defined in code (CSS variables and media queries).Expected behavior: Selecting a grid column property shows the variable picker, just like other numeric fields. Changing a frame’s variable mode updates the grid immediately.