Share Your Thoughts

I’m trying to recreate the structure of our Text Field web component with slots. I would prefer the Figma slots to behave similar to the <slot> element in that they wouldn’t reserve space until there is content in them.Currently I can work around this by adding a boolean property that controls visibility of each slot but this adds clutter to the property controls.In the properties panel slot contents are described as “Default” or “Modified”. Having a third state “Empty” that also hides the slot from Auto Layout would solve both for me. 

Slides and Figma prototype are products of same tool, there is no way to add prototype into slides which can let me me scroll through my desktop prototype 🤔This causes a lot of back and forth between different tabs while doing a presentation. 

Please answer the questions as soon as possible. Any approximate date to next release.

Here, I have an orange colour at 60% opacityPreviously I could paste a hex value in, and the colour would be replaced and remain at 60%Now it goes to 100% no matter what I paste here. As soon as I paste in a new hex value, I have to set it back to 60%.I am replacing a colour - not the opacity. Why change opacity as well? This is awful, and as of today, it has really slowed down my workflow. Thanks.

Engineers on my team just noticed that they can’t see and export local variables unless they have edit permissions. This is a huge limitation since not everyone on my team can have edit permissions due to licensing/cost. My ideas is to keep local variables visible to View Only collaborators. They should not be able to edit the variables.

Why are the "Save to version history" and "Show version history" options disabled in Figma Make, even on a paid account?

Hello,I am looking to create a good hero section for my site, where it should take the height of browser in the first fold. The subsequent sections can be of fixed heights based on content. I need something like 100vh to have for my hero section.

This has been mentioned here: Hide layer using variables - #5 by Andreas_Braendhaugen1 Invert boolean variable for layer display - #14 by Desislava_Slavkova Inverted Boolean Property - #2 by drewcovi_usb but those topics are all closed. I am looking for the availability to HIDE a layer when a Boolean variable is TRUE and SHOW it when it is FALSE. So, the inverse of the default/current behavior. I want to do this without using components. Use case: When a variable is true, show one frame. When that same variable is false, show a different frame. I can get basically this by using two different variables:

It would be really cool if we could access Code Connect for variables at a lower plan level. It appears you cannot use Code Connect for variables in any other plan than an Enterprise full seat due to not having access to “REST API for variables” feature.This would really help us in using the Figma MCP for better consistency but as a self employed professional $90 a month is a bit too rich for me personally.

Introducing annotations is great, they’re super helpful ✨ That said, the lack of flexibility when it comes to their positioning is quickly counter intuitive. They end up overlapping with other elements, which can make designs harder to read and manage—especially when multiple annotations are stacked in the same area. It would be incredibly helpful to be able to manually drag the annotations component to reposition it (e.g. top, bottom, left, or right of the target element), while still maintaining their link to the relevant object.   

Current State: When you add a stroke to a mask, the stroke becomes an extension of the mask.Needed Improvement: When you add a stroke to a mask, the stroke is on top of the mask.This should be so simple, can’t understand why this wouldn’t be the default, but at the very least to have this as an option would be super helpful. I understand you can duplicate the shape on top and add the border, but then when resizing the mask you have to resize the shape on top as well, trying to eliminate a step. 

I’ve got our company’s internal design system packages published into our private NPM registry. But in doing so, I found (after I published) I needed to modify the packages for consumption by figma make. Figma’s NPM private registry would not allow me to unpublish or overwrite the package versions once I published them.This is causing a problem in Figma Make because users are able to select old, incorrect versions of the packages when installing. I want to prevent this by being able to unpublish or delete packages from the registry, but I’m unable to do it.We are experimenting with the best way to handle this for figma make that is easiest for our figma users--and would like to be able to hit a hard reset at some point as we may completely change strategies. Right now, we have 50 or so unbundled packages in figma make. In the future, we may want to bundle those into a single versioned package for easier consumption.To summarize, here is a list of figma make NPM

HiI’m looking for a way to simply be able to highlight and make bold  at the same time if possible.It can also be just changing text color, again preferably with the option to add bold effect.I would like to then be able to customize shortcuts for this..Example:Blue highlight / Command - Shift - 1Yellow / Command - Shift - 2etc.I really can't believe that this is not an easily available option in Figma, seeing as highlight pens are very very popular for anyone studying anything, and categorizing things through color can be very helpful for those working with large amounts of text. So I hope anyone can let me know if there’s a way to do this, or that this me

