Suggest a Feature

There are many times I want to go back in the conversation thread and find something I’ve written previously, but after 800 iterations, that’s nearly impossible. If I could hide the AI’s side of the conversation, I could much more easily find my earlier prompts. 

tl;dr Adding options for crop marks and print bleed expands the usefulness of PDF exports and better leverages Figma for print design. Problem Figma is a fantastic design tool. So much so, designers are finding it capable beyond screen design and into the world of print. The PDF export option allows designers to easily produce posters, business cards, and other print-based documents that have been created via Figma. Although the PDF Export option is useful in many situations, it falls short in some areas that limit its ease of use for print designers. One way the PDF Export falls short is the absence of crop marks and print bleed. These elements are essential for designers wishing to use Figma to produce printed documents with elements cropped to the edge of the page. It is possible to work around these issues, but not without extra effort and knowledge of Figma and print beyond the basics. Solution

I’m a designer at a large e-commerce company. I introduced Figma to a team that worked exclusively in Adobe, and I’m now leading an organization-wide shift to make Figma our primary tool—for web and print. We’re building a label-automation workflow entirely in Figma, and I believe there’s a big product opportunity for Figma here.The problemEnterprise security policies (ours included) often block Google/Microsoft data sharing, so external connectors aren’t viable. Yet modern print ops—labels, care tags, manuals, packaging—are data-driven at scale. Adobe tools have been hard to automate and to collaborate in; Figma is the only environment that fits our collaboration + automation needs, if key print/data features are native.The opportunity for FigmaA secure, file-scoped, on-canvas data + print-ready export

Creating buttons in Figma is fantastic, but when working with multi-layered components that have custom corner details, resizing often causes distortion even if saved as components. This makes flexible scaling challenging and affects design consistency. Don’t you think it’s about time to add native 9-slice scaling support? It would significantly improve precision and workflow. Please consider this feature for future updates.

We should get option to detach all components inside all the selected Frames in one click which will detach all nested and parent compoents in one click.

Por favor, arrume uma função que dê a opção de escolher limpar ou pausar histórico de projetos visitados recentemente.

Thumbnails will not be updated (or not predictably anyway) in the project gallery unless you perform Restore default thumbnail + Set as thumbnail sequence on the wanted frame. This problem has been around forever, would be great to finally fix it as it is pretty annoying. Found this ticket describing it, which was closed sadly: My new thumbnail didn't refresh even after waiting 8h how to force refresh?

OverviewFigma Variables are already powerful for theming and responsive behavior - but Auto Layout settings remain static. Currently, we can’t change layout direction (horizontal/vertical), item sizing (hug/fill), or alignment (space-between, center, etc.) using variables.This limits the flexibility of truly responsive components - especially in systems using mode-based logic. Current LimitationRight now, Figma only supports number-based variables in Auto Layout settings (e.g., padding, gap, min/max width). But many key layout settings require string values, and they’re not variable-compatible yet: Direction: Horizontal / Vertical Justification: Space-between / Center / Start Sizing: Hug / Fill / Fixed

My question is in the title. Can auto-emoji be disabled when typing? For example, when copy-pasting “↔” in a text field, Figma will automatically render the emoji that matches those arrows. Can this (feature?) be disabled somewhere, maybe temporarily? I looked around on https://help.figma.com/ but found nothing about.

Today it seems that a comment’s date/time does not update with the last reply date/time in the comment thread. This makes following comment threads kind of impossible or at least hard.E.g. if I sort comments by date I see comments from 3 days ago on top even though there are comments that have a reply more recently than that.Sorting comments by ‘unread’ is not a solution because I might click through them quickly and then they will move out of the top of the list to anywhere where they move (based on comment creation date I guess). What is the purpose of having comment threads if it’s only possible to sort them by creation date? Or am I missing something obvious?Thanks. 

Hi Figma, glad for the update so far. I just want to share an idea or you can call it a suggestion. For now we have inner shadow, drop shadow and blur for effects. What about add one more effect such as outline just like in css?

Right now you can only select (and therefore filter) by Library, each of which is a separate, published file. If you have multiple primitive sets or collections within a single library, then scrolling through them to find the right variable is currently an incredibly poor user-experience. Yes you can search by variable name, but this requires you to remember variable names and it does not allow you search by collection name! This is particularly bad if you are setting up multi-brand variable architecture and surely you want to make that as easy as possible right, so people will need more than 4 modes? Overall, this encourages multi-file systems (so you can filter by library), which have their pros and cons, but namely that you can’t duplicate whole projects/multi-file systems and maintain the mappings/connections.  

