Share Your Thoughts

There’s a bug on grid. If I move a component with a vertical grid into another frame/component, it takes on a fixed property instead of fill

Hey there! I was also wondering if it is somehow possible to include also the layer of variant controls to be exposed or hid! I often have cases where I need to nest base components e.g. an icon wrapper providing me with the ability to select certain sizes, or color overrides and boolean props of an icon. I am now able to expose all of those or none, but I can’t restrict the users to only be able to select just some of those. What do you think about it?

I often paste screenshots into Figma – for documentation, comparisons, or quick visual discussions. But every time an image is pasted from the clipboard, Figma automatically compresses and scales it down.This makes text in the pasted image blurry and unreadable, which basically makes screenshots useless when trying to show interface details or discuss content. It also creates unnecessary friction in the workflow, since the only way to keep full quality is to save the image locally and use Place image…, which breaks the creative flow.I see requests for this feature that are several years old – time to fix it!

Hello. I was wondering if it is possible to have percentage values in variables, like setting percentage value for frame widths or shape sizes (etc.) that have variable modes applied to them? Percentage values could respond better to content that varies within a frame or frames within frames.

When presenting in Figma Slides, I would like the smart animate transition to be played even when going back to previous slide. Currently smart animate is only played when advancing to next slide, but not when going back to previous (then it’s just an instant change). This behaviour would not have to be the default, but having the option would be nice.

Currently, in order to check if a variable value is set correctly, you need to apply it to a text or field. It would be great to have a way to debug/inspect a variable in runtime, especially for those that are not displayed on screen.

Let’s say I… Create a variable for a background color Apply it to element Delete the variable Recreate the same variable with different background color The element now has a broken variable link, though it retains the original variable name. Is there a way to relink it to the new variable since the name is identical? I’d like to do this across a file without having to manually relink every variable and none of these options seems to do what I want.

Figma's current branching is a bottleneck. All branches must come from main.If one designer is working on Feature A (v1.1.0) and another is on Feature B (v1.2.0), the designer on Feature B cannot get updates from Feature A. They are blocked until Feature A is fully merged into main. This forces designers to either wait, or manually copy-paste work, which breaks components and causes errors. The Solution: We Need Git-Style Branching To fix this, we need three features that developers use in Git every day: Branch from Branch: Let me create a new branch from any existing branch, not just main. Update from Branch: Let me "update" my branch by pulling changes from any other branch (e.g., merge Feature A directly into Fea

Inside Figma make, it would be nice to be able to have the AI reference more than one library. We have atomic, molecular, and then our tokens in different libraries. Being able to just select more would be beneficial. It would also be nice to be able to select a variable mode for the AI to also use when referencing and building the experience. 

Auto-Layout has padding (inner spacing), but no margins (outer spacing). Currently the only 2 ways to add spacing is to: Create a spacer element or Wrap the items in another frame and apply gap spacing This creates a lot of unnecessary frames, and sometimes creates nesting so deep it goes outside the layers panel. Not sure if a technical limitation left this out of consideration in the first few versions of Auto Layout, but it would be much appreciated if it were included in a future version as it comes up as a significant limitation many times a day.

Figma makeにGithubのリポジトリを連携しています。このリポジトリに行った変更を、Figma makeに取り込みたいのですが、今の所、Figma makeからGithubリポジトリへのプッシュしかできず、双方向で同期できたらいいなと思っています。 Figma makeさんがGithubのプルに対応してもらえるのが最高なのですが、それまでの間は、どのように同期するのが良いでしょうか。今のところ、変更をFigma makeに直接コピペすることで対応しています。

Sometimes I work on a design and I get comment from my team. Then I may answer a comment or partially resolve it but don’t wanna resolve it fully yet. But then I click on it again and again because I don’t know which comment I have read so far. Maybe you could add a state for partially resolved or opened comments. Like turn them green or something.,

the ability to expose color variables (and other variable types) as component properties, similar to how text variables can be exposed today.Right now, designers have to manually switch modes from the Variables panel, which is less intuitive than using component properties. Being able to expose color variables directly would make components easier to use, reduce variant overload, and better support variable-driven systems.

