Share Your Thoughts

I work in a large design team (50 designers) in a fast-growing company. The product is complex and has many different flows and variations. I often find myself wanting to find a specific screen in Figma from a specific part of the product. If we had a great index internally that we kept very well groomed, this wouldn’t be a challenge. But it is not the case. Most of the time, I really on asking in Slack if anyone knows where I can find a recent-ish version of this or this in Figma, wait, and 50% of the time another designer finds something. What if we could do reverse image search in Figma like we do in Google? I screenshot a part of my product I use it the reverse search in Figma Figma shows me the files, and where in the files, that have designs that match very closely my screenshot I can grab my screen and start designing!

I was having internet connectivity problems, so I was met with the Connection Error screen:Connection error screenshotThe “Try again” button doesn’t seem to do anything.I had to go to the tab, right-click it and use the “Reload Tab” option. 

I have a button which is created in the library file in the way it has hover state while hovering:The same button, according to the WCAG AA requirements must have a tooltip on hover (and when it’s focused while using keyboard navigation but it’s not the case here) https://www.w3.org/WAI/WCAG22/Understanding/labels-or-instructionsThe current interaction mechanism doesn’t allow to display a tooltip on hover from the project level as the hover variant interaction is already reserved on the library level. The screenshot from the project: Theoretically I can c

My suggestions is to allow users to include annotations and / or measurements  when they export images. Seems that we can’t currently do thisThe user benefits –allows users to share images with annotations and measurements when creating images to be shared wither wider stakeholders and creating documentation for other platforms. If we can’t export annotations and measurements, then for those instances requiring annotations in an export as an image, users won’t use the annotations feature, and revert to creating “Notes” manuallyHope this makes sense

Often I’m adding autolayout around a frame/component/element, and the default vertical and horizontal padding is 10px. As well, the gap applied is 10px. It would be amazing to set the default padding and gap to auto-layout elements. This would help with keeping your files clean, but also, to ensure that redundant CSS properties are not added to dev mode output. Clearing and resetting these properties takes time and often the gap is not cleared due to the property not having an affect on single children. Thanks!

Please introduce a more prominent visual indicator for active branches in the main file.Currently, the branch indicator appears as a small footnote near the page title, which is easy to overlook. Because there are multiple ways to create a new branch, designers may miss the moment when an active branch is present and unintentionally continue working on elements already affected by it.This can lead to merge conflicts and significant loss of time, as changes may need to be reverted and redone. A clearer and more visible indicator would help prevent these issues and improve collaboration within teams using Figma.

Would love to see metadata added to top-level items on the canvas or in the layers panel, and stored somewhere discreetly. For example, it’d be really advantageous for large teams—and editors specifically—to have the ability to view the timestamp/authoring details of a specific section or frame (e.g., when it was created, who created it, when it was last modified, etc.).

Pretty simple ask: I want to move a page from one Figma to another. I don’t see a way to do it. Select All + Cut + Paste is not a good solution as I might have locked objects that don’t come with the copy and there might be properties set on the page (background color, etc.) that I might lose.

I frequently share notes on designs with a group of developers without knowing which one will work on what I’ve designed. I’d love to be able to tag several in a comment via a “group” I’ve created within my team (eg- “@FrontendDevs”) How are others handling this?

Background: I am a developer, and I use Figma exclusively in Dev Mode via the web interface. I don’t have (nor do I want) any edit access to the designs I’m implementing. That’s for the designers. When the Measure tool appeared (the ruler icon on the upper left toolbar), I latched onto it very quickly. It greatly improved my speed of accurately implementing a design. There are certainly other ways to measure things in Figma, but they are all transient. The best part of the new tool was that I could quickly measure many different things and have all the measurements persist so that I could then just refer to them during development. It was a simple yet well-conceived tool.

Hey everyone,This has been driving me (and apparently hundreds of others) crazy since 2021: there is STILL no native way to properly move or duplicate an entire page from one Figma file to another.Copy-paste or “Select All” destroys page background/grid/rulers, breaks prototypes, loses comments, turns library styles into local duplicates, and forgets locked/hidden layers. Duplicating the whole file then deleting pages is the only “workaround” — but it’s a nightmare with 50+ page files or design systems.I’m a fellow designer who’s fed up and seriously considering building a free Figma plugin called PagePort that would let you:Export any page (or batch multiple pages) with 100% fidelity (layers, auto-layout, constraints, page props, prototypes where possible) Import into any other open file in one click Choose Move (delete from source) or Copy Smart remapping for styles/variables/libraries + basic prototype r

As a viewer, I need to understand the design system variables—using the built-in variable manager—so I can clearly see the token architecture and color relationships across modes. This helps me decide which tokens to apply to custom components and how they will behave in both light and dark modes.

A few years ago there was a fix - The icon on the instance inherit color override, imposed by main component, when swaping icon or changing variant. Great!but… Problem If I modify the icon color on the main component - change color style or manually pick new one, doesn’t matter. The instance with swapped icon doesn’t notice the change! Steps to reproduce:Place an instance Swap the icon on instance Change variant's (main component) icon color Instance's icon color will remain not updatedNote: Of course, all layers properly named to keep the naming integrity. The example:

I’m trying to create a horizontal scroll section (basically a simple carousel) in Figma Sites, but it looks like this interaction isn’t supported at the moment.Has anyone managed to make horizontal scrolling work?If it’s currently impossible, is there any workaround or alternative to simulate a carousel?

