Share Your Thoughts

While prototyping in Figma, all connectors (nodes/links) are the same color, making it difficult to visually distinguish which frames are connected to each other. To improve clarity, consider adding an option for color-coded connectors or user-defined colors. This would allow users to assign different colors based on interaction types, flows, or personal preferences, making complex prototypes easier to understand and manage.

I happily created a variables collection for my existing dark mode and light mode color style palettes that I had in my Design System. The thing is, my app is primarily designed in dark mode, but I created the light mode variables first and now I’m stuck with having light mode as the default which is very frustrating. My only option seem to be do just delete and redo the ‘light mode mode’ which I’m not that keen on doing. I wish it was possible to just change the order of my color variable mode columns horizontally using drag and drop, just like how you change order of variant properties vertically.

This screenshot shows a split-screen view. I often work with different Figma files in split-screen mode, and it gets frustrating when I open the Variables panel to edit something, only to find that the “Close” or “Cancel” button in the top-right corner is not visible. The panel doesn’t resize to fit within the split-screen or other adjusted window ratios, making it cumbersome to close or navigate without manually resizing the window each time working with variables panel.

According to the below articles, it appears that it’s not possible to build a plugin that auto-runs and runs headlessly (no visible UI) without showing a running progress bar spinner, is that correct?Article Reference https://help.figma.com/hc/en-us/articles/360042532714-Use-plugins-in-files Running message when trying to run operations after running figma.ui.hide()If this isn’t possible today, I think it would be a really useful feature that would unlock a lot of new workflows interacting with other apps and hardware that doesn’t necessitate having a UI dialog up and running.

Hi Figma Team, I’d love to request support for Native MacOS Notifications in the Figma desktop app. Currently, notifications only appear within the app itself, while the mobile app does a great job of utilizing native OS notifications. This creates a bit of a disconnect between platforms and can make it unclear where users should expect important updates. Supporting MacOS’s native notification system would bring the desktop experience inline with the Figma mobile app and allow users to receive alerts even when Figma isn’t the active window. More importantly, MacOS provides robust notification preferences, giving users full control over how those alerts are displayed—whether silently, persistently, or not at all—based on their individual workflows and needs. Native support would significantly improve visibility and responsiveness to things like design comments, file updates, or collaboration pings. It’s a small change with a big impact in terms of usability and consistency. Thanks for c

Like with Google Slides, the canned animations that one can apply in Figma are not particularly useful in making more complex or impressive animations. Powerpoint is the gold standard there, allowing for path animations and timing based on a real (ish) timeline.Since it seems to allow some animation in the non-slides interface already via Lottie, (and would be nice if one could use embedded animation-commands inside the SVGs like with JS or SMIL) It seems as if this might be able to be ported to slides. Then, I could make complex lottie animations via BodyMovin in AE, animations in Rive, or directly in Figma and be able to ditch GSlides and Powerpoint both.

Hi Figma,As the title suggests, the main use case for UI 3 as a product designer like myself is utilizing AI features, background removal, and layer renaming. However, beyond these, the UI itself presents cognitive challenges.Here’s a small comparison between UI 2 and UI 3: UI 3 has more complex icons. (Why use a border in the typography icon, especially in such a small space?) Wasted space and visual distraction. (I don’t understand—why does everything need to be wrapped in a background? This adds unnecessary layers of complexity and distraction.)  

I need to limit the number of items when using Wrap on Auto Layout. Like the number of columns or rows on grids. I want to use wrap auto layout and auto-fill on inner items at the same time and I want to set a limit for the number of columns or rows. Look at these images, I designed that thing I meant. Additional: I don’t want to use max/min width, because these happen:

If some layers in my component are currently assigned to a boolean property, Figma now blocks my ability to re-assign these layers to a different boolean property without first locating every layer with an existing property and removing the prop assignment. This is incredibly frustrating, because there is no easy way to select these layers. I instead have to dig through (potentially hundreds of) layers to figure out which ones have properties so I can remove them, then use multi-edit to assign them all to the correct new property. This could be a quick thing for Figma to fix, by means of a couple solutions:Allow re-assignment of layer properties without having to first remove existing assignments. Make it possible to select all layers assigned to a property. This is already possible with variants — I can click the button next to the listed variant to “select _ variants.”Here’s an example of my current experience:After merging variants from 2 components, I accidentally now have 2 proper

While it seems to have improved since the initial launch, using prototypes in Figma Slides is still a poor experience. Below are the three areas that bother me the most: Quality loss. The quality of protoypes when viewed through Slides is noticeably less sharp. It’s better to just have the actual prototype open in a separate tab. Prototypes have to load every time you change slides. This is very annoying when designing a deck because you constantly have to load it to make sure it’s the correct prototype, but the real issue is having to wait for the prototype to load while presenting the deck. Every time you change slides, the prototype has to load up again so if you’re sharing concepts and need to go back and forth between slides, it’s a huge pain. Again, it’s better to just have the actual prototypes pre-loaded in the background. Moving prototypes around a slide is really annoying because it triggers the interactions on the prototype itself. I have no idea why this is the defau

