Share Your Thoughts

Feature would be a search of some kind, where all interactions containing a specific variable (whether that is making a change to it or it is included in a conditional). When I have complex prototypes involving many different variables, and I want to refactor it to simplify, this can be very difficult.

Please make Dev Mode Annotations visible by all roles, not just Full Dev Mode seats. This can become costly for users needing context but not all the other dev-mode features. Here’s the scenario: We have a dashboard, with cards showing a customer’s account status. This status can be mapped from multiple back-end statuses, to show just one front-end status. For example, any of the following could be mapped to a single status known to the customer as “Completed”: canceled, terminated, sold, complete, etc. This is something that the developer needs to reference, but then also the PM needs to reference in writing tickets (who doesn’t need full dev-mode access), the QE needs to reference for testing automations, and various other individuals on our team. Placing it in a comment makes it less clearly attached to the specific piece of the design, and requires us to keep documentation dispersed among different tools (Jira, Confluence, Figma etc). Simply making Dev mode annotations visible to v

Hey,I draw a lot of icons, and almost every stroke I make needs round caps. Right now, every new line, arrow, or pen path starts with Figma's default cap, so I manually switch the start and End points to Round on basically every layer. If I miss one, the whole icon set looks off.Could we get a default for this in Preferences, next to Nudge amount? Set it once, and every new stroke uses it. A default join setting in the same spot would be great too.For now, I duplicate an old line instead of drawing a new one, or run a plugin after. It works, but it's a chore for something that should stick.

You can duplicate a file, and create a branch of the current file but when your in a branch you can only duplicate to a new file not a new branch. I always have this need I create a branch and don’t want extra files I just want to create extra branches off of the branch not the original file which has been significantly modified at this point.

Fractional units and hugs are definitely a welcome addition to Grids, but what’s still missing is the ability to assign both the number of columns/rows and colspan/rowspan to variables.We’ve defined our website breakpoints as modes so we can build components that automatically adapt to the viewport (for example, a 50/50 layout that stacks on mobile). Right now, the only way to achieve this is by storing fixed column-width values for each breakpoint and use them in combination with horizontal auto-layout. It works, but it defeats the whole purpose of Figma’s grid system.Assigning variables directly to the grid would allow every component using that grid to automatically adapt based on its current mode (breakpoint). This would make creating mockups across different breakpoints significantly faster and more efficient.

Currently the activity log requires a full email address to do search. It would be useful to search by first or last name or a part of the email address in some cases.

I am the Figma admin for my org and it would be really useful for us to have a single screen with a list of workspace and billing admins for all groups that we can use to manage. Currently, we need to go to each billing group or each workspace and then see the list. This creates a problem as one person can be present as an admin of multiple groups and the only way to know will be through excel export. Instead what I suggest is to have one screen with the admin list for all workspaces and billing groups that we can use to manage admins.

I am the Figma admin for my org and we have workspace and billing groups with a long list of admins. I’d like to see a way to scroll through that list easily. Currently it feels clunky.

Whose idea was it to put the little icon for the new AI agent so close to the upper right corner of an object? I can’t tell you how many times I’ve gone to adjust the size of an object and accidentally opened the agent. Each instance doesn’t take that much time, but when you do it countless times a day, it makes work that normally feels fluid feel disjointed. If I want to open the agent, the option in the left nav panel is super easy to access. I don’t need the agent connected to every object I touch. I’d like to see the user research (or lack thereof) that made team Figma think this was a good idea. You’re assuming the agent is so helpful and so needed that people need it right there. That’s confirmation bias at it’s finest. Please take this away or at least move it!  

Switching to the Enterprise license and would like the ability to assign a user to multiple workspaces. I see there is an option for folks to be invited to teams in different workspaces, but it would be more efficient if we can easily add and see how many workspaces folks are assigned to. In our organization we do a lot of cross collaboration, across the workspaces.

Hi Figma team,I'd love to see sorting preferences persist across sessions in the Projects view. Currently, every time I navigate into a project and return to the home screen, the sort order resets to default.Our team numbers all projects (01, 02, 03…) to maintain a clear workflow overview. Having to manually re-apply alphabetical sorting every single time is a small but repetitive friction point that interrupts the flow.It would be great if Figma could remember the last used sort order, ideally per user or workspace. This seems like a relatively simple improvement that would benefit many teams who rely on consistent project naming conventions.If this is already possible and I'm missing it, I'd love to know how.Thanks for considering this.Best,Justin Eleveld

Every project I work on ends up with a huge number of layers. Without proper organization, it’s easy to get lost in them—like trying to find your way through a forest in the dark.The idea is to let users add tags—colors, icons, stars, or other markers—to layers, layouts, groups, and so on, making them stand out from the rest.For example, take a typical project with at least 100 layers. With this feature, I could mark anything that shouldn’t be touched in red and anything that needs changes in yellow. This would not only help keep things organized but also serve as a way to leave visual notes in larger projects that you work on for weeks at a time.If you like this idea, please support it with a like (or even a comment). I’d really appreciate it. Thank you!I’ve also created a concept design showing how I envision this feature being implemented.

