Share Your Thoughts

Hi Figma, is there plans to move the right sidebar content so the component properties and the Appearance variable modes are closer together?  Having the Position and Auto-layout sections in between really disconnect the component properties and the variable modes. For smaller screen size or when there’s multiple component properties, the variable modes can easily be fully hidden down, which makes it harder for designers to know there’s additional settings for a component.   

The variables feature is a great addition to Figma. In our workflow, we use them extensively with multiple modes (like light and dark mode) and collections, which involves a lot of variable aliasing (linking variables to other variables).This has created a large and complex network of references. It is becoming difficult and time-consuming to find the original source value (like the final hex code) for a specific variable.It would be a significant workflow improvement if we could trace a variable's origin, much like you can trace CSS variables in devtools.We propose the ability to click (or right-click) on an applied variable to see which variable it is referencing, and then be able to follow that "chain" of aliases all the way back to its original source value. This "Go to Definition" or tracing feature would make debugging complex variable setups much more efficient.If this functionality already exists, please let me know. Otherwise, I hope this is valuable feedback.

Been playing around with the “expose nested properties” feature currently in beta. One of the great uses of variant properties is the ability to batch edit property values on multiple selected components. That use doesn’t carry over to exposed nested properties (yet I hope). Demo file to help When selecting one component instance exposing nested properties, said properties display fine. Add another instance of the same component to your selection (using Shift+Click), and the nested properties outright disappear from the right panel. I haven’t seen this issue raised elsewhere! Do you experience it too?

Allow us to change the background color of text (not just the text fill color) to give a highlighter effect that stays with the words that the effect is applied to even when the size/shape of the text box is changed. For example: The above shows two examples of the same ipsum (left and right) where specific words are highlighted. When the size of the text box (the left example) is changed to accommodate a responsive layout (the right example), the highlighting stays with the selected words. The way to add highlighting for the above examples could be included in the type settings pop-over: Note: the idea here is that the user can apply this to specific sets of selected characters within a text box or to the entire text box, just like how all of the other type settings already behave.

Situation It often happens that there are a lot of instances that have overrides in a design. Sometimes you are not quite aware what exact overrides have been made to a component, though. For example someone could have manually changed the height of a component and if the height override is actually the same as the main component, you would be blissfully unaware. Problem You will notice that an override has been made maybe, after you make adjustments to your main component and realising that the instances did not change. Annoyingly, if you want to reset a particular override behaviour, you will have to reset the entire component back to the state of the main component and then do the overrides you do want to keep again. Depending on the complexity of the component (Maybe it is even a nested component), this can be quite the hassle. Proposal As such it would be nice if we had some listing of the overrides that have been made (maybe also interesting for the devs) as well as the option to

Hi everyone, 👋I’m new to Figma and learning everything completely from scratch. I really appreciate having access to the free version, as it’s been helpful for getting started. That said, I’m finding the current limitations a bit challenging when trying to fully understand the workflow and explore what Figma can really do. I feel that having access to some Pro features would really help me learn faster and more effectively. I wanted to ask if there are any options for a free trial or a discounted Pro upgrade for beginners even if just for a limited time. I’d love the chance to experience the Pro features before fully committing. Thanks so much, and I really appreciate this community and the product!— Bright

It would be beneficial to have version control in Figma Make, or at least the ability to publish changes to a "QA" instance. Currently, the only way to test app changes across different browsers is to publish them and hope for the best!

Dear Figma product team, does the UI of UI3 need to be updated again? Compared to the last UI update, many new features have been added. Do you need to update the UI now, from visual to UI to UX? Let me urge you to update it

Not very easy for users to test on the Make prototypes, as they need to log in. Takes quite a while to log in or even register.Maybe some features like in Figjam, can open the session for certain amount of time, allowing visitors to get on the link without registration or login.  When previewing the Make file in Figjam, can we also allow users to interact with it, without login?

I have to jump between my foundation and theme collections pretty frequently. I’d love a “Go to main component” but for aliases.   

I sit in a ton of Figma demos, and I use the “follow” feature pretty regularly to track what the presenter is showing. However, often times, their zoom level is not ideal. Currently, you are locked into their zoom level - and to zoom in (or out) you have to break out of following them.Can you please allow followers to adjust their zoom in and out without breaking out of “follow mode”? This would allow us to zoom in on the details, or out on the macro picture, easily without losing track of the presenter in the demo.  Thanks!

I’ve spent so much time trying to figure out how to export a PNG with a transparent background. I finally found a solution in the support forum where you have to add an image fill. This just doesn’t seem obvious to me at all.. Could we get a checkbox to add transparency in the export option for PNGs? That would be much more straightforward! 

Hello there, I am currently having issues viewing the guides on my design when the brand colour is pretty much the same as the guides and familiar to some colour. Please help me how to change the guideline colour like black, blue green and any other dark colour

