Suggest a Feature

My iPhone takes screenshots at 1179 × 2556px, which is @3x. The native resolution @1x should be 393 x 852px.But, Figma imports my iPhone screenshots at 589.5 × 1278px, seemingly assuming that the images are Retina / @2x. Can I change this setting somewhere?

The hug update to auto layout grid is a great update, but still lacking some critical features for creating data tables. It would be extremely helpful if we had the ability to assign fill colors or strokes to an entire row instead needing to add to create a cell component with the fill or stroke added to that. The issue with that is if you had content in a cell that needs to wrap to multiple lines, you would need to adjust the height of all the cells in that row to fill so that the color or strokes line up. I would also be helpful if we could control an entire row or column with variables. I am creating a table component and we have an multi-level header row that is optional so we need the ability to toggle that row on and off via the props panel. Another small addition that would be useful is on right hand panel where you see the full list of all columns and rows, allow us to change the order of them in that section. Hoping you continue to iterate on this feature. Thanks

I work in an agency with a team wanting to create a Slides template for our studio decks. However, as far as I can see, only one designer can be the owner of the template and therefore edit it. Everyone in the rest of the team can only use it.This is a huge limitation as that single designer always has to be available to make updates, and if we want to add some new slides with layouts useful for our deck, then nobody else can make those additions. If that designer is on holiday or leaves, we’re stuffed!This could be a huge barrier for us moving agency decks into Slides, however much we love it, compared to InDesign or Keynote.Please Figma, make everyone in the team be able to edit Slides templates!Are others out there running into this same limitation?

I would love to be able to change the default fill / stroke color / and corner rounding of sections within Figma. I find myself spending a lot of time adjusting sections after initial creation to the way I like them throughout my files.

Figma 슬라이드를 사용 중인데, 내가 현재 작업하고 있는 슬라이드 페이지에는 현재 상태가 표시가 되어있지 않는 듯한 UI 입니다. 좀 더 또렷한 상태로 확인 가능하면 좋겠어요. 다크모드여서 그런것인가 싶기도 합니다.하지만 전체 화면 모드 색을 피그마때문에 바꿀 순 없으니 개선이 되면 좋겠어요.슬라이드 페이지를 작성하는 데 시간이 걸리기 때문에 시간이 오래 걸리게 됩니다. Google 슬라이드를 칭찬했을 때 지금 가장 좋은 점은 점이라고 생각합니다.

We need a feature that enables counting and reporting of annotation labels for team metrics.In our workflow, designers leave comments on Annotations and apply one of multiple possible labels. For metrics and reporting, we want to: Aggregate counts per label (e.g., Interaction: 12, Accesibility: 7, etc.) Understand the distribution of annotation labels over time/projects to improve our overview and tracking.

Hi Figma team,I wanted to share a small pain point I keep running into — and maybe a solution.As a UI/UX designer working on complex SaaS and mobile projects, I often end up with Figma files that have dozens of frames across multiple flows. Despite careful naming, it's easy to lose track of what’s ready for dev, what needs review, or which version belongs to which client.Lately, I’ve found myself wishing I could just tag frames — like #ready, #needs-feedback, or #v1.2 — directly on the canvas or in the left sidebar.Something lightweight, like sticky labels or even a built-in tagging system, would make navigating and collaborating inside Figma so much smoother.Right now, I rely on naming hacks or color-coded backgrounds, but it gets messy — especially when the file grows.I imagine a world where I could quickly filter or search for #mobile or #dashboard and instantly jump to relevant designs.Thank you for building such a powerful tool already. I just thought this small improvement could

Hi Figma Team, While working across multiple design systems and cleaning older project files, I’ve noticed a recurring friction point in the Color Styles panel: Figma does not support searching color styles by their hex values.This small limitation creates a surprisingly large productivity gap for designers and teams. The Core IssueCurrently, the Color Styles search recognizes only the style name, not its underlying hex code.But in real workflows, hex values are often the most direct, reliable reference point — especially when working across old files, new token systems, or unlinked fills.Evidences  Why This MattersHere are a few common scenarios where hex-based search would significantly improve workflow efficiency:1. Faster Updating & Mapping ColorsWhen aligning older files with a new design system, designers often copy a hex from the canvas and expect the matching style to appear in search — but it doesn’t.2. Easier Reviewing of Junior Designers’ FilesJuniors sometimes use direc

It seems very unusual to publish a code generation feature without any kind of mechanism for export to version control. While I’ve been testing figma make and enjoyed the result, i’m having to consider moving to alternatives like lovable because of the benefits of simpler integration with version control.Will we be able to link our figma make projects to a github repository in future?an alternative approach would be integration with the figma for VSCode extension. 

Hi everyone,I’ve been working with the Figma API and noticed that while FigJam mind maps can be created via the UI, there is currently no official API support for programmatically creating or manipulating mind maps in FigJam.I would love to see an API that:Allows creating a Mind map programmatically Allows adding/removing nodes and connecting them Supports retrieving an existing mind map structureAt the moment I can only manipulate text nodes and connectors, but not the Mind map UX behavior itself.Is there any plan to expose a Mind map API for FigJam? It would greatly help in plugin and workflow automation.Thanks! 

