Share Your Thoughts

Is it possible to map the HUG or FILL to a variable. It would be great to not only assign particular width values, but also set the width to either hug or fill the container.

This may be a hacky way to achieve what should probably be a standalone text decoration style (highlight)… but with the addition of underline styling, you can basically setup a highlightThe issue is that the underline appears over the text. It would be great to have to option to set the position or z-index of the underline to appear behind the text? 

We currently manage over 800 templates across roughly 20 collections in Figma Buzz. When using the Grid view, the scrollable area limits out at approximately the top 50% of the loaded templates. To access templates at the bottom of the grid, we are forced to manually collapse the collections above them. This is an unnecessarily cumbersome workaround that slows down our workflow. We should be able to infinitely scroll or navigate smoothly from the very top collection down to the bottom collection in Grid view without hitting an artificial scroll limit or needing to collapse preceding folders.

Hot take,Figma Make, in it’s current beta form, is underwhelming when it comes to being able take a design and turn it into a usable coded prototype quickly.This feature will have a huge impact on designer-developer workflows only when the speed to getting to a Make prototype is faster than getting to a noodle prototype. Until that happens, designers will continue to stick with what is fastest/most effective for them.Being able to provide Make with the entire context of a prototype + developer notes + design library inside a given file/page seems to be the best route to doing this.I hope the refactor needed to get to being able to provide access to all of this data is well underway, but if not, I’m putting my trust in the rest of the community to get some movement behind this idea here in the portal.

There are many legacy companies starting to value design a lot more, and they are hiring designers into their ranks to make their software products a lot better. At these places, there may be strict network or security requirements that our critical software must be self-hosted or deployed on-premise. For us designers, we join these companies in hopes of showing that design is about collaboration and working together, not about opaque hand-offs and “design black boxes”. What better tool do we have than Figma, to show the collaborative nature of design? Please please please do allow for on-premise deployments of Figma — and help us all in traditional companies bring change slowly, one tool at a time. 🙏 I understand that this feature request is pretty far-off from Figma’s product philosophy so far, but well… 🤞 (Hey, our companies usually can pay too.)

When working on complex files with deeply nested layer structures, the fixed left sidebar creates a significant workspace constraint. On a single monitor, navigating the layer hierarchy competes directly with canvas space. On multi-monitor setups, there is no native way to move the layers panel to a second screen so the full canvas width can be used on the primary display.I would like to be able to detach the layers panel and open it as a standalone, resizable window, either on the same monitor or on a secondary display. This would allow me to keep the full canvas in view while navigating and inspecting the layer tree, particularly on large or structurally complex files where frequent layer panel interaction is required.This would benefit designers working on multi-monitor setups, those managing files with deep nesting or high layer counts, and anyone who finds the fixed sidebar a bottleneck during detailed inspection or handover work.

Why did my design files disappear by themselves and I can't find them?

In Figma, all the boards, etc can only be sorted by when I last viewed. That’s not very useful (I know what I’ve viewed) What would be much more useful would be to view by last edited so I can view what is the most recently changed thing.

Problem: When defining "Preferred instances" for the new native Slots, we can only select base Component Sets. Inserting one always loads the default variant, requiring extra clicks to reach the desired state.Request: Please allow us to pin specific variants (e.g., State = Active) directly in the preferred instances list.Why: Saves clicks, provides strict guardrails, and clarifies exactly which variant is intended for that slot right out of the box.

Senior engineer, 6 years in. I can read a codebase faster than I can read a Figma file.Every Design - Dev handoff is a different puzzle and you're the one solving it on the clock. Here's what's started bothering me more recently — it's not just a me problem anymore.My AI agent can't read Figma either.I've been using Claude for few months. It's fast, it's good, and it's completely blind to design intent. I paste in a component description and it hallucinates spacing. I give it a screenshot and it gets the layout roughly right but the tokens wrong. There's no file format that bridges "what the designer built" and "what the agent needs to implement it."What I actually want when I pick up a ticket:— A file that tells me the flex direction, gap, padding, and alignment of every layer. Not a screenshot. A structured file.— Token names, not hex values. color/background/primary not #6750A4. My codebase uses tokens. My agent should use tokens.— A u/theme{} block for Tailwind v4 I can drop straig

I see you’ve added the ability to name sections now in the overview view in slides, big fan. But what i thought would be cool would be the ability to add that title/text as a dynamic piece of text to a slide like a page number.This would be really useful for Overlines/footers in templates and live documents where you might want to add signposting to a slide. For example my slide footer will have the section name on the left, and rather than having to edit this on ever slide, having it auto populate from the section name would be awesome.

Right now, once you create a Main Component, there is no way to convert it back into a normal Frame/Group/Autolayout. If a component is no longer useful, we are forced to use the workaround: create instance → detach → delete main component. This adds extra steps and slows down workflow. Request: Please add a simple option like “Remove Component” that instantly converts a main component back to its original state.This would save time, reduce friction, and improve cleanup when working with experimental or temporary components.

Hi there!We use the comment feature (C) a lot in Figma for feedback and collaboration across the team, but it doesn’t work well for tracking design tasks or to-dos.Right now we misuse comments for task tracking, which creates clutter and causes important items to get lost. Also, not all tasks should be visible to the wider team outside design team.What we’re missing is a simple task system for designers! Nothing heavy — just a clean way to track internal design tasks without mixing them into comments.Here an example 🙂TaskFor example a ‘Task tool’ similar to a comment tool with features like:text field assign to @name mark as done optional priority (high) This would significantly improve workflow for design teams. Thanks! 🙏

