Share Your Thoughts

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: but it would be more convenient to be able to do it with just one. Just give me a Boolean toggle when the variable is used to say if the variable should be inverted or not.

So many times I may detach a component or copy and paste a frame and have to go one by one deleting each annotation that carried over. Would be great if I can just select the frame and have some sort of shortcut to delete all annotations. Would save me a lot of time, I do this at least a few times a day and some of my frames have over 20 annotations. (working product designer) 

Please add independent loop controls for animated component instances in Figma Motion, so an instance placed inside a parent frame can repeat on its own timeline without forcing the main component duration to match the full frame durationExample: a 2-second animated component placed in a 10-second frame should be able to loop continuously for the full 10 seconds while the parent frame animation continues separately.

I would like to make lines of text that, when hovered, display actions in an action bar. However, when I move the mouse over the action bar, I leave my frame, since the action bar is in absolute position. We’d need an option to make absolute elements hoverable and clickable even if they are outside the main frame.

Simple but yet powerful addition would be support of the categories for Figma CMS content. Along with different type of filed you can add “Tags”, and allow users to create them when they add new content items.On the front side, simple filter components with showing “All” as selected by default tag and list of tags after. Together with my proposed pagination idea Figma Sites would be able to support much bigger pool of builders and designers.

Please provide an option to remove this "grid" in autolayout; it's become impossible to work with. I didn't write this before because I thought I'd get used to it, but NO, it's terribly unnecessary and completely inconvenient. Please provide an option to remove autolayout by default. This feature is only for some kind of perverts. Whoever suggested it obviously has never used their own program. Thanks for your attention.

I think it would be great to see keyboard shortcuts for the ‘Auto height, Auto Width’ text box sizing features. I use these all the time and it would be really beneficial to have a quicker way to change these 🙏

 i can do this all day。。。。。。。。。。。

I’m developing an icon set, and attempting to export a set of uniformly sized SVG assets. Each icon has a 20 x 20 frame, with the vector graphics nested inside. In some cases, the graphics have strokes that exceed the edges of the frame, even though the vector paths themselves are inside the frame. In those cases, when exporting to SVG, the viewbox is greater than 20 x 20. How can I restrict the viewbox to a very specific size? Seems like this post is related, but I’m having a hard time understanding the guidance: SVG exports at a different size to W & H values in editor - #3 by Corin Thanks!

Although I find the new autolayout UI extremely convoluted and overdesigned, the ‘hug/fill parent’ feature is great. However, It would be immensely helpful to have more control over how the elements fill the parent. Currently, the only option is for the elements to fill the remaining space, but oftentimes, I need certain elements to take up a certain proportion. Example: I need element-1 to take up 2fr (~66%) and the rest to take up 1fr (~33%). It would be a game-changer if we could use ‘fr’ units. Framer does this beautifully and it’s vital for efficient, adaptive layout workflows:

Add native two-way sync between Figma variables and a design tokens file so changes made in Figma or in code stay aligned automatically. Figma already supports variables through the REST API and Plugin API, which teams use today for custom sync workflows, so built-in syncing would reduce manual reconciliation and plugin dependence.

Hey Figma So I have been building our component library and stumbled through this issue where I built parts of the component that are not needed to be published because they are only make sense to use them inside the main component. So having these nested components being published make it confusing and clutters the library. Can we please allow Instance swap property and Slots to have these components show up I literally picked them as Preferred component but they won’t show up since they are marked as Hidden.  

I have a single page site that has a nav bar that scrolls to different sections on that page. I want to add sub pages for some of the content on that page, and I’m trying to add the same nav bar and anchor a nav menu item to a section on the main page but it doesn’t seem like its possible unless its on the same page. 

I'd like to suggest adding additional readiness statuses beyond "Ready for Dev". For example:Animation Ready UI/UX Ready Legal ReadyThis would allow teams and agents to understand which aspects of a design are complete and which still require attention, rather than relying on a single development readiness indicator.

