Share Your Thoughts

I think the idea for figma sites is great! However there is some issues I am having. There is no way to connect a backend DB to the site that I have seen. I want to make my site password protected so have made a login system and Figma Make has created an authentication for it which is great and works, but if you type /home in the address bar it takes you into the site bypassing authentication.  The second issue is that there is no way to access the files behind the site. You can use figma make to code components which is cool, but trying to make a site-wide search bar isn't working because the code can't seem to go across pages so can only search things on that page which is pretty pointless. We need Figma Make that has access to all of the sites pages for better context. Another issue is that it's hard to redesign something once it has been coded in Make. If you design something and send it to Make then Make creates an image instead of SVG so it doesn't look great. But also means you

Context and ProblemFigma's current Instance Swap Override is a useful feature for swapping singular instances within a component. However, it becomes cumbersome and time-consuming when applied to more complex design patterns, such as:Managing dynamic content for cards, sidebars, and templates. Creating unique combinations of content within reusable components.Currently, designers must create a new component for each unique content combination, which leads to bloated libraries, repetitive work, and a loss of efficiency. This approach also lacks flexibility for managing dynamic layouts, which are more naturally represented in code through structures like parent-child relationships in HTML or Children props in React.Proposed Feature: Component "Child" or "Slot" OverrideIntroduce a new override type, referred to as "Child" or "Slot," allowing component creators to define designated areas within a component where users can **drag and drop any content**. This feature would streamline the wor

I can't believe Figma is forcing this change on us. UI3 is, without a doubt, the most unfriendly design possible. It has made my workflow painfully slow and incredibly unproductive. What’s the harm in letting people CHOOSE which UI works best for them?I always thought switching to UI3 was a HUGE mistake, but I never felt the need to comment on it because UI2 was still an option. Now that you're FORCING this change, I have to speak up.This is NOT an upgrade. It’s a downgrade in usability, efficiency, and user experience. Figma was supposed to be about flexibility and user-centered design—so why ignore the feedback of those who actually use the platform every day?Give us back the choice. Let people stick to UI2 if they want. This forced migration is a slap in the face to long-time users who built their workflow around UI2.

Hello, I used Figma site a lo recently and here are some feedback :The requirement to use a subdomain is quite restrictive. For example, if I'm forced to deploy my site on www.domain.com, I also need to redirect domain.com to www.domain.com to avoid users being blocked or unable to find the site when simply typing domain.com. This redirection then has to be set up manually on the server side, whether through a .htaccess file or an Nginx or Apache configuration. I have the technical skills to do this — it's my job — so it didn’t take me long. But it's far from accessible for someone who isn't a developer. In my case, the simplest solution would have been to host the site directly on domain.com. Dynamic components (e.g : carousel) which have breakpoint variants do not adapt responsively to the screen size. This cause major interface problems. The problem is not observed for static components. Buttons do not have focus states (interactions) which is highly problematic ATM for designing we

I love that with the add-on I can better integrate figma designs to google workspace. It woul be awesome if the chip conversion would also work for google sheets currently its just a link, even if the add-on is installed.  I would love to have it like in google docs: 

In my project, a primary color variable needs to be used with different opacity levels to represent various states. Unfortunately, variables that reference the primary color variable cannot have their opacity adjusted individually unless the alias is detached first. This significantly affects color consistency across the project. I hope a separate opacity setting can be added.  

To add an out animation for an object in Figma slides, I have to create a new slide. Plus, let me trigger the object animation after I change my slide. I don’t want to double-click if I have both a slide transition and an object animation.

Is it possible to change the units on the ruler without a plugin? If so would love to learn how! Trying to make a research poster on Figma, and finding it difficult to confirm that the scale is correct in inches.

I'd like to suggest being able to select different colours for different measurements, for instance blue for 8px, pink for 16 px, so on and so forth. It's easier to standardize my designs, and to help people quickly get the different paddings and margins. Thank you 🙂

Measurements should always display above everything in the UI including annotations. Currently, when I try to get the distance between some elements, it is becoming difficult because it is being hidden by the annotations I have added. Also would love the ability to change the location of the annotations and if they should display to the right/left/top/bottom of the element you are annotating.

Currently, it’s possible to hide both sidebars. I usually work on a smaller screen, in which this feature becomes helpful when trying to review designs on a canvas.I think it would be useful if we are able to hide either just the left sidebar, or just the right sidebar, along with the current feature of hiding both. Hiding the just left sidebar would help designing be more efficient on smaller screens, as having access to pages and layers is not always necessary.

Figma Buzz looks very promising for our team, but there are a few features that our team will need in order to use this product.Autolayout on the parent frame. Email graphics are a great use case for Figma buzz, but often times assets need to adjust in height based on the headline or copy length. Persistent linked data. If I click out of the import pane, all the text linking I did just disappears. Linking groupings of pages. A simple application is a card with a front and back side. The variable data might only be on one of the sides, but I’m still going to want to export the front and back for each card. I need a way of grouping the front and back as a single multipage document that applies to bulk creating assets and exporting them as multipage pdfs. Batch process using template based on data. For example, use the HR department business card template when the field in the “department” column is “HR” and the Finance department business card template when the field in the “department”

I want to favourite some files. But I don’t want to always switch teams in order to see them. That should be a personal favourite that will always show. Regardless of team switch. 

