Suggest a Feature

Hey lovely Figma team! Wouldn't be great if we could click or right click on a design system input/variable and instantly see where it’s used across our files.

Design reviews, ideation sessions for fully remote teams. Right now we have to switch between the video calling app and Figma. It feels more natural to schedule a video call directly from Figma since we already have the real-time collaboration out of the box.

When I export images/photos that were placed in FigJam file, all photos export with this thick white border. Is there workaround so that the images export as if in normal Figma design file, ie, without the border?

Maybe there’s a workaround I’m not aware of — any help would be appreciated.I’m trying to create a card component with text and an image. The tricky part is the image: it should be flexible – keep the original nested component size and support different aspect ratios across component instances (for different breakpoints). Now in the main component, I use an image placeholder for the visual. However, when I swap that placeholder with a real image in an instance, the image always conforms to the placeholder’s dimensions instead of preserving its original size/aspect ratio. I tried different auto-layout options but nothing worked.I’m looking for a way to build this so that the image resizes based on it’s own dimensions and aspect ratio, rather than forcing all images into the same fixed size.

I’m noticing to make much of anything with variables, I’m creating a lot of collections that use mostly aliases. After selecting the alias source I mostly have to keep these connections in my head. It would be nice to open up all these connections in a node editor view to either make updates or check for mistakes.

Hi,The new grid feature is nice for general layout, but if you where to allow properties to be assigned to the hug/fill/fixed values of colums/rows as well as to the addition/subtraction of columns/rows and to row/column span- the grid would become much more powerful. This would allow me to create one grid component that is controllable using properties instead of having to create multiple custom grids depending on the content of the grid in a particular module/page of an application. You can obviously nest grids, which is something I’ve explored to try and solve some of this- where each cell contains another grid- but If one can dream I would also very much like to be able to have individual auto-layout settings for each cell in a grid (including grid) as well as being able to treat the column/ row as its own individual container e.g. place components in each cell of a row but then also place another component in the actual ROW.We have a file explorer type grid in our

Hi Figma team,I’d love to suggest an improvement to PDF export.Use case: I often work on a single page that contains many frames (slides / variants / iterations). Today, if I need a clean single multi-page PDF (one PDF containing multiple pages), the best option is File → Export frames to PDF.Problem: this exports everything on the page and the page order depends on the layout (left-to-right, top-to-bottom). In real files, I usually have draft frames, alternative versions, notes, etc. So to export only what I want, I often end up: moving/hiding unrelated frames, or copying the frames to a brand new page just for export. That’s extra friction compared to Adobe XD, where exporting a multi-page PDF from a selection is straightforward.Feature request: Add an export option like “Export selected frames as multi-page PDF” With a

TLDR; Figma should stop rewriting the entire code document every time a minute change is requested. So far, I'm incredibly impressed with Figma Make. It definitely has its limitations when it comes to deeper logic, but it has been doing a fantastic job of helping me to rapidly prototype up some of my designs, and I'm excited for where it is going. The way that entire code documents are being rewritten is one of those AI code agent growing pain items that are now becoming obsolete when working with tools like Cursor where they can be negated by creating a rule that explicitly asks to avoid the practice. I would love for there to be a similar feature available in Figma Make to allow me to prevent entire code rewrites for every little change that I request. 

  Currently, an interaction (e.g., a button click) on an object can only have one destination per trigger type. If a designer wants to use the exact same object in two different flows (e.g., a "Happy Path" and an "Error Path"), they are forced to either: Duplicate the page, breaking the "Single Source of Truth" principle and increasing maintenance. Use (page)components and instances, not ideal. Use Complex Variables/Logic, which is powerful but overcomplicates simple flow branching and makes the "Prototype Settings" unnecessarily complicated. RequestA feature where a component can have multiple destinations for the same trigger type depending on which 'Flow Starting Point' is active. 

Currently you can set things like, 5.99 or 4.32 but you can’t show 5.00 by default. This looks weird when you start adding amounts like #amount + 0.5 which will then look like $5, $5.50, $6, $6.50. It would be nice if instead it showed as $5.00, $5.50, $6.00, $6.50

So, my company has a card component which may have 3,4,5 or whatever number of columns is needed - the same for rows. However, I cannot build a straightforward component without either: a) instead of using grid (the way the devs usually do), using regular autolayout with a bunch of max/min/fill properties. b) creating a huge megazord component with all the variants we´d need or  c) resorting to detaching.  It´d be really useful to be able to toggle rows and columns on a component instance to create really customizable and powerful components.  Would be very useful not only for cards but for things like tables (eg toggle the whole column with checkboxes or with actions) .

