Suggest a Feature

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 mode annotations visible to v

Something about the old UI made it easier for me to understand that layers and pages were two sup panes. I think it was the fact that pages were indented a bit. It helped easily distinguish the pages and layers section of the left pane. Now with UI3 I find myself not being able to find where pages end and layers begin as easily. I need some sort of visual anchor here. My eye used to follow the negative space to the left of page names all the way down until I hit the layers area and now I feel like I’m going cross-eyed trying to find where my layers start and pages end.

The text above the top left of the frame is very small. Please have some setting so that when you zoom in a lot, the text no longer stays the same size and enlarges, so you can at some point easily see the text and be able to edit it easily. Sometimes I have to take a screenshot and then zoom in to see what i’ve typed. Other text in other apps appear easily readible. I remember another app ( I think Sketch) did this, when you zoom past 100% it keeps the font size relative to the zooms instead. so the artboard name becomes larger and larger.

Figma needs a glyph panel to access glyphs per specific font. Photoshop and Illustrator have this feature and it is a necessity for typographic design. Having to leave Figma and go to Photoshop or Illustrator is incredibly inefficient. Implementing better type setting tools within Figma would be a major improvement

I don’t use Figma all the time, I don’t want it to run anything on startup. It’s frustrating to manually remove Figma from Login Items, since it automatically adds itself there again. It would be nice to have at least an option to disable it in settings, or even better - remove that functionality at all, since it’s not user friendly. I want control over what and when the apps do at my workstation. P.S. If it’s needed for updates check - I’m more than okay to update on app start

Prototyping triggers won’t allow to bind an action to diagonal moves of the stick. Both LStick and Rstick. Tried to prototype a command wheel. Segments should be triggered by eight corresponding directions of stick movement. But only four of them was possible: up, down, left and right. Does anyone else in the game industry experience this? Is anyone using a plugin or workaround to help solve this?

I’ve been using Buzz to create full page templates, which has great potential. However, in the Edit Content panel, all editable fields for the entire page are displayed at once, which makes it difficult to navigate and manage.My suggestion is to improve this panel by making it context-aware. For example, when a specific section or component is selected on the page, the panel could display only the fields related to that element. This would make editing full pages much easier and more efficient.To give some context, in one of my projects, Buzz shows around 160 text fields along with dozens of media items. That’s a lot of information to manage in a single panel. A filtering mechanism based on the selected element would significantly improve usability.

Been playing around with the “expose nested properties” feature currently in beta. One of the great uses of variant properties is the ability to batch edit property values on multiple selected components. That use doesn’t carry over to exposed nested properties (yet I hope). Demo file to help When selecting one component instance exposing nested properties, said properties display fine. Add another instance of the same component to your selection (using Shift+Click), and the nested properties outright disappear from the right panel. I haven’t seen this issue raised elsewhere! Do you experience it too?

Hello,I would like to suggest some important improvements to the Lock Aspect Ratio functionality. Since Figma is widely used for building responsive designs, I believe this should be an important feature.I noticed that this issue has already been raised, and I believe it is a real problem when working with responsive layouts.The problemThe main issue is that Figma calculates the aspect ratio based on the exact pixel dimensions of the original element, including decimals, rather than preserving the intended aspect ratio.For example, suppose I have:A parent frame that is 375 px wide A responsive version of the design that is 440 px wide An element inside the 375 px frame that should have a 4:3 aspect ratioAt 375 px, the element is 343 × 257 px. This is not mathematically an exact 4:3 ratio, but this is understandable because using an exact 4:3 ratio would result in decimal values.However, when I resize the parent frame to 440 px, Figma appears to preserve the exact ratio of 343 × 257, ra

💡 Feature Idea for Figma: “Fonts Used in Frame”I’d love to see a feature in Figma that automatically shows all fonts used within a selected frame.For example:Fonts UsedInter — 12 layers Regular — 7 Medium — 3 Bold — 2 Roboto — 4 layers Poppins — 2 layersIt would be even more useful if we could click a font, see which layers are using it, and replace it across the selected frame.Suggested workflowSelect Frame → View Fonts → Identify Usage → Replace FontA Suggestions section could also highlight:⚠️ Missing fonts 💡 Too many font families 📏 Inconsistent text sizes 🎨 Similar text styles/colorsThis could make design audits and maintaining consistency much faster.Would you find this useful in Figma? What would you add to this feature?#Figma #FigmaCommunity #FigmaFeature #UIDesign #UXDesign #DesignSystems  

I do a lot of packaging and print work, and Figma is already my tool of choice for everything up to the moment the file has to go to the printer. That last step is where it falls apart, and I end up rebuilding the layout in Illustrator or InDesign just to hand it off.A few things that would let us stay in Figma end to end:CMYK and spot colour supportRight now everything is RGB, so colours shift the moment the file hits a press. Being able to define CMYK values, assign Pantone/spot colours, and see an out-of-gamut warning would solve the single biggest problem.Bleed, trim and safe areaA document-level setting for bleed and trim marks, with the artwork actually extending into the bleed, rather than everyone faking it with a frame inside a bigger frame.Print-ready PDF exportPDF/X-1a or PDF/X-4 export with crop marks, bleed, embedded fonts and no downsampled images. Today's PDF export is fine for review but printers reject it.Dieline / cut layer handlingFor packaging we work on top of a di

