Suggest a Feature

The biggest hindrance I have right now with using Figma Make is the inability to simply chat with the AI and/or make a plan with the AI before it executes changes. From what I can tell, the “Ask to start” setting does nothing different than the other options. I want to ensure the AI has a clear understanding of what I’m asking before it just starts making changes, particularly functional changes to a prototype. For comparison, I have been using Lovable for a while now and use the Plan mode (formerly Chat mode) almost all the time. It draws/writes up detailed plans that ensure alignment between me and the AI. If this is already in development and there’s a way to get early access, I would definitely like to try it. For now, I continue to use Lovable until this functionality is available in Make.

Hi Figma team,I'd like to request a per-account option to disable the AI sparkle (✦) icon that appears when hovering over elements in the editor.Currently, the only way to turn off Figma AI features is at the team admin level, which requires admin access and affects all team members. There's no way for an individual user to opt out of the AI hover trigger on their own account.For users who don't use Figma AI, this icon adds visual noise to the editing experience and can interfere with the workflow — especially when working with dense layers or small elements, where the sparkle icon overlaps with other controls.Requested behavior: add a toggle in user account preferences (e.g. Account Settings → Editor preferences) to show/hide the AI sparkle icon on hover, independently from team-level AI settings.Thank you for con

Figma has added percentages to text styles, which is fantastic. However, when the style is linked to a variable, the percentage is removed, and uses px units instead. I am trying to set up my design system using a scalable token system, and little features that don’t quite work are so frustrating. Please allow variables to support percentages! It will help us not need to use plugins like Token Studio. 

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 Figma Team, I always struggle with comments when I move layers, especially when changing the order of the frames as they remain relative to the canvas, not the element. This becomes especially challenging when too many people review the design and they leave their comments. One change on the frames’ order will cause the comments to be pointing at the wrong element causing unnecessary confusion. It would be great if I could bind the comment to an element rather than the canvas.

Abstract My team would like the ability to publish versions of multiple libraries simultaneously. Adding version control on a project level instead of on a file level would make this possible. This behavior would more closely mimic the kind repo versioning that our engineering counterparts are able to do with git tool like gitlab and GitHub. Background Our team builds and maintains a design system used by a very large number of designers who work across a variety of themes and extensions libraries. In order to support the various needs of our users we have various library files for tokens, core components, and component extension libraries. Frequently, changes to our libraries involve needing to make changes more than one library; any one of which is being consumed by any number of teams at any given time. We use semantic versioning and make minor releases on a quarterly basis. Problem We need

Version control for designs or “GIT for designers” inside Figma 🙂: Master design; Branching; Merging changes.

 I cannot find a way to copy the image styles without using the original image. I just mocked up this kind of stupidly but… that would be great if you could do that..  There is no way to actually adjust from image to image. Unless I'm missing something! Thank you for your attention and your great work. I hope that I'm making myself clear. Chris

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.

Please can we get percentages for variables? We can use percentages manually, but we can’t create a percentage as a variable. This would speed up my design to dev process tenfold, and considering we can already use percentages in the design, why disallow it in variables?An example is I want store values for line height and letter spacing as percentages which behave responsively/dynamically, so when creating type variables I don’t have to do manual calculations, store 10+ letter spacing/line height values based on which font size they will be used with and hope I never change the font size variable in the future.

The Check designs tool is really useful but I have one big problem with it. In some cases I have used items or colors outside the design system by intention, (annotations or information to the developer or business as the built in annotation is not visible for all). I would need to be able to ignore some design suggestions. Right now I can not use the check design function as only some of the suggestions actually applies. So, my suggestion is to either be able to ignore suggestions that aren’t correct or select those that you want to apply.

I wish there were a "Reset Slot" button next to the slot that has a "Modified" tag. This could help me a lot to reduce the steps to reset the slot. I guess while building this feature, the dev team might have guessed this action is not welcome for the slot. But in some scenarios, for example, I want to reset the slot whenever I accidentally change something in the slot, which causes the slot to freeze and not receive new updates.  

Sometimes a particular boolean variable can affect several layers. And some of that layers may require inverted visibility state. E.g. Layer 1 is visible when the variable is truthy and Layer 2 is visible when the same varaible is falsy. Let’s say, we have a multiselect field with a dropdown. When we select the first option, it should be added into the input as a label (label layer becomes visible). But also this option should be removed from the dropdown list as it’s no longer availiable for selection (option layer becomes hidden). So, both states depend on the same variable, but their conditions are inverted. It would be nice to have some negation operator when applying a varaible. Kinda logical not (!) in JS: ! isSelected. Or just allow us to apply boolean expressions as we do in prototypes , e.g. isSelected != true.