Is Figma ever going to allow us to collapse/expand pages in the sidebar? What about text-wrapping layer names?

I’d like to suggest adding support for viewport-based height (for example 100vh) in Figma Sites. In many real-world design scenarios, especially for web and responsive layouts, designers need a page or a specific section to always take the full height of the user’s browser viewport. Currently, this requires workarounds with fixed frame sizes or manual resizing, which breaks responsiveness and does not accurately reflect how layouts behave in production. Tools like Framer and Webflow already support viewport units, making it easy to design hero sections, full-screen onboarding, landing pages that adapt to the user’s screen height. Having a similar option in Figma, such as setting a frame or section height to “Viewport height” or “100vh”, would greatly improve accuracy, responsiveness. This would be especially useful for: Full-screen landing sections and heroes Onboarding and single section screens

I really need adaptive font sizing for text inside fixed-size text boxes, especially for Buzz.Here’s the use case:We create a creative for social media. We then create multiple sizes of that creative using auto-layout, constraints, etc. After that, we generate Bulk Create versions in different languages.The challenge is that text length varies significantly between languages - for example, French is often much longer, while Japanese can be much more compact.It would be incredibly helpful if the font size could automatically adapt to fit the fixed text box, similar to how text behaves in PowerPoint or Keynote.This feature would save a huge amount of time and effort, especially when working with multi-language creatives at scale. I believe many teams would benefit from this.Thanks in advance — really looking forward to this improvement. 🙂

I am writing to request a new feature: the ability to connect my SyncFusion license to 'Figma Make'.Currently, I need to use SyncFusion components while building my designs, and having this integration would allow me to use my licensed assets directly during the prototyping process. This would greatly improve our workflow and design-to-code consistency.Could you please let me know if this is currently possible or if it's on your roadmap?

Currently, corners can only be rounded at whatever size you set. However, it would be great if you could set different styles of corners such as inverted rounded or chamfer as you can in Illustrator. The goal would be to create a style like the image below:

In regards to Figma Analytics, there’s two ideas I would like to suggest!On the table on the main library statistics page, it becomes very difficult to remember what the columns are as you scroll towards the bottom. Is it possible to make the header bar sticky so that I can still see the column titles when I reach the bottom? Also it is helpful to see how many times a component is detached. While that functionality exists, we cannot tell where the detaches are within the files that use that component/variant. Having the count continue from the variant table into the table with the files that use that variant would help use immensely so we can do some user research to find out why that team/file is detaching that component.Thank you!

I noticed I’m able to set a default color (variable) on shapes, so when creating a new shape it uses the defined color (variable). However, this behavior doesn’t work on text. I’m guessing this has to do with the default text color being tied to the color of the page. However, I’d prefer the option to be able to set a variable as the default text color. When doing rapid iterations, it’s often the case where I accidentally have text unlinked to a variable, and sense dealing with dark grey colors it’s easy to miss some text being black. Tried to set the text to default to my dark grey variable color but it was at this point I realized I was unable to.

Please give the ability to change position of toolbars/widgets (or at least swap left and right), my neck is already in chronic pain to constantly turn my head to keep looking on the right. I want to pop out the damn thing and place it where i need it to. When you have a large monitor it is a pain! Everything tiny and far away from what I am working with.

Upon using Figma Sites, one of the first things I noticed was that you can’t nest pages inside other pages or folders to keep related content organized in the sidebar (like /projects, projects/project 01, projects/project 02, etc.). Dividers, which we got last year, definitely helped a bit—but having collapsible folders or nested pages, like with layers, or pages in Framer, would seriously help keep things organized – especially for URLs.

It would indeed be game changing and important if we could get the option to automatically swap between variants based on the actual size of the parent frame. This could simulate real life complete web applications and be really helpful to show when and how a breakpoint should interfere with a component.

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

When you come to a point that you want to create a dark translucent container on top of a colourful background, we all notice how desaturated it becomes, and how  i.e. Apple seems to negate that. And after having tried each blend mode, it just doesn’t give us 1 blend mode to rule them all and have your container be how you want it to turn out when changing the background to a dark grey background. So instead of messing around with blend modes, how about the backdrop-filter saturate gets introduced in Figma, and bring back some colour?

While presenting to my students (all in view mode only), one of them realized that they could turn music on for the entire class by clicking on the music button. I think that users with view access only should not be able to start the timer or music. Could you restrict access to to these widget to only collaborators in edit mode. Thanks, Sean

Angular + Figma MakeSupport for Angular in Figma make:Whoever think it’s important - Vote. Thanks,Galit