Hi There, consider Dev Mode in browsers.Imagine how painful the endless right-to-left mouse work would be, if the element inspector was hard-left, with the CSS panel hard right… Well, that’s Figma today An outdated concept?It seems Figma might be based on an outdated idea that if tools are spread around the work area, it’s more efficient.But in reality, that’s not how it works because we use the grabber hand to position work next to the tools. So when the tools are all on one side, there’s never any need to move to the far left - drastically reducing the daily grind. Reduce the daily grindPlease allow us to dock the left panel to the right, then dock the toolbar vertically next to it.It takes a day to get used to, but if you work long days,

For many years, I’ve been working as a designer, accumulating over 10 years of experience using almost all Adobe products. Now, I’ve transitioned to Figma, as it’s an excellent tool not only for prototyping but much more. I’ve encountered an issue that might be of concern not just to me, but to others as well. Specifically, it’s about the placement of the two most important panels, namely the “Layers” and “Properties” panels, on opposite sides of the screen. I have a 34-inch monitor, and Figma is open in full-screen mode. However, when I need to perform actions on a specific set of layers, I find myself moving the cursor across the vast screen from left to right. Now, imagine needing to perform 10 or more consecutive actions like this. A significant portion of time is spent simply moving the cursor back and forth across the screen, along with the physical strain of repeatedly shifting focus and aiming at small buttons. It’s an ordeal and a waste of time on unnec

Hi, Figma community! It would be great to support dotted/dashed underlines in Figma. In CSS, it’s supported through the text-decoration-style attribute - see [text-decoration-style - CSS: Cascading Style Sheets | MDN]. Please vote 👍 👍 👍 for this feature! We hope to see it supported one day in Figma. 🥳

FigJam should have vertical alignment of text (Top, Middle, Bottom) in the table.

When using Auto Layout for an entire page flow, not everything is spaced equally. For example, imagine a page like: Toolbar Heading Paragraph Input Button To put all of these into a single Auto Layout and give equal spacing to all of it is not typically how it’d work (eg, Toolbar + Heading might be close together, but more spacing around above and below the Input). To use the benefits of Auto Layout, I wrap these objects into their own Auto Layout frames and then use the padding within these nested frames to create the spacing between elements. It’d be great to be able to apply margins to objects (like text frames or other frames) without having to first nest them into their own individual frames. This would be closer to how CSS typically works as text elements (h1, h2, p, …) don’t need to be nested in a div to have margin added to them.

it would be game changer to be able to export generated artefacts with figma make to figma design  

Currently, when copying ChatGPT content into Figma, it does not carry over the formatting. It copys the ChatGPT formatting as markdown, but Figma does not convert the markdown back into formatted styles. It would be helpful for Figma to recognize markdown and convert it into styles when pasting content.

There is a variable option for text strings that pulls in the value of a variable. I would like to an option to apply a variable name to a text string. This would allow my design system documentation to be dynamic based on the changes I make to the variable names. I used this option in Tokens Studio and it was incredibly useful.

Ability to color code at the project level for easier PMO

We really need to be able to create animated components in a more feasable way than what it is now.By animated, I mean animated, not the ‘smart animate’ interaction transition, but classic, loopable, keyframed animation. I sometimes need to show a thing happening in background, which I can, by using variants and ‘after delay’ interaction. This, however, is really wonky because it, for some reason, blocks keyboard inputs not associated with currently animated component. THis effectively locks the entire prototype if a component loops its animation.

Simple and straightforward:I am designing prototypes for video games, that include games that rely on mouse control (strategy, city builders, turn-based) as well as ones that sometimes don’t require mouse control (first-person shooters, third-person shooters). Sometimes a screen does not have a mouse control and is reliant only on keyboard strokes (or gamepad buttons).This is critical when showing prototypes to users because I need to test whether they can function without a pointer and find their way around a screen where only keystrokes are allowed.In order to do that I need to be able to turn off mouse pointer on specific screens, but allow them on other. An example would be an FPP shooter, which normally has no pointer on HUD, but reveals one when opening up the equipment screen.

When I select a single component, I can see the nested instances I exposed (super useful). But if I multi-select the same components, those nested instances disappear.Would be awesome if they stayed visible also on multi-select — it would make bulk edits much easier.

Hi team ,I quickly created a working prototype of an idea with great results. Now I’d like to use the components I built in my design files—not just the styles and colors.Is this possible, and if so, what’s the best way to bring those custom components into my design workflow? Also, can we create a base file of custom components for Make and share it with other designers so they can build their flows using those components?Thanks in advance!