Add native JSON / Lottie format export support for Figma animations and prototype interactions directly from the Export panel.Why is this needed?Currently, to export UI animations or micro-interactions as light-weight .json (Lottie) files for web and mobile apps, designers have to rely entirely on third-party plugins (like LottieFiles or Aninix).

Add a unified, searchable variables table directly in Dev Mode so developers can review all variables, modes, and collections in one place instead of only seeing variables tied to the selected layer. Dev Mode already supports variable details, suggested variables, and access to local variable collections, so expanding this into a full-file view would make multi-theme and multi-brand systems much easier to inspect.

I'm building a blog with Figma Sites CMS, and articles vary a lot in how many images they use, some have 1, others 5+, in different arrangements. Right now a CMS Page is one shared template for the whole collection, so every article renders with the same fixed layout. If an Image field is left empty, it just becomes a transparent fill, the layout doesn't collapse, so I end up with blank gaps instead of a clean design.Figma Sites already ships a big library of pre-built blocks with different image/text combinations (Insert > Blocks), which is exactly what a blog like mine needs. There's just no way for the CMS to pick a different block per item based on how much content that item actually has.Two things that would fix this for my use case:1. Conditional visibility tied to whether a CMS field is empty, so an unused image slot collapses cleanly instead of leaving dead space (similar to "Is Set" / "Is Not Set" conditions in Webflow or Framer).2. The ability to swap which component/block

I want to share feedback on the Figma Make credit system, because in its current form it is not workable for real projects.Yesterday I spent one working day building a page in Make (Full seat, 3,000 credits/month). By the end of the day I had consumed almost the entire monthly allocation — without reaching the intended result. The core problem: the agent frequently makes mistakes, ignores constraints, and breaks previously working parts of the build. Each mistake requires another prompt to fix, and each fix consumes more credits. The more rework the agent causes, the faster credits drain. Effectively, users pay for the model's errors.Suggestions:1. Improve agent reliability, or stop charging full credits for correction cycles caused by the agent's own errors.2. Add cost estimates before execution, usage alerts, and spending caps.3. Reconsider whether 3,000 credits is a realistic monthly limit for professional iterative work — right now it can disappear in a day.I like the product conce

I find managing template colors really difficult in Slides. I can’t easily organize, re-order, or rename them. I’ve found some ways to hack it but it feels really convoluted trying to provide color options in the templates I’m making. I think Slides is doing a really great job on most fronts and I love the product, but I find myself just using colors from other libraries because managing them within Slides is so confusing.

Figma can you please add the Font Miranda Sans. Its on Google Fonts. Thank you. 

Hi! Many keyboard shortcuts do not work when the Russian keyboard layout is active. To use them, I have to switch to the English layout first.This interrupts the workflow, especially when working with Russian text and frequently switching between typing and design tools.Please make keyboard shortcuts work consistently regardless of the active keyboard layout.

Annotation orientation control (vertical placement)When laying out flows horizontally, annotations from one screen's frame overlap the adjacent screen because they render to the left/right. Request: allow annotations to render above/below the parent frame instead, with the same anchor logic rotated 90°. Ideally a per-frame setting with a global default.

Currently you can set things like, 5.99 or 4.32 but you can’t show 5.00 by default. This looks weird when you start adding amounts like #amount + 0.5 which will then look like $5, $5.50, $6, $6.50. It would be nice if instead it showed as $5.00, $5.50, $6.00, $6.50

The current Tables feature in Figma feels quite limited. It would be fantastic if some basic functionalities could be introduced soon, such as: • The ability to easily resize cells without needing to adjust font size • The option to merge cells • Top, middle, and bottom text alignment options These enhancements would bring Figma’s table functionality more in line with what we already have in tools like Keynote and Google Slides.

In other design tools you can simply press a key, and any selection outlines, grab handles, etc. get hidden while the key is down, so you can preview and evaluate how things look, without having to de-select everything and lose your selection. Apparently there is no way to do this in Figma =( This is important while experimenting with different colors, fonts, etc., and in Figma it could be used to see how different sizes, variants, and states, look in your design, without those selection handles and outlines getting in the way of you previewing things.