Suggest a Feature

Figma: If you’re used to working in another design tool, you may find it strange that your text styles in Figma don’t include traits like color or justification. Although it could take some getting used to, hopefully the benefits of this approach will quickly become clear. Well, no it didn’t. And strange indeed. In addition to getting used to, it takes a lot of time to to change the color every single time I create a new text element, because our text color is not black. Having a default color saved with text styles would be SO. MUCH. EASIER. I see no reason why the color can’t be in there and also be changed when using the style, if necessary.

Is there any plan to be able to create the gradient itself as a variable? For example, if I wanted some themes to have a solid background variable but others to have a gradient?

It is possible to make the Who can view setting default to only show people in my org. Having it default to Anyone on the web makes it easy for people to make public concepts they shouldn’t

Of course it is easy enough to lock layers but I think that it would be helpful to be able to lock pages in a fashion similar to the layers. I often place root (master, main, og?) components on a separate page and it would be nice to be able to lock these pages to keep items from moving around without intention.

Can we submit a feature request for Figma to improve its PDF export settings?Currently, PDFs exported from Figma are very large in file size, and end users are unable to use editing tools. I need exported PDFs to remain searchable and editable for legal needs, which is not functioning well in the current format.Additionally, it would be helpful to export multiple pages without relying on a plug-in. Having to use a plug-in adds an extra step to the process.Adobe XD generated smaller, cleaner PDFs that preserved searchability and edit functionality. This is one feature I genuinely miss from XD.

As a freelancer, I often need to share files with developers, however, not all clients have a paid account and I don’t want to have to pay for a new seat for every developer who needs access to Dev mode or ask my clients to pay for Figma.

Chad Bergman announced in November 2025, during the Schema by Figma 2025, that the Figma tokens export is “completely aligned with the design tokens specification.” However, we later discovered that most composite tokens such as typography, gradients, and shadows are not yet supported, despite being in the stable revision of the specification in Design Tokens Format Module 2025.10.No clear future plans or roadmap for the export feature were communicated during the conference, which leads us to believe that we won’t receive any updates until the next keynote.Is support for composite token export planned in the near future, or do we have to stick to third-party plugins for now to obtain production-ready design token exp

Hi everyone, Are there plans to support native JSON import/editing for variables and text styles, similar to what Token Studio does?One concrete use case: generating a full typographic scale (with sizes, line heights, naming etc.) from a structured JSON and importing it directly into Figma. Right now, creating or updating a large scale manually can be time-consuming and error-prone. As more teams generate tokens programmatically (and increasingly with LLMs), being able to automate the insertion and update of variables and text styles natively would save a significant amount of repetitive setup work. Is this something being considered for the core product?thanks in advance </3

Currently in text styles, we can assign variables to nearly all values except for list spacing, is there a reason for this?

As written in the documentation (Prototype interactions and animations) the destination of a Scroll to action can only be an element of the same top-level frame. But with this limitation it is impossible to prototype a common navigation pattern. On one-pagers there are often floating menu for intrapage links. E.g you have an hamburger icon that opens a menu overlay from where you can scroll to a specific page section. This can’t be realized with an Figma overlay because of the restrictions mentioned above. There is a workaround, but it seems that it only works because of a bug: You can set the menu overlay as an child of the top-level frame of the one-pager, define the Scroll-to actions and then move the menu outside the frame (as an separate top-level layer) to show it later as an overlay. By doing this all the Scrol

Hello, I have a student (education) account on Figma, which should include all the Professional plan features. However, the option to enable Figma AI tools in the team settings does not work for me. Does anyone know if AI tools are available for education accounts, or how I can properly enable them?

Hey! How can I transfer the AI generated Prototype in Figma Make to Figma Design and continue editing it manually there?

I have been extensively using Figma Make for iterative AI-driven design exploration and observed a workflow-level limitation that may benefit from product consideration.During extended usage across multiple prompt iterations, there is currently no structured mechanism to manage or track AI-generated outputs in a systematic way. Specifically, there is no built-in version control or branching model that enables users to:• Track prompt-to-output evolution• Compare multiple AI-generated variations side by side• Branch or revert iterations in a structured manner• Maintain continuity across sessionsIn complex exploratory workflows, this creates cognitive overhead and reduces efficiency when managing multiple variations or refinement paths.Steps to reproduce: Generate multiple outputs using iterative prompts in Figma Make. Attempt to compare, branch, or revert earlier variations. Observe the ab

Variables are missing for Effects like drop shadow, inner shadow, blur, and background blur. They should be used for the number fields and colors, so we can have dynamically applying themes and sizes for these effects.