‘Absolute position’ is now called ‘ignore auto layout’, ‘space between’ is called ‘auto’ and there are probably a few other settings that Figma has applied its own naming to.Why?It’s bad enough that layout and styling in Figma does not behave like CSS and HTML in many cases, which means that we have to completely rethink our approach to design. Now we have learn new terminology as well.Even for somebody who doesn’t know CSS, I would assume that it hardly makes any difference which term they learn. It would even be an advantage if they learn the correct CSS terminology, so if they do learn CSS one day (which, in my opinion, would be highly beneficial), they don’t have to learn new terminology for everything.If I could make a wish, it would be to please align terminology and behaviour between Figma and real-world CSS wherever possible.

It would be nice if we had an option to show a little dot or something that shows you where the user clicks on a prototype. We’re a remote-first company, and it would be really helpful for me to be able to have some visual indicator when I click on something when I’m sharing my screen on a call. This would also be very useful for remote user testing if we can see where testers are trying to click.

Hello Figma team,Thanks for this beautiful solution.Just want to say that is in the title.  

Let’s face it, variables for dev seats need some more thinking.We had all our files using variables from another file, where we keep our localization variables (Japanese and English) and the color themes (dark and light), so several design files can use them.With the new dev seats our developers CAN’T SEE any localization or change the color theme of the design. Sure, they have the color variables in the side panel as part of CSS, but no clue why the strings not. BUT they can’t change it to see it.I’m not saying to see it as code. Our developers want to see the design to check themselves that the code is ok. They want to see the design in Japanese or in dark theme if they want, selecting the variable mode by themselves.That’s why I’m suggesting you to think a solution to this. Since right now the only solutions are duplicate every single screen, like we did before you introduce variables, or give a full seat to every developer. 

Scenario: In a remote lecture, I am sharing the presentation with students (view rights). On the first slide I ask a question and create an interactive poll. The answer/solution is displayed on the next slide. If the user can click forward on their own using the arrow keys, they can cheat.

Hi there, the button is too big in my opinion for changing tabs. I’d love for it to be the same size as Google Chrome’s button. I’ve accidentally closed so many windows because of this.

The keyboard shortcut to Zoom to 100% is quite uncomfortable. Hitting Command + 0 is just so unnatural, it requires both hands, or moving one hand to around mid-keyboard to use the other Command key and the 0.I know this is pretty standard, I don’t really blame whomever made the call.Now: 1) you cannot edit the shortcut with macOS’s Keyboard Shortcuts feature (I can’t overwrite it to ⌘1), which is quite lame, 2) nor can I set it up within Figma’s Preferences. This could be a very cool addition. Let users choose keyboard shortcuts.To be fair, having ⌘1 go to the Home tab in Figma makes no sense. Why would I want that easy, comfortable shortcut to do that? I barely go to the Home tab.Anyways, I hope this can be moved up the chain.Thanks.

If I have an item or component and send it to a different page, it often takes me several minutes to figure out where it went. 

A current pain point I’m facing is having to manually select the text layers that I want to change (and matching layers doesn’t always work for me, which also causes some frustration). The “Selection Colors” feature is super helpful for when I want to swap color styles within a frame. I wish this was also the case for typography, where there is a “Selection Typography” feature that allows me to easily swap text styles within a selected frame, or identify layers that are not linked to a text style.

I want a way to edit the speaker notes for all of the slides at once. Maybe like a word doc style on the side separated by slide number. That way I can check general flow of my presentation at a glance. 

Hi Figma team,I’d love to request a feature that allows designers to simulate browser zoom behavior (e.g., 90%, 100%, 110%, 125%, 150%) either in the file editor or the frame preview window when a specific frame is selected. 🔍 What I’m Looking ForI’d like to be able to press Ctrl + Plus (or minus) while editing a frame and see the contents scale like they would in an actual browser zoom, without having to: Use the K Scale tool (which permanently resizes elements), Or manually simulate responsiveness with constraints and resizing the frame width. This would be incredibly helpful for quickly checking how my UI elements appear at different zoom levels — particularly for accessibility and UX tuning — without jumping in and out of preview mode or doing frame gymnastics. 📌 Suggested Implementations A toggle setting (e.g., “Enable Zoom Scaling on Selected Frame”) in the editor. A zoom dropdown in the Preview (Present) window that behaves like browser scaling rather than just canvas zoom

Figma just added an icon to collapse all layers. A thing that has existed in keyboard commands forever. but once again...they did not provide the reverse. Ability to expand all layers. why does Figma only do anything halfway? maybe instead of focusing on things like silly “FigPals” they could work on the million half-finished shortcomings in the product? instead of a cute temporary bunny, I would like to be able to control which properties of a nested component are adjustable. but Figma is making play toys. this is what my enterprise team license is getting me. 

Hi team, it is very easy to accidentally destroy a design in Figma web on a touchscreen like an iPad because tapping to select an object and moving the object can happen in a single gesture. If I’m panning around the canvas and don’t touch two fingers to pan at exactly the same time I can accidentally drag something.This has been taken care of in the Figjam app, as panning is performed with a single finger and an object needs to be explicitly selected before any gesture can be used to manipulate it. It would be wonderful to have this functionality ported over to Figma on web. Thank you.

Is there a way to set a color in preferences or something to choose what the background color is? My old files used to have a background of #E5E5E5, but now it is set to #F5F5F5. This is a problem for me as F5F5F5 is close to one of our brand colors, so I need to go and manually change it every time. Is there a way to set a preference for the background colour in design files?

Slides doesn’t have Auto-Layout which is one of the major reasons to use Figma for Presentation. Please make it available!