Page dividers or spacing? 🤔 Cause this hack to use a page to fake it is in 99% of all Figma files I’m in. Does anyone else experience this?

It would be great to have more information available of which component changes got published in the version history. When a change needs to be reverted, it’s hard to know which version needs to be recovered when no or barely any information was providede with the publication of components.

When using Find & Replace with Arabic text, Figma always navigates to the first matching result starting from the left side of the canvas.For RTL languages such as Arabic, I’d expect the navigation order to follow the reading direction and start from the right side instead.This becomes especially noticeable in flows where screens are arranged from right to left, as Find & Replace jumps to a screen on the opposite end of the flow first.It would be helpful if result navigation respected the text or document direction for RTL languages.

Please add the “auto” value to the gap in the grid layout. The “auto” value can be applied to flex layouts but not to grid layouts 😁.

I posted this wish in comments back in 2022 and 2023. Am I the only one that wants a nice elegant curved arrow option for the connectors? 🙂 It makes diagrams look so much friendlier and aesthetically pleasing, instead of orthogonal curves, straight lines or angled straight lines. Thanks all! Ben

Love what you've built with Motion, using it almost every day.One thing that slows me down is the lack of native audio support. Having to render and add audio in a separate tool gets cumbersome, especially when working in bulk.Would love to see that integrated down the road! Also, any plans for HTML exports?I've looked at plugins but they feel a bit pricey and not very intuitive. Keep up the great work! Peace ✌

We need a side-by-side visibility!The switch from a floating/movable Variables modal to a full-screen tab has hurt my workflow.I need to see the canvas and variables side by side — to check a token change against the design, compare values across modes, catch mismatches before they ship.Switching back and forth constantly is tedious! This isn't just slower — it's causing errors. Editing without seeing the canvas means working from memory instead of visual confirmation, which leads to picking the wrong step in a scale or missing something like a contrast issue.Please! make it float again. 

Changing the Variables panel to be a tab along the side that takes over the view instead of a panel I can move around has impacted by design flow. I would often have the variables panel open side-by-side to my designs so I can view/add/update variables and build design simultaneously. Now I have to flip back and forth causing frustration and slower process.

The recent figma autolayout update has brought up conflicting emotions. From one point it’s great that the autolayout would work closer to code, but on the other hand for teams that do more complex projects than Web UI, this creates a loooot of issues. 3 things in particular, that I know for sure, will break what we've been using in case of complex layouts:"Padding now always gets the room it needs" - Often when necessary, I relied on the fact that you can set auto-layout frame size to 0 and add paddings inside to allow precise position of elements without affecting the size and position parent and sibling frames. Now that won't be possible. ⁠"Inside strokes counting in autolayout" - again pretty sure this will break layouts where inside stroke was used. ⁠"Stacks with gap set to auto no longer overlap" - A lot of cases it's better to have parent in the desired size than have the parent rely on the children. Then we will get uneven distances and paddings in some cases. All of this would

I’ve been thinking about how much difference good file organization can make when working on a design project.For example, how do you usually organize your Figma files and pages? Do you have a specific naming system for layers, components, and sections, or do you keep things more flexible?I’d be interested to hear what organization habits other designers have found useful, especially when multiple people need to work on the same file.

Hey everyone. I would like you to consider the text animation feature in Figma Motion. What I mean by text animation is animating text either word by word, or character by character, like the kind of animation we see in Saas promo videos. With other effects to the text like gradient color change that moves along the text reveal. That would be really cool :))

Hello! I noticed that in the Figma article What is Human Computer Interaction?, the author writes:Dialogue. Use clear and concise language to communicate task completion, like  “Purchase Confirmed” pop-ups after completing an online order. On Shneiderman’s website, he writes: Design dialogs to yield closure.Sequences of actions should be organized into groups with a beginning, middle, and end. Informative feedback at the completion of a group of actions gives users the satisfaction of accomplishment, a sense of relief, a signal to drop contingency plans from their minds, and an indicator to prepare for the next group of actions. For example, e-commerce websites move users from selecting products to the checkout, ending with a clear confirmation page that completes the transaction. I understand that they are variations of the same word but I would argue that in this context, it is important to use dialog because Schneiderman is referring to the importance of the graphical interface  (li

Hi Figma Team,I’d like to request the ability to temporarily hide the selection bounding box and handles of an active object without deselecting it.The Problem: As a UI design tool, our canvases are filled with rectangular containers and elements. When fine-tuning pixel-sensitive details—such as adjusting complex borders or multiple effects on rectangles—the selection bounding box directly covers the edges and working area, making it very difficult to accurately judge visual contrast. Industry Standard: Other industry-standard tools like Adobe Illustrator and Photoshop already solve this by letting users hide bounding boxes (e.g., Hide Bounding Box / Show Transform Controls). Having a similar toggle or shortcut in Figma would greatly improve high-precision UI work. The Solution: A quick shortcut or option to hide the transform handles/box on the canvas while the layer remains selected.Thank you for your incredible work on Figma!Best regards,Aleix