As a design system team, we want the ability to trigger a plugin or widget callback when a user detaches a component instance from a library. This would allow us to collect contextual feedback at the moment of detachment, helping us understand why components are being detached and improve our libraries accordingly.ProblemFigma's library analytics already surface quantitative detach data (which components are detached, how often, and by whom). However, there is no way to capture the qualitative reason behind a detachment.Was the component missing a variant? Was there a bug? Did it not fit the use case?Currently, the only workaround is building a plugin that monitors documentchange events and attempts to infer detachments from node type changes. This approach is:Fragile — there is no reliable, documented way to distinguish a detach from other structur

In Dev mode, sometimes the effects designed by the designer are not suitable for the developer.The developer may only need a cutout that contains a part of the layer or effect instead of the full cutout.But in Dev mode, there is no function to hide the layer or effect (small eyes), which will result in the designer having to deal with the extra layer repeatedly every time.

Figma should let local variables override external variables of the same name, just like CSS. For example, if a component uses primary-color from an external file, I should be able to override it in my local file by creating a variable with the same name and modes. This would make working with external components and theming far easier.

I've been using the Figma MCP server with Claude Code to build a design-to-code workflow, and I've hit what feels like a significant gap in the `generate_figma_design` (html-to-design) capture tool. I'd love to see this addressed and wanted to share the use case in detail. The current behaviorWhen generate_figma_design captures a rendered web page, it converts everything to raw Figma geometry — frames, rectangles, and text nodes. Even if the page is built entirely from your published design system components (Button, Tag, Checkbox, etc.), and even if those components have Code Connect mappings configured, the capture output has no awareness of them. You get a pixel-faithful snapshot, but it's "dead" — no component instances, no variable bindings, no variant properties. The gap this createsCode Connect already establishes a bidirectional relationship between Figma components and code componen

Currently I have an improvised bridge to give me the ability to  ‘create_frame’ from inside my IDE via MCP.However this requires a local server and a Figma client running a custom plugin, which is not suitable for use in a pipeline.I would like to have write access from my Claude Code pipeline to Figma Remote MCP but this does not seem to be currently supported. Am I missing something? Is there a published roadmap for the Remote MCP service? 

The Problem: Managing multiple versions of a deck (e.g., External, Internal, Engineering, Operation) is a maintenance nightmare. If one "Core" slide changes, you have to manually update it everywhere.The Solution: Allow users to turn an entire slide into a Component. Master Slide: Stays in a central "Source of Truth" deck. Instances: Placed in various audience-specific decks. Result: Update the Master once; all audience decks sync automatically. Value: This brings Design System logic to presentations, ensuring data consistency and saving hours of redundant "pixel-pushing."

Every time I create a new variable mode, I have to duplicate the full set of variables that already exist in something like light mode or a base brand. This makes it very difficult to maintain and to visualize which variables are actually different for dark mode or across different brands. I’m not updating all the dimension tokens (variables), corner radii, fonts, borders, etc across every single mode.On the engineering side, I like to merge my tokens into the foundation/base token set so that only the overrides apply while original unchanged tokens remain constant across themes and brands. I’m able with more work to modify Figma’s token exports to fit my engineering needs at least. But Figma makes token management very difficult on the design side, which should be the source of truth! ProposalWhen creating a new Variable Mode, let me choose to leave all variables blank and which other mode to merge(

Would it be possible to add a subtle visual and audio notification when someone creates an audio chat? I find that almost nobody realises when this happens because the notification just pops up in the top right-hand corner. 

Next to Prototype tab add a THIRD tab called SHARE:Here we can add BOTH the VIEW/EDIT link + the PROTOTYPE LINKS as panel sections Then we can setup a starting point and also control the permissions of the share links. It doesn’t seem to be an easy way to add these to the FLOWS section, hence adding it as a new SHARE tabIf possible, the share links should also be accessible WITHOUT opening the file in a pop-up dialog maybe with two tabs for View/EDIT and Prototype.

Figma already powers how design is created collaboratively. There is an opportunity to extend this into a public Design Commons where finished projects can be published directly from live files while preserving structural depth.This would not be acting fully as a social feed or marketplace, but a curated, searchable layer focused on structured project publishing and creative collaboration signals.

Context: Currently, when a Figma design file is shared, its entire version history is automatically accessible. If the version history needs to be excluded, the only workaround is duplicating the file and sharing the duplicate — which results in unnecessary file clutter.Suggestion: Introduce an option to control whether version history is shared when sharing a file. This would help keep files organized and avoid sharing internal iterations that aren’t relevant to all stakeholders.