Hey everyone I wanted to share my workflow for designing SEO-optimized landing pages in Figma, something I’ve been refining while working with clients here in Nepal.A lot of designers focus purely on visuals, but I’ve learned that small design decisions can directly impact rankings, page speed, and conversions.Here’s a simplified version of my process:1. Start with search intent (not design)Before opening Figma, I map out: Target keywords User intent (what they actually want) Competitor page structure This helps me design pages that match what users are searching for, not just what looks good.2. Structure comes firstInside Figma, I focus on layout hierarchy: Clear H1 section (above the fold) Logical content flow (H2, H3 sections) Scannable layout (short section

We want to use it to link design variables to the design tokens in our application. Our company runs on a Professional plan. There are only 10 users that need access, so we don’t have any need to go to an Organization or Enterprise. I saw the same question here, but it wasn’t answered and just pointed to the Plugin API which has an entirely different use case.

I’m working on the initial ideation and brainstorming solutions using Figma for the product I’m working on. I’m genuinely happy with the results it has generated on rough level, it has helped in making my execution process faster. But I have been consistently seeing a pattern where in certain designs it provides certain features or context which are unexplained or we’re unable to understand. I tried asking within the chat itself to explain what exactly that feature means and how is it relevant in our product but it wasn’t able to answer. Also the point and edit features has been working very slow. I was assuming if it is getting heavy for make to prompt and edit / also answer questions about feature’s vagueness in the same chat estate. Shall we have a different chat estate just to ask questions about what features it has exactly designed, if it has ability to explain the context it will be helpful for us to use it or rather shape and align with our use case if it shall surpass. 

Currently, the "While in view" trigger is too binary. The animation often doesn't feel right because it won't trigger until the entire layer is within the viewport, or it fires the moment a single pixel touches the edge. This makes it impossible to time smooth reveals—like headers or hero images—so they glide in exactly when the user is actually looking at them. It makes high-fidelity prototypes feel "jittery" and unpolished.The Suggestion: I’d love to see an Offset (or Threshold) property added to the Prototyping panel for all scroll-based triggers. Custom Thresholds: Let us set a pixel value (e.g., 200px) or percentage so we can control the exact moment a reveal starts. This ensures the animation happens in the "Active Zone" of the screen, not just the moment the layer edge appears. Better Handoff: This takes the guesswork out of the design-to-dev process. Instead o

It would be highly beneficial if Figma provided a way to view the creation date of a project. Currently, there is no clear or accessible indication of when a project was originally created, which can create challenges in project tracking and management.Having visibility into the project’s creation date would help designers and teams better understand project timelines, especially when working across multiple files or collaborating in larger teams. It would also improve organization, auditing, and version control by providing clear context about when a project started.This information could be displayed in the project overview, file details panel, or alongside metadata such as last edited time. A simple and visible timestamp would significantly enhance usability and workflow clarity.

EDIT: i can already do this by using the Gap function.It’s still almost impossible to design for fluid widths in FigmaBut with the new Grid Beta, it is now possible to set up for example a 12 col grid system , see my screenshot:https://prnt.sc/fetKFckcQpT4 Basically I set the colums to 1fr, and i set the gutter to my design in pixels. This is how most grids work on a webpage. Now if i rescale horizontally, it keeps the gutter, and scales the grid like in real-life.But on smaller screens the gutter usually need to be smaller, and it would be extremely tedious to manually replace 12 gutters for EACH and every frame i use this on a webpage (potentially hundreds)So if we could use variables to the colums in Grid Beta, that would be just one click solution and we almost got a working fluid system in Figma.

Hello,Looks like Figma doesn’t give you an option to chose dark mode colors when you assigning semantic tokens, in the menu only light mode colors even tho I have dark mode too in my primitives.So that means I can’t use different color pallet for the dark theme (in case if I’m actually want to use different colors in my dark mode completely different pallet). I’m I missing something? or It just feature they didn’t thought about yet? or never will?

Can’t do truly responsive tables in figma.I design complex applications that require a lot of tables. Currrently, there are two primary approaches to responsive tables in figma: row-based and column-based.In reality, neither of these is fully responsive. In row-based ones, when a cell's content expands in height, all cells in that row adjust accordingly. However, if the content expands in width, the cells that are supposed to be in the same column don't follow suit because there is no relationship between them. The same happens with column-based tables, but the issue lies with the height. There is another approach called grid-based tables that almost solves that issue. The downside is that you can't use components in a simple way, like slots. If you need to create a prototype with hover effects, the interaction

Our design system leverages mix blend modes for hover states so our icon buttons appear on any background color and remain accessible, without needing separate hover–on-primary, hover–on-secondary, etc tokens. We use multiply for light theme, and screen for dark theme. It would be really awesome if we could apply blend modes directly to the color variables, OR support blend modes as variables in general. Our current work around is to apply the blend mode directly on each component variant, but this requires us to define separate light and dark theme variants. would be great if we could use variables here to have it automatically switch between light/dark.

It would be beneficial if Figma included the option to enlarge the interactions panel. Reading all the conditional and variable interactions within the small preset frame size can be challenging. Enabling users to expand the panel size, similar to the way the variables frame can be expanded, would make it easier for users to review the interactions they have set. Being able to copy interaction would be extremely helpful and reduce redundant work

The title just about summarizes my issue. Developers until recently had access to ruler measurements and annotations with their Dev Mode seats. Recently, these tools were stripped from them. I don’t understand why only designers can measure distances or leave annotations, so long as they are not editing files, why should Devs be unable to annotate or inspect files using the tools Figma designed for Devs to inspect files?Good design practice in Figma often requires us to build things differently than they would be built with actual HTML/CSS. with Autolayout in mind, it’s better to determine the space between objects rather than apply padding to the top of Divs as many devs would do. However, when a dev wants to measure the total space between elements, they should be able to use rulers to make the measurement THEY need and not the one Figma decided they should have. Why were these tools stripped from Developers? We’re already on an Organization plan, paying quite a lot