The fonts looks sharper and crispier in Figma due to the font-smoothing css property that applied in Figma’s CSS style by default. Hence the font-smoothing property is deprecated and the support is limited to MacOS, it is misleading when designing on a Mac and looking in any web browser on Windows. Providing an option to disable the font-smoothing in Figma settings will let us get the same results in Figma and web browser regardless of operating systems. Thanks in advance!

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 would be amazing to have a simple MCP tool that allows external AI agents to send prompts/messages directly to an existing Figma Make project.Something similar to Lovable’s send_message capability.The goal is simply:AI Agent → MCP → Figma Make → generate/edit designThis would make it possible to control and iterate on Figma Make directly from the AI agent without manually copying prompts between tools.

Currently, the settings for export in Figma are limited and in turn, limiting. Mobile banners and ads would export to a crisper, higher quality if given the option of exporting at DPI of 300 and/or 450. Right now, having no options other than 72 dpi for teeny tiny ads that are 300x50 and 320x100, means the quality suffers.

I’m a graphic designer, and my first introduction to the design program was adobe, and the same can be said for many Figma users. However, the new features that Figma keeps rolling out make the design file space increasingly more and more versatile and comfortable to use than Adobe for many things. However, one major killer is the lack of print-friendly features: I’d toss Adobe out the window in a heartbeat if I was able to change the units of my ruler in Figma and was able to imposition booklets in Figma. I know that Figma Design was created primarily for product design, but it’s becoming more of a versatile tool for designers beyond just the UX/UI space, and it would be cool if Figma could take this into account.

It would be incredibly helpful to be able to render HTML in a widget or iframe type tool in FigJam, allowing for stickies and comments to then be overlaid on top of it.The use case for this is when using FigJam for planning or design collaboration, we often need to take screenshots of prototypes, whether that be from make or other prototyping tools in order to have discussions. Existing tools to get this information into Figma are lacking. There are tools which render HTML files into Figma, but they require giving access to untrusted developers. I would like to simply be able to upload an HTML file and have it get rendered by Figma into a widget which can then have discussion based on it next to all the other FigJam tools. There seems to be a considerable market for this. There are other tools such as markup.io or pastel, which essentially exist just to serve this purpose of rendering HTML assets and allowing comments. This feature would make Figma a much stickier part of our product d

Dear Figma Team,I would like to suggest a useful improvement to the Export option in Figma.Currently, Figma provides export options such as PNG, JPG, SVG, and PDF, which are very useful. However, when working on websites, I often need only the SVG code rather than downloading an SVG file.It would be very helpful if Figma could provide an option such as “Copy SVG Code” or “Copy as SVG” directly in the Export section.For example:Export → SVG → Copy SVG CodeThis would allow designers and developers to quickly copy the SVG markup and paste it directly into HTML, CSS, or web projects without having to download the SVG file and then open it separately to copy the code.I believe this would make the designer-to-developer workflow much faster and more convenient.Thank you for considering this feature request.Best regards,Arvind

In the Figma UI, you can create a color variable that references another color variable (alias) and override its opacity — producing a "composed color" value. This is extremely useful for building semantic color systems where, for example, surface/overlay = palette/neutral/900 at 54% opacity.However, the Plugin API currently does not support writing these composed color values via setValueForMode(). Attempting to do so throws:Uncaught Error: in setValueForMode: Composed color variable values are not supportedMinimal reproduction scriptRun this in the Plugin API console or inside a plugin: // Step 1: Create a variable collectionconst collection = figma.variables.createVariableCollection("Semantic Colors");const modeId = collection.modes[0].modeId;// Step 2: Create palette/neutral/900 — a base colorconst paletteNeutral900 = figma.variables.createVariable("palette/neutral/900", collection, "COLOR");paletteNeutral900.setValueForMode(modeId, { r: 0.07, g: 0.07, b: 0.07 }); // Works fine ✅//

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

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.

 When I select a hex color, for example #FFFFFF, Figma should automatically check whether the exact same color already exists in my local color variables or styles.If a matching variable/style exists, Figma should suggest it first when I choose to apply a variable or style.Example:I select #FFFFFF Figma detects that #FFFFFF already exists as a color variable in my design system Instead of showing all available variables equally, Figma prioritizes or recommends the matching variable:White / #FFFFFFThis would make it much faster to connect manually entered colors to existing design-system variables, reduce duplicate colors, and help maintain consistency across a design system.

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

Hi! Turning off “snap to pixel grid” in a Figma Design file no longer changes snapping behavior when dragging frames around. Whether this feature is turned on or off, a dragged frame still snaps to each pixel, no matter how zoomed-in. Note that some other objects (e.g., vector objects) still respect this setting. It’s just an issue with frames, components, and component instances. Note that If I group the frame, I then can drag the group to any sub-pixel location. I’ve restarted my machine, restarted Figma, checked for updates, reloaded tabs, tried it in other design files. Tried it in the client, in Chrome, and in Safari. Same problem. Can anyone else replicate this?

Current State: When you add a stroke to a mask, the stroke becomes an extension of the mask.Needed Improvement: When you add a stroke to a mask, the stroke is on top of the mask.This should be so simple, can’t understand why this wouldn’t be the default, but at the very least to have this as an option would be super helpful. I understand you can duplicate the shape on top and add the border, but then when resizing the mask you have to resize the shape on top as well, trying to eliminate a step.