Hi there,One issue we noticed with the new Slot feature is discoverability inside components such as tiles or cards.Currently, when a slot is configured in the properties panel but the final component is not hovered, the slot area is completely invisible. Because of this, users do not realize that there is an adjustable slot inside the component.At the moment, the slot only becomes visible on hover, which makes the feature difficult to discover. I attached screenshots showing:a non-hovered state where the slot is invisible   a hovered state where the slot becomes visible   My concern is that slots should remain somehow visible when empty.Would it be possible to introduce a subtle always-visible indicator for slots, without requiring a full background color? 

Hello,Have raised multiple tickets and having an enterprise paid subscription. Support is quite poor in responses with closure of tickets with no responses either. What’s the point of an enterprise subscription if we aren’t able to reach support?  

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.

Hello, I would like to propose an improvement for navigation in the design files.In our project, we add many internal links to specifications details, which facilitates the timely consultation of information.On the other hand, after following an internal link, it lacks a simple way to return to the previous location in the file, such as a floating Back button or a behavior similar to "Return to instance" after navigating to a component definition.It would also be very useful to be able to automatically display the list of backlinks pointing to a given section, frame, or element.This type of functionality would greatly improve navigation, reading documentation, and working with complex files that have a lot of cross-referencing.

Layer names can get really messy when layer renaming is enabled, and the number never seems to be very useful for me. (ex I don’t remember what “Frame 324” is, I usually just reference a named parent/child for context). To me, it’s just additional noise in my layer list. Thankfully, Figma offers an option to disable this, “Rename Duplicate Layers”. This solves my issue when duplicating, so I don’t end up with “List Cell 2, List Cell 3, etc”. But… New frames & groups still get a number added by default. This can sometimes result in seemly very random numbers appended to a new group or frame, depending on how it’s added, or what already exists in a Project. For example, drawing multiple Frames will cause them to increment, but if you group an item and apply auto-layout, it starts again at 1. See this example. The behaviour I’d rather have Don’t append any number to layers when this option is disabled (New frames would simply be “Frame”, and you could create multiple elemen

Using shift+click the variable search opens automatically on most fields. The Gap field in AutoLayout is excluded from this and does not have a variable picker icon but it needs to be selected via dropdown every time.This is inconsistent and I think it should be also possible to have shift+click open the variable search.#littlebigupdates

When working with design tokens, not every variable should end up in an export. Internal aliases, private overrides, or work-in-progress tokens are often necessary inside the file but irrelevant for code.Right now there's no way to exclude individual variables from export.Extend the existing "Hide from publishing" checkbox so it also suppresses the variable from export output Or add a dedicated "Hide from export" checkbox (as shown in the screenshot)Low effort, high value. 🙌

it would be nice to see variable usages so one can actually know which variables are redundant. which variables are not tied to any property. its easy that way to say okay we are no longer using this based on a 0 or 3% usage then go ahead to delete. right now i have a whole lot of redundant variables which i don’t know about because an attempt to delete might cause error in the file.

Figma Make are not using my library components attached. It only picked “generic” ones. Both with “Attach design” and using a full design system library file.

I’m working with Figma Buzz to create some social media post templates. My template includes an image nested within a mask. I would like to allow the rest of my team to use these buzz templates and provide them with a simple way to place images in the desired space.Using slots works almost perfectly in that it enables me to designate the frame within a mask as a slot and placing the image involves a simple drag-and-drop into the slot. With all other layers locked, this makes my template very easy to use.However, having the slot frame not locked makes it easy to accidentally move the slot altogether, which in turn ruins the layout of my template. Locking the slot prevents it both from being moved, but it also prevents the drag-and-drop functionality from working. QuestionIs there a way to lock the position of a slot frame without disabling the drag-and-drop functionality? Feedback on SlotsIdeally, slots nested within other frames/groups would work with the layer locking feature using a

I love the new variables feature but have hit a snag I’d love to see resolved. As I’m the only UX practitioner at my company, we only have the professional plan which means we can’t use branching. Instead, we have developed a system where we initial design in a “WIP” file, which is reviewed and iterated on until approved; at this point, we copy things over to a “Live” file. While working through that with some variables now in use, I discovered that there’s no way to copy variables between files. I can’t just use variables stored in a library because I need to get the variables from our WIP Library project into the Live Library product and, by their very nature, they can’t refer to the same library of variables (changes made to a variable value for the WIP library shouldn’t be automatically updated in the LIVE library). It would be helpful if one could either export and import variables by collection or individually. Or even if one could select one or more variables to copy and then pa

Now that Figma is officially available and expanding in India, I’ve been wondering:Why are subscriptions still not localized for Indian users?Currently:pricing is shown in USD many local payment methods are unsupported international card payments don’t work smoothly for everyone currency conversion + taxes make subscriptions more expensive and confusingFor a lot of students, freelancers, and early-stage designers in India, this becomes a major barrier even if they genuinely want to pay for Figma.Why this mattersIndia has one of the fastest-growing design and tech communities:thousands of new designers every year startups heavily adopting Figma huge student creator ecosystem increasing use of AI + collaborative design toolsA lot of people want to purchase Figma subscriptions legitimately, but the payment experience still feels built primarily for international users.Things that could improve the experience1. INR pricingShowing plans directly in Indian Rupees would make pricing clearer a