Ever wondered how a few clicks can get you from one place to another with ease? That’s the beauty of thoughtful design. A great cab service app is not just about getting a ride. It’s about creating a smooth journey for users from start to finish — and that starts with design.When I first began designing a concept for a cab service interface in Figma, I realized how essential structure and flow are. Every button, color, and icon needs to communicate trust and simplicity. With Figma’s collaborative features, I could quickly mock up wireframes and invite feedback from other designers, which made the creative process feel more human and dynamic.Transitioning from low-fidelity wireframes to high-fidelity prototypes was an exciting part of the process. It’s in this stage that the design begins to feel alive. Adding small animations for ride confirmation screens or micro-interactions

With "Text-wrap: balance" headlines could be made more readable and visually appealing.Here’s how it could look: 

Auto layout behaviours are just different, hugging barely ever works, I can’t use fill reliably. You can overlap blocks but you can’t really merge them… which becomes problematic because then things like hug or fill breaks easily. Rearranging is an absolute PITA. Why can’t I just move a row up or down? I can’t even select a row. I understand that there was a reason for changing the expected behaviour but this feature is just not practical, it far too cumbersome to use. I really wish Figma would pay attention to refining and improving things instead of shipping new and shiny things all the time. I haven’t seem any improvements to grid so I’m assuming it’ll be staying like this for the foreseeable future.

Hi Figma team,It would be great if we could see which team members are currently active in the workspace level — for example, a small list or sidebar showing online collaborators with their profile avatars as you already have inside the files with Spotlight.By clicking on a teammate’s avatar, we could jump directly to the file they’re currently working on. This would make collaboration smoother, help teams quickly locate each other, and reduce time spent searching through shared projects.This will help us to collaborate better specially during design reviews.Thanks for considering this improvement!— Margarida

About the behavior when drag-and-dropping multiple images from a file browser onto a FigJam board. I often use FigJam for raw data analysis in my work. Specifically, I line up a wide variety of visualizations, add markers, and inspect them visually to analyze the data; FigJam’s features are a perfect match for this workflow, and there’s virtually no alternative solution. When I paste a lot of images onto a FigJam board at once, they’re arranged in a default kinda “automatically tiled” layout. It can even consider size of each image and arrange them into the most ”compact” form automatically, how smart it is.current default behavior For my use case, it would be very helpful to have modes that place them “in a single horizontal row” or “in a single vertical column,” which would greatly

The Problem: Collaborating with stakeholders often requires many content updates & iterations (text, image, etc). I think most content writers/stakeholders could easily make these updates but would require editor access, giving them unneeded (& often unwanted) edit permissions. Suggested Solution: Provide a Content Editor role in Figma that allows a user to: Update text layers Update image fills Anything else? Additional features could include: Editor can lock/unlock editability of content per layer Ability to suggest/accept changes (similar to google docs?) Assign content to users for editing? Any other ideas on how this role could work?

It would be great if you could see a colour variables hex code when assigning a variable to an elements fill / stroke.

I’m playing around in figma sites and I’ve got some specific text styles and crops on a component, but when I view it in the ‘preview mode’ all the styles get resset to default (ie font not showing up, clip content not working, etc). Anyone else having the same issue?

I’m really big on shortcuts and makes my workflow much quicker. Please add a shortcut for copying an SVG to clipboard. No plugins or anyhting, just a shortcut. 🙏🏼🙏🏼🙏🏼🙏🏼🙏🏼 I’m on Windows, but even something like “ ctrl + alt + shift + G (tilde)” would suffice.

Hello,Possibly a feature request or lack of understanding on my behalf.I would love/like to be able to share the review modal to add the link to a jira ticket.This would allow the devs I work with to see what has changed etc…I really like how this modal clearly shows updates. But when this modal is not open, it can be a mine filled for a dev or stakeholder to understand what has and has not changed.Any advice or suggestions welcomed on this topic. 

Was told by a Figma rep that there are only 200+ requests for Figma to export as webP - and they didn’t sound positive that it would be integrated. So, I want to rally the community to push for this feature. There are already paid plugins out there that do this, so there must be a need. Show your support and let’s push the incredible team at Figma to incorporate it!