Right now, tying layer visibility to a variable means if the boolean is false = layer is hidden. It’d be great if we could invert this functionality (boolean is false = layer is shown) on a per-layer basis as I need to show some layers and hide others depending on the state of the variable. Anyone else run into this?

Native Dev Mode annotations are valuable sources of context that get lost for anything using the MCP. Measurements and props, too, although I don’t think that’s nearly as important. My response from Github Copilot:This is a limitation of the Figma MCP server that powers my Figma tools — it currently exposes the layer/node tree but not the annotations or comments API endpoints.

Please make Dev Mode Annotations visible by all roles, not just Full Dev Mode seats. This can become costly for users needing context but not all the other dev-mode features. Here’s the scenario: We have a dashboard, with cards showing a customer’s account status. This status can be mapped from multiple back-end statuses, to show just one front-end status. For example, any of the following could be mapped to a single status known to the customer as “Completed”: canceled, terminated, sold, complete, etc. This is something that the developer needs to reference, but then also the PM needs to reference in writing tickets (who doesn’t need full dev-mode access), the QE needs to reference for testing automations, and various other individuals on our team. Placing it in a comment makes it less clearly attached to the specific piece of the design, and requires us to keep documentation dispersed among different tools (Jira, Confluence, Figma etc). Simply making Dev m

Hello, I was wondering if there was a way to hide the Figma Make chatbot bar at the bottom-left of the UI. I have to use my computer at a higher magnification setting due to visual issues, so the bar takes up a lot of space for a feature I’m not going to use. It’s also distracting to have it type out example prompts each time I open a new board, so I have to stop what I’m doing and wait until the animations stop before resuming my work.Thank you!

A ton of great features launched yesterday. One of them is Autolayout Wrap. It might be just me but I couldn’t find how to wrap from right to left. This seems weird as Figma did an amazing job of closing its long technological debt when it comes to RTL languages. Please tell me this gap has not been reopened again…

As a designer, I'm working on a large-scale Figma project with over 3 years of development. The file includes numerous deeply nested components used throughout the product.Even minor changes to a single component—such as swapping a fill for a stroke on a button—trigger severe performance problems:Figma freezes for 5–10 minutes as changes propagate across all instances. Another 5–7 minutes are needed to sync with the server. The tool becomes sluggish, with 1–3 second lag on every action due to background updates.This makes efficient work nearly impossible. I can't make consecutive changes without waiting for updates after each one, significantly hampering my workflow. Proposal:Implement a feature that allows users to temporarily freeze a component, preventing changes to the parent component from immediately affecting its instances

With the new update, we have a great new feature, but unfortunately, it’s not usable with our component structure. Exposing all props of a nested instance also exposes props that we don’t want in the context of the consuming component. What if we could also select which properties to expose? This would lead to a cleaner sidebar with only valid props.

I’m building a web app. The issue I have is that the mobile frame options in Figma don’t include the header and footer that browsers have. So when you preview your work, it looks like a native app, not how you’d actually see it when browsing the web on a phone. I know I can manually add this as a header and footer for every frame for every page of the site I’m designing, but it’s kind of a pain. Real mobile browsing includes these headers and footers of the browser. 2.

Does anyone know how to turn off Figma’s auto-formatting? I’m trying to type '- ', but it looks like Figma is assuming this text must be a bulleted list. I’m having a similar issue when using text that’s in the format of an email address or a url. Figma is changing these to unwanted links. I’d like to turn off all text auto-formatting.

When creating tokens and working with variables Dev Mode generates code where the group name is included as part of the token name. Currently this doesn’t make too much sense (for me at least) and in Figmas own variables tutorial it would result in spacing tokens being called “SpacingSpacing-sm” if you would look at the tokens in Dev Mode. Can we please get an option to exclude the group names from the generated code? The groups as I seem them are for organising and not necessarily something we want to automatically include in the token name. Semantics are important for tokens so if I have to leave out part of the name and only have it as part of a group name it makes reading the token and using it correctly in Figma so much harder. Definitely interested in hearing others experience regarding this! Maybe i missed something or should rethink our structure.

The Problem: > Currently, Figma’s native PDF export converts all text layers into vector paths (SVG objects). This causes several major issues: High File Size: Vectorizing every character creates unnecessarily large files. No Accessibility: Text is not selectable, searchable, or readable by screen readers. Professional Limitation: We cannot use Figma for brochures, data sheets, or documents that require copyable text. Proposed Solution: > Implement Font Embedding (subsetting) in the PDF export engine. Retaining text as a "text layer" would make Figma a viable alternative to Illustrator or InDesign for document design.Why it matters: > This would significantly improve workflow for designers creating marketing assets and technical documents within Figma, ensuring files remain lightweig