Share Your Thoughts

It would be great to be able to seperate the visibility objects beyond just the layer. To be able to associate a boolean variable to the visibility of; Layer Fill Stroke Effects Would make it more effective when putting together a design system. This means that you could effectively determine that all buttons have outlines, or drop shadows or both right across the whole design. See examples below. Thoughts?

Previously, Figma Make let you launch a console for debugging bugs, but this feature was removed after the latest updates. Why? Now you have to publish the app and launch the console in the browser via developer mode, which is extremely inconvenient. Bring back the console!

Please… PLEASE! For those of us with lots of simultaneous projects and heavy deliverable schedules, tab browsing in Figma needs some LOVE! Now, I’m not one of those psychos that keeps 300 tabs open in their Chrome browser, but I do, at any given time, need access to multiple projects simultaneously. If I could easily group those tabs together in Figma and give them a nice, friendly name, maybe an emoji, or… dare I say… a color, I’d be a really, really happy camper.  

Would love to have more options on the typewriter effect, such as easing.  Also would love to have more/better control over parallax scrolling (direction, speed, distance all as separate parameters).

It would be great to have a feature that allows you to hide or lock a page in a file. There have been moments when stakeholders will keep peeking at the work before it is ready for review. Having a hide & lock feature would be nice to have so that if you do share the figma, they can only access the pages visible to them. 

Здравствуйте подскажите пожалуйста как можно добавить шрифты в фигму если работаю на ipad

I am using variants to enable dark and light modes for example and it works automatically for almost everything except for overlays. I have am user flow with an overlay menu that opens when I click on a button or icon. I want to display how to shwitch between light/dark modes. So when Im in light mode and open the overlay menu (light) and then switch to dark mode and then open this menu again its still in light mode and I dont see a way to change this using the “Change to” nor “Set Variable” options in the “On click” prototyping option. How can I simulate this consistently without having to use two different menus (one for each mode)?

I use Figma Sites to build websites for companies. Overall, I like it a lot. Pages are easy to create, and links and effects work well with very little effort. However, there are some essential things that I currently miss.1. Usability for non-designersI build websites for clients or colleagues who need to manage the finished website but are not familiar with design tools like Figma.There is currently a CMS feature, which allows text and images to be edited in a table. However, this does not work for all pages. I cannot find a way to make the homepage editable for other users.Ideally, every element that should be editable could be connected to the CMS in such a way that other users can manage the site exclusively through tables, without interacting with the design canvas at all.2. Quality of Life improvementsWhen I create multiple CMS collections, things quickly become confusing. There is no way to reorder collections, and I also miss the ability to create a folder structure.It would b

With the emergence of skills for agents becoming very popular, are there plans to create agent skills for the various dev API you offer? For example, skill for plugin & widget development. Skill for dealing with the REST API, etc.

I ran into a common Figma Prototype issue:when the first animation uses After Delay (e.g. 10s auto-play for a hero carousel), it doesn’t start in Present mode unless the page is refreshed.Small preview works. Full Present mode doesn’t.The delay never starts, and progress indicators stay frozen.After some testing, I realized this is because the starting frame doesn’t reliably trigger initialization, so After Delay has no real “entry point”.My workaroundInstead of relying on time-based logic on the starting frame, I switched to event-driven triggering: On Mouse Enter (or any explicit interaction) Immediately navigate to a transition frame From that transition frame, start After Delay (10000ms) Then move to the next carousel slide This transition frame acts as a forced “mount”, similar to a lifecycle hook.Why this works Navigate to always re-initializes the frame After Delay finally gets a reliable start point No manual refresh needed before demos It’s not meant to simulate prod

It would be really helpful to have the ability to group opened Figma tabs in the top bar, allowing users to create collapsible and expandable folders, similar to the tab groups in Google Chrome.

It would be so great to have some additional filter options when browsing search results. In a large organization, there can be dozens of files spanning years, all with similar names and content. It’d be great if one could still sort by recommended results, but filter by the modified/created date

The fill is not visible on a vector shape unless its closed. Many applications and the web supports fill on open vector shapes, but not Figma. Please allow something like this. This red area should be fillable by the paint bucket.  

Figma Prototype : In large IT companies and design teams, it’s often a struggle to manage design review tasks because we constantly need to jump between Figma and external management tools (Jira, Asana, Notion, etc.) just to track: what page or element was assigned to us for review who is responsible for feedback what review status each screen is in ✅ Proposed Feature: Review Tab Inside FigmaIntroduce a new “Review” tab, similar to the existing Dev Mode icon, that enables teams to manage review assignments directly in Figma.🔹 Key Features1. Assign Reviewers to Frames / Pages / ElementsJust like adding a Dev icon, designers could add a small Review badge on a page or specific frame. Assign a team member Add due date or notes Track who is responsible 2. Review Status TrackingEach assigned item could have a status such as: To Review In Progress Approved Needs Changes This would give instant visibility without leaving the design file.3. Review Inbox Panel (Like Notifications

When selecting an object inside a component, the bounding box uses the same purple color as components. This makes it difficult to quickly confirm whether you’ve selected the parent container or a nested object.It would be helpful if objects within a frame or component used a different selection color than the container itself. This visual distinction would reduce selection ambiguity and speed up precise edits.A comparable example is InDesign: images live inside frames, where the frame is highlighted in blue, and double-clicking into the image shows an orange bounding box. This clear color separation provides immediate confirmation of what level you’re editing.Introducing a similar distinction in Figma would improve clarity and reduce mis-selection, especially in complex, component-heavy files.

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.