Share Your Thoughts

Describe the problem your experiencing and how your idea helps solve this When you create an autolayout frame, it always defaults to 10px. Many design systems call for an 8px grid and in many cases, users don’t want ANY padding especially where edge-to-edge designs are concerned. Ask questions to bring the community into the conversation What are everyone’s thoughts about the following solutions?: Default autolayout padding based on the big nudge amount in your settings Allow for tokenization of padding/margin grids and offer up autolayout parameters based upon those tokens Allow users to override the padding to 0px at the creation of the autolayout frame by using an alternative key command like ctrl+shift+a (command on mac)

I don’t need the layer thumbnails in the layer list. They clutter the layout. Is there a way to turn them off? The right-hand rail used to have variable pickers that let you select a padding or size variable from the attached design system, but they went away. This is going to slow down work in Figma significantly. Is there a way to turn those back on?  

Dear Figma Team,I would like to propose a feature that could be useful for UX designers and researchers. Problems I identified during my research:CJM, JTBD, empathy map templates, and other research methods are scattered across different tools — Figma, Google Docs, Notion, Miro. It takes 15–20 minutes to find the right method, and there is no centralized storage.Difficulty choosing the right research method.Fragmented workflows. After analyzing these problems, I created an application called UX Logic, which addresses them:Adding a library of methods and research materials, with the ability to add custom libraries and research materials. AI recommendations on the home screen. The AI suggests: “Structure insights,” “Validate hypotheses,” and “Build a CJM.” A unified workflow: Home - Projects - AI Chat - Library - Profile. All tools are in one place, without switching between 5+ applications. How can you use this application?Here is an example of one scenario:You paste interview notes int

When creating nested components, I want to lock the contents of a child components slots. For example, I make a generic “menu” component with slots. So then I make a specific “File Menu” using that generic menu component. That’s great. But when I turn that File Menu into a component, the contents are still editable in instances of the File Menu. I don’t want that. I don’t want consumers of the File Menu turning it into an Edit Menu. Standard Lock isn’t what I want, because I do want the user to be able to apply regular overrides, just not use the more drastic “Slot” features.So my request is for a feature that allows a main component to disable child slots.

Hello,I always enjoy using Figma Design and FigJam.I use FigJam for organizing Minecraft addon development and system design, and as projects become larger, I’ve started encountering difficulties balancing “the amount of information inside nodes” with overall readability.Currently, FigJam is extremely effective for:mind mapping organizing ideas visualizing dependencies structuring systems and architecturesHowever, as projects scale up, each node tends to require a large amount of detailed information, such as:identifiers recipes geometry references technical notes implementation status tags JSON-related information various propertiesIf all of this information is displayed at all times, the overall board quickly becomes difficult to read and manage.Because of this, I would love for you to consider adding:“Expandable / collapsible node functionality”For example:Normally, a node would display only a simple summary Pressing a button would expand detailed information A larger text area or s

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.

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  

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.

The management of seats is absolutely terrible. We have unused seats, and there is no way in the user interface to remove them to avoid being charged in the next billing cycle. If this is automatically not charged, it is not explained anywhere. The most terrible experience I had managing subscriptions after 25 years of actively using internet.  

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

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

Hi Figma Support,When writing a comment, accidentally double-clicking the canvas closes the comment box and deletes everything I’ve typed. This is frustrating, especially after spending time writing detailed feedback.Could you preserve unsent comments as drafts so they can be recovered when reopening the comment box? Alternatively, a confirmation prompt before discarding a comment would help prevent accidental loss.Thank you for considering this improvement!

 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.

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.