Suggest a Feature

Could you add the ability to include the update icon thingy next to those nested instances which have updates available but might not have been update when the initial component update was applied, and maybe add an extra option in the instance update menu to also enable the ability to update the instance and nested instance as a short cut, or at least indicate to the user that there are nested instance updates available that haven’t been update.It makes sense that when you do an update to an instance you don’t want to automatically update those nested instances that the user may have already configured their properties, but it would still be very useful from an in application feedback context that the user is still being informed and communicated when there is a potential nested instance update that can be made but hasn’t been executed by the application.Like it could be as straight forward as have an update icon next the nested instance name on the side panel.

It needs to be easier to zero in on the specific things that were change in a branch review. For example, I have a branch where I add a simple line of copy to one frame. But when I review that before merging, it shows me an entire section without multiple layout frames in it. One of them has the new text line, but how am I supposed to know that? See the screenshot below - I made the additional text bigger so you might be able to spot the difference. But what if it was the same size as the rest of the body text? It would be better if it highlighted the specific difference and allowed you to zoom in/out at the parent/child layer level.

I have been playing around with creating variables but realized I would rather have groups in separate collections, but cannot move them.I would like to be able to duplicate an entire collection so I don’t have to manually re-create values and can remove what I don’t need from that collection OR simply be able to move groups into other collections.[The title of this post was edited from “LAUNCHED: Copy/Move variable groups into other collections” to “Copy/Move variable groups into other collections” by a moderator on 17-Jan-2026.]

Hello!I encountered an issue today where children of a frame (auto layout or not) who have constraints set of any kind (Top + Bottom & Left + Right shown in video demo) will only grow in increments of 1px. In Auto Layout frames with Fill it works correctly, but not with non-Auto Layout. I think this is a bug! Or if it is working as expected, I think the expectation should change, as it does not meet my user expectation!Thank you!Sam Smith

I use percentages in a project for the letter spacing. I can’t use variables to achieve this value. It always defaults to pixels.

So, in our design system we want to apply variables to our text styles to ensure consistent letter spacing. Since we want to use different letter spacing depending on the mode (light mode/dark mode), we’d like to apply these variables to the text style and assign different values to them.However, as Figma uses percentages for letter spacing, it’s not really possible to achieve this properly. Variables can’t hold percentages, and therefore we can’t fully make use of this feature at the moment.I hope Figma will soon allow us to choose the format we want to use for letter spacing globally.Does anyone have a solution for this problem?

Love the new Typography Variable release, but it falls short for our use case. Our goal is to use variable modes to switch styles between our 3 brands. 2 of those brands use all caps for headings, the other brand uses sentence case. We need to be able to bind a variable to the case of a character style (As typed, Uppercase, Lowercase, Title case, Small caps). Without this capability, when switching modes from brand 1 to brand 2 for example, we are getting the default case for the character style (sentence case coming from brand 1). We would then have to go through our designs and manually type in all caps for all instances of headings in brands 2 and 3. Certainly not ideal and will lead to inconsistencies / places where manually typing in all caps are missed if we went this route. Until binding a variable to the case of a character style is an option, using typography variables isn’t feasible for our use c

Hey Figma team 👋We’re exploring ways to use Dev Mode annotations more heavily in our workflow so that we can move away from sticky notes and keep all developer-related notes/context directly in Figma.However, we’ve hit a challenge — users with “View only” permissions can’t see annotations. This becomes a blocker for our team because our PMs (who only need viewing access) are unable to read these annotations. It’s important that they can, since they often need to reference these details when writing specs and collaborating with engineers.We’re on an Enterprise plan, and while we understand that edit access is required for creating or modifying annotations, it would be really valuable if view-only users could at least read existing annotations.  Is there any existing workaround to allow this visibility? Or is this something that could be cons

ProblemWhen working on long-term social media strategies, we need to create both visuals and the accompanying copy. Currently, Figma Buzz focuses on visuals, but there’s no dedicated space to add or manage related text content. This forces us to switch between multiple tools or documents, which increases the risk of losing information and slows down the workflow.Proposed SolutionIntroduce a dedicated text area within Figma Buzz, similar to the text blocks available in Figma Slides. This would allow us to write, edit, and organize copy directly alongside the visuals.Why This Would Be Useful Centralizes all content (visual + copy) in one place Makes collaboration and client approvals easier Reduces context switching between tools Minimizes the risk of missing key information

When marking up a file with comments (comment tool active), if I hold space and activate the hand tool, when clicking to drag (pointer turns into hand icon) instead of dragging a new comment is drawn on the page. Guessing this is a bug not a feature? Just would like to use the hand tool shortcut without creating new comments - this forces changing back to the move tool to cancel out each time

I’m trying to make our design system easier to search by including alternate search terms/tags in the description of the component, and it’s a frustrating experience. I can’t rename the component itself, because we want to keep naming 1:1 with an existing web framework, so I’m adding in alternate search terms in the descriptions.Using the component description works to an extent, by which I mean that the component will appear… somewhere in the middle of a long list.For example, if I search for “dropdown”, my asset panel results will contain a mix of dropdown menu items, icons with “down” in the name, the actual component I want to highlight somewhere in the middle of this, as well as some assets that are completely unrelated to dropdowns if I have other libraries turned on in the document.Many of our components are nested and contain several items for constructing menus (dropdown/item, dropdown/separator etc.) , and these are often shown with equal or more prior

Hi all, ChallengeI regularly need to check all comments on a Prototype and it’s not always convenient to switch to Editor view to see all comments. Currently comments in Prototypes are presented per frame which requires me to scroll through the frames until I find comments.SolutionAdd the Only current page filter from the Editor view to the Prototype view comments list  Or add Show all comments filter What do you all think?Btw, I do use desktop notifications too.

It would be so beneficial to add a “Go to instances” feature to Figma, just like the existing “Go to main component” feature. In crowded design teams, it is so hard to track the use cases of a main component, since a variety of different designers may have used a single component in so many different screens and cases. Especially while constructing or revising a design system, this feature is extremely needed. It would save a lot of time and effort in trying to detect the specific needs and requirement or the necessity of a component.

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.

The title case isn’t accurate. As it also capitalizes: articles (such as “a,” “an,” and “the”) conjunctions (such as “and,” “but,” and “or”), and prepositions (such as “at,” “by,” “of,” “to,” and “on”). In my opinion, the better naming would be “Capitalize”. Figma team can also consider adding “Title Case” and “Sentence Case” options separately.

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.

Since Figma does not support going back to previous views, it is quite frustrating to switch between pages. Would you ever allow the same file to be opened in another tab, but not in a new app window? This would become very handy to switch between pages in the same file.

I often work across multiple pages within a single Figma file/project, and I’d love the ability to open different pages as separate tabs in the desktop app—just like I can open different files. Currently, I have to either open and close multiple pages many times to get what I need from other pages, use multiple windows or duplicate the file, which isn't ideal for managing design systems or multi-page projects.This would greatly improve workflow efficiency for designers managing large files or working across different sections (e.g., desktop vs. mobile layouts) simultaneously.Please consider adding support for tabbed views of multiple pages within the same file.

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.