Simplify “Assets” to only show all components of the local file instead of which page they are on. Too many clicks to navigate to find the component, and there isn’t a search function.

In the new UI there is no option to view all Assets of a library at once. You always have to click through the groups which is super annoying. There should be an option to have everything visible and not in a folder view!

When publishing a library, I would like an option to shows all nested elements at the top level. OR even better, when in a Figma file when working in the ‘Assets’ tab, I’d like an option in the grid view (in addition to the grid / list) which allows all elements to be displayed on the top level and not display them as nested items.I realize when publishing I can put all elements on the same page in a file and then I will have no nested items for the users in authoring when trying to pull in components. However, this makes the page too massive to work with. I have to break up the pages but when published, this make nested items which I don’t want. I want everything displayed on the top level as its SO MUCH faster for designers to easily pull in components/elements when they don’t constantly have to go back and forth between levels to find the components they need.

It’s 2026, why are links (especially figma file links) being pasted as plain text? Notion and tools similar to it show a stylized container/preview by default when a link is pasted, with the option of a hyperlink or plain text link. Not having it in Figma Design is one thing, but not having it in Figjam feels especially lacking.

Figma supports enabling/disabling some OpenType features from the UI.https://help.figma.com/hc/en-us/articles/4913951097367-Use-OpenType-features From the plugin API I can see which features are being enabled withhttps://www.figma.com/plugin-docs/api/properties/TextNode-opentypefeatures/but the property is read-only. How can I programmatically enable/disable some OpenType features?Also, is there a reason why it’s accessible on UI but not Plugin API?

Hi all,First of all, the new Slots feature is truly awesome, I can’t wait to see how in depth we’re going to rework the components of our design system with it. I’d like to suggest a small improvement regarding their visibility. When a slot has no fill or background, it’s basically invisible on the canvas unless you hover over it. This makes it harder to understand the structure of a component at a glance, especially for our designers who are going to consume the components we provide.It would be really helpful if slots could have a dashed outline, similar to the dotted boundary used for variant groups in component sets, so empty slots remain visible without adding a background.I tried looking through the settings to see if this was already an option. If it exists and I simply missed it, my bad. But if not, having something like a default or optional slot outline could make components much easier to read and work with.

EDIT: i can already do this by using the Gap function.It’s still almost impossible to design for fluid widths in FigmaBut with the new Grid Beta, it is now possible to set up for example a 12 col grid system , see my screenshot:https://prnt.sc/fetKFckcQpT4 Basically I set the colums to 1fr, and i set the gutter to my design in pixels. This is how most grids work on a webpage. Now if i rescale horizontally, it keeps the gutter, and scales the grid like in real-life.But on smaller screens the gutter usually need to be smaller, and it would be extremely tedious to manually replace 12 gutters for EACH and every frame i use this on a webpage (potentially hundreds)So if we could use variables to the colums in Grid Beta, that would be just one click solution and we almost got a working fluid system in Figma.

It would be a great idea to add the ability to move annotations (сhanging the place). Right now, they’re fixed in place and can overlap other elements. And you cannot change it.What I mean is the ability to reposition an annotation freely while keeping the link to the target object intact.Annotations are a really useful feature—thank you! Previously, I had to create similar functionality using my own objects. Please do not move this offer to another discussion. 🙏Can we move the Figma Annotations (in dev mode) from one Figma project to another?These are different questions.

Please implement AI into the variable editor. It would make re-factoring a design system infinitely easier if we had an AI that could go through and change everything to the way we need it. For example, we’ve decided we want to ‘master’ up the stroke width for field components, but now have to go through 50+ component variants telling them to alias the new master value

When assigning a variable to a component property, the search box displays both the variable name and its value, making it easy to know what you’re selecting: However, when you’re aliasing a variable from within the Variables page, the search popup does not show the target variable’s value, making it harder to confirm the correct selection: 

I am facing issues on Figma. For example, I have a circle with dimensions 400x400 in Figma and when exported in my Mac folder, it shows 401x401px. Which is not compatible with the device interface I’m working on… Of course, a possible solution could be to scale the original component in Figma to 399x399, but should we cheat like this? Is this sustainable? Any advice?

I just want to adjust the page settings for each page “frame” so to speak so I can make it wider. It’s not clear that this is possible.