It would be great to be able to copy a Figma prototype and paste it directly into a Figma site, similar to how Figma Slides handles this.  I’m using Figma Sites because I expect tighter integration with Figma, but it currently feels like they don’t work well together.

I understand Figma Sites is still in beta and primarily aimed at design‑first, variables/CMS‑driven site generation. That said, it’s also clear that under the hood it uses a React‑based stack.Removing multi‑file support in code layers makes the experience objectively worse. Large, single‑file components:Reduce maintainability and code clarity Degrade AI assistance performance as file size and line count grow Go against basic, well‑understood best practices of keeping code modular and scopedKeeping code split into reasonably sized files is a fundamental requirement when AI is expected to help users read, reason about, and modify code. Without this, even simple workflows break down, and Figma Sites becomes unusable in any meaningful way with Figma Make. This isn’t a power‑user edge case—it’s table stakes for AI‑assisted workflows.Is the single‑file limitation a temporary beta constraint, or is there a planned, supported way to structure modular code in Figma Sites going forward?   

The Problem: Friction in Freeform BrainstormingIn FigJam (and Figma Design), organizing loose assets requires too many clicks. Currently, if I have 20 images or stickies and want to reshape them from a 2x10 column to a 5x4 grid, I have to rely on "Tidy Up" (which is static) or manually move items.The Solution: A Dynamic Reflow HandlePlease implement a direct manipulation handle on the selection box that allows us to drag to reflow content instantly.Miro currently sets the gold standard for this: you select multiple items, grab the corner handle, and dragging it instantly reflows the grid (changing columns/rows dynamically).Why "Auto Layout Wrap" Is Not the AnswerI know Figma technically has the layout engine to do this via Auto Layout Wrap. However, relying on the current Auto Layout workflow is inferior for brainstorming for three logical reasons: Interaction Cost (1 Action vs. 4 Actions): Miro: Select > Drag handle. (Done) Figma: Select > Shift+A > Go to Property Pane

Figma prototyping would be really useful to have in Figma slides. I don’t mean embedding a prototype on a slide, I mean things like the ability to put a button on a slide that takes you forward, back or to a specific slide. Some examples of how this could be used: Back and forward arrows you can click to go back / forward Table of contents Creating carousels of information within a slide Hover states and other interactions to make slides more engaging I know you can get the URL of a slide and add it as a link to text, but that’s very hacky and doesn’t work for something like an actual button or an icon. Basically bring prototyping functionality that’s already in Figma to Figma Slides. In my opinion that’s a big reason why so many people were using Figma for presentations in the first place.

This seems like a very expected feature, but it doesn’t work in slides.

Hey guys, I’ve created a presentation and I exported to PDF to send it to my client. But all the slides are with rounded corners with a white background. Isn’t there a way of exporting WITHOUT the rounded corners? Thank you!

Two ideas that continually come to me when running into these scenarios:Sort/Filter menu remains open after click. Instead of having to reopen the menu after each change, it should remain active until I intentionally click off of it. Find component from prototype. When viewing a prototype, leaving comments sometimes end up floating in the edit version of the same file. I should be able to right-click the component to open its location in a new tab.

We have integrated Figma MCP with VS Code. This allows us to compare styles between Figma and the actual code, making it easier to identify and fix discrepancies. However, we are currently unable to compare all variants of the same component at once.For example, a single component may have Default, Hover, and Active states. Is there a way for Figma MCP to internally compare all variants simultaneously? Currently, we have to compare them one by one.The reason we want to compare everything at once is that we are planning to automate this task using workflow agents with Figma MCP.We would appreciate your guidance on how we can compare all variants at once.

Annoying to switch option between png.svg all the time, when i export assets these are svg, but Figma has png format as default.

It’d be awesome if I could change the BG color of the entire work area because mostly my team’s UI uses white. Pretty please? 😍

I’d like to be able to create aliases for text styles, colors, shadows, etc. For example, I have the color “Color/Primary/500” and would like to create the color “Button/Primary/Background” that is a link to the first color, so if “Colors/Primary/500” is changed, “Buttons/Primary/Background” would change too. This would also be useful for text styles, effect styles and any other named style, allowing to create a kind of root tokens that can be reused under different purpose names.

The problemRight now, Figma Make files live separately from Design files.That means: I have to search for Make files I don’t always remember the file name There’s no clear way to tell others “this design has behavior” Design + interaction don’t feel like one project What I wantI want to treat Design + Make as one thing.Ideally: I can link Make files directly to Design files I can browse them together as one project Other designers can instantly see: “This screen has interactive behavior”

As of now, you can’t use % values for the line height and character spacing when creating a typography variable. Essentially, making it useless in terms of responsiveness if I want different heights and spaces on different screens or when a font size changes and I want the rest to follow according to that size. I am dreading having to review every single font size to make sure all the settings and numerics are correct when another designer without any type backgrounds edits the files.

Hi, Please, get the feature back. When i click ‘marked red’, fullscreen/small. It frustrate to always click on button…Thanks! 

We recently moved our deck from regular Figma design file into figma slides and turned it into a template.But a major UX problem for usin figma slides is the inability to select multiple slides from when a list shows up after + New Slide. We have around 100+ slide templates and adding all and then removing is also a hassle. Ability to choose multiple slides at the same time would be a godsend.