I know that you can set aliases for number variables, but it would be great if we could use number variables with other number variables to do a computation. For example, this would be great for playing around with type scales without needing a plugin. Below is an image of the use case (ignore the line height variable).  The current workaround is just doing the math manually, but the computation isn’t preserved (e.g. `s` doesn’t show `14 * 1.25`). Granted, I did end up fudging these numbers so that they would be rounded up to the nearest even number, but I still feel this is a fair request.Bonus is if you add a rounding function to these math opportunities, but I understand that the software will just round to the nearest whole number anyways so it’s more for the developers. 

It would be very beneficial to be able to use the command/scroll wheel in a Figma file, either in the supported Figma app or in any browser on iPad. Some people are working in environments where the iPad is used for connecting to corporate, “locked” systems (often via Microsoft), and if you are to present a prototype in an online meeting, it is nearly impossible or at least extremely cumbersome to use pinch-to-zoom on mid-sized iPads. Under such circumstances, the iPad acts almost as a separate PC, so a feature like this should be the norm, not the exception.

I’ve recently worked on a design in a FY 24/25 Q4 document that still needs implementing, and that quarter/year is now over (for us, I’m aware that other orgs use different dates) so I want to:Create a new FY25/26 Q1 design document Move (not copy) the page from the FY 24/25 Q4 design document into the new Q1 document Achieve the above in as few inputs as possibleI would ideally expect to be able to right-click the page in the Pages panel, select “Move page to another document” and either choose an existing document or create a new one (naming & choosing its location in the process)However this route doesn’t exist, the choices are only “Copy link to page”, “Rename page”, “Duplicate page” and “Delete page”, none of which help me - I can’t even Copy the page and Paste it into a new document!Suggest this is a pretty obvious missing feature, would be relatively easy to implement, and alongside the “Move page to another document” feature there should be a “Copy page to another document”

Hi dear Figma teamI’m writing you as an advanced designer. Why not adding a arrow connector to make it easier to put both advanced designs and flows in a file? something like what already happens in FigJam... 

i believe put design and figjam diagram in single file better than different file.for example,  i can create and edit task flow next to UI, instead of copy and paste back and forth.same goes for figma slide.

Can’t say how disappointed I am with the Make function of Figma. Very overcomplicated way to view, modify and export the files. All kinds of exotic explanations of how to possibly view the files of an application, until Figma;s AI itself admits, it’s actually not possible, nor is it possible to export into zip files. Modifying a Make is possible but insanely clunky. Today, I regret to say it’s little more than a prototyping gimmick that may be useful only for early stage ideation.

When creating a component, I might use one setting of the extended collection, however, it always fixes the "Default" mode, which means, if I want to change the mode in an instance, I have to manually pick that mode regardless of it being applied on a parent container.Ex: A Collection with expanded brands, and dark and light modes. If I decide to use Brand X (not the default brand), it immediately applies the light mode, and every time I want to use the instance of that component, I need to manually set it to Dark mode even though the dark mode is used in that specific frame or section.I don't know if this is the intended behaviour, and if it is, I would suggest to consider changing it and always inheriting the mode from the parent unless otherwise stated.

Design files BADLY need a way to organize old and regional design pages. There is so much happening in some files because of globalization that we REALLY need a way to create folders so that people don't get confused and look at old or in design process work.  I would jump off Figma in a heartbeat if another program did the same thing and allowed for such a structure in side of the files.

Why is this impossible while logged in? or without switching to incognito mode?this seems to be an insane user experience when I just want to see what’s new real quick or perhaps check pricing or any other normal or sane reason to visit your front page!Just add a link to the figma menu? or even in the help button? 

For example searching keyword ‘Tooltip’ here should find 2 results But only one is returned This presents a problems when maintaining designs and design systems. Please make invisible layers findable as well. I don’t care if it should be a setting to include or exclude invisible layers. As long as I can search and find them. Currently I cannot at all. 😵‍💫

I need variable for corner smoothing !

ProblemCurrently, there’s no way to bind the Flex Direction property (horizontal / vertical) to a variable or boolean condition. This makes it impossible to dynamically switch layouts inside a component using variables or modes. Designers are forced to create duplicate components or manually toggle the direction. Proposed SolutionAllow flexDirection to be controlled via a variable or boolean property, similar to how alignment, spacing, and padding can already be managed.Example syntax:flexDirection = isVertical ? "VERTICAL" : "HORIZONTAL" Expected Benefits  Enables adaptive, single-source components without duplicates. Improves token-driven and responsive design workflows. Makes component logic consistent with existing variable bindings.   PriorityMedium–High — essential for scalable, adaptive design systems using Figma variables and Auto Layout.