While cleaning up my file, I hid a frame that I didn't want visible at the time. I didn’t want to delete it because it was still useful. Months later, I needed that screen again. I tried searching for it using keywords, browsed through pages, and even looked through the version history.I ended up reviewing five months of version history, scanning for keywords to locate the screen. I eventually found it—it had been hidden all along. The content was never deleted. But because it was hidden, it didn’t show up in search results.This was frustrating. Search is supposed to make it easier to find things. Just because an object is hidden doesn’t mean it stops being part of the file. Excluding it from search reduces the usefulness of the feature.Request: Please make sure hidden elements are still indexed and searchable. At the very least, give users an option to include hidden content in search results.

Following a change in logic or flow we have to update the same thing in various screens, but they’re not always right next to each other. In bigger files it can become hard to keep a good overview, and designers might miss instances where something would’ve had to be updated. To avoid this, I have to manually add a new comment to every single instance, which makes it really messy and hard to keep an overview if there’s more than one change to be done in different screens. IDEA:It would be great if I could tag screens within a page that relate to one comment / action item, so the designer can see right away all the screens where the same action has to be done. 

Hello,We’re currently migrating our studio portfolio to Figma Slides.Our main concern is ensuring clients (who will discover the portfolio for the first time) can navigate through the slides easily and intuitively.❌ The problemWe’ve noticed that new users often struggle with Figma Slides’ default navigation, especially when trying to go back to the previous slide:They must use keyboard arrow keys, which many people aren’t used to anymore (since most sites and tools are fully operable by mouse)Or they have to hover on specific screen edges to make small navigation arrows appear👉 Overall, the default navigation is not intuitive, and this creates friction that undermines the purpose of a clean, user-friendly presentation.✅ Suggested improvementsWe believe the following features would significantly enhance the experience.Each is useful on its own, but ideally, they could work together for maximum flexibility:🖱️ Better navigation toolsAbility to add navigation buttons directly from the to

This, but in Figma.Making it possible to paste elements into an already existing component. Im not talking about instance swapping. That would mean creating new components for what i wanted to put into my component. I dig the way webflow is handling it.   

在设计文件内部增加文件夹功能，且可以多层嵌套，这样方便对不同模块的页面进行分组管理。

First and foremost, branching is a great addition to Figma, thank you! Here is some background on how our Style and Component libraries are setup: Project: Design System File 1: Styles (text/color/other token styles) File 2: Components (primitive components, larger organisms, and some templates) What I’d like to do is create a branch in File 1 and change our brand color and add some text styles. I’d then like to “stage” this branch so that I can reference it in File 2 (another file) and test some of the changes downstream in components to see how they might look before merging and publishing File 1 (in case there are things I need to change/add). I would love some suggestions on how I might accomplish a workflow like this, or if it’s something that might be supported in the future. Thanks!

It would help with the prototyping and testing workflow to allow users to select multiple colors in the “Selection colors” section of the property sidebar on the right. When you select colors you will be provided with an option to “create styles form selection” and to “add to variable table...”This will enhance the initial UI testing and research phase of UIX design allowing you to easily and quickly apply your final styles and colors to a design system’s style set and variables.

With the rise of LLM-based “Vibe Coding” tools like V0 and Cursor, I’m expecting Figma to address this shift at Config 2025. This year has been transformational—it's now faster than ever to validate early ideas and prototype them with full interactivity. This speed benefits designers, teams, PMs, and users alike, making rapid iteration and validation a core part of the process.In my practice, we quickly realized that traditional wireframing in Figma no longer felt as useful—especially since we’ve never been big fans of its prototyping layer. Figma’s strength has always been in UI design, but we’re now facing new bottlenecks:1. Bridging the gap between AI-powered coding tools and high-fidelity UI in Figma.2. Defining components in a way that makes them easily usable in these new workflows. (What does a design system look like in this new landscape) As these AI-driven tools evolve, the question is: how will Figma adapt? Will they double down on their UI strengths, improve handoff workflo

Problem:Product Owners (nondesigners) will often times share early work in progress without the designer knowing. This ends up being a headache of dev comments (30+) pinging with comments that designs are not complete or components are not built correctly. Solution:Designer who is the owner of the file can assign specific users/staff so they get all push notifications/emails  Reason:To help each team member own accountability for the consequences of their action. If a product owner wants to share an incomplete file to 100+ people in the organization without communicating the designer. Let’s ensure the push notifications/emails get sent to the product owner that initially share a file too early to help respond to each comment. 

I suggest having this feature in Figma since we are on a paid plan. Especially when we have so many frames/screens to be exported (eg. 170+) it’s a really huge filesize. And it’s not allowed to use an external PDF compressor platform when our projects are confidential. So far, I can only convert the frames into individual PNGs/JPGs, replace the frames with these image files, and export them into PDF. This is so time-consuming and troublesome.

It is now very unclear to see which files a person has access to. When a user has access to a specific file, you can’t see it anywhere in the admin page. It’s not very user friendly. I remember it being there in an earlier version, so please just bring that back. The files a user has access to should be shown in the sidepanel when selecting a user.   

Our UXR team has noticed an increasing issue with loading prototypes on Android devices. Are certain devices more susceptible to this issue? Sometimes refreshing the prototype once resolves the problem, but other times the prototype either fails to load entirely or crashes. Are there any recommended optimizations, or have others experienced this issue?