Share Your Thoughts

I still consider myself a newbie in Figma (this is a caveat), though I’ve had a chance to play around with it. My hope in using Figma is that it will make it easier and quicker for those collaborating with designers - mainly PMs, Devs, and QA, to find the designs they are looking for. Coming from Invision, it was a pretty bad experience (sorry Invision), and after checking out Figma and other potential solutions out there, I was sold on Figma (for many reasons), and pitched it to my client. Now we are going in. An important contextual aspect of this topic, is the fact that many, if not most doing software development these days, follow some flavor of agile development - so think epics, stories/tasks, and sprints, for example. So the challenge here is, how to best match up the agile development process, to how everything in the Figma design space is organized, so that designs are quick and easy to find, not just for the figma designers. I was hoping

For God’s sakes why isn’t Figma including this feature? It has been years ever since the community requested this.Use case: Clients keep bombarding comments and would simply like to finalize by deadline of their feedback phase. Isn’t enabling/disabling a basic feature nowadays? Or is there some kind of conspiracy or business ulterior motive behind this?Most of the time Figma keeps on adding a bunch of features but the basic ones - especially for design which is supposed to be the foundation - are not being implemented.

OverviewFigma Variables are already powerful for theming and responsive behavior - but Auto Layout settings remain static. Currently, we can’t change layout direction (horizontal/vertical), item sizing (hug/fill), or alignment (space-between, center, etc.) using variables.This limits the flexibility of truly responsive components - especially in systems using mode-based logic. Current LimitationRight now, Figma only supports number-based variables in Auto Layout settings (e.g., padding, gap, min/max width). But many key layout settings require string values, and they’re not variable-compatible yet: Direction: Horizontal / Vertical Justification: Space-between / Center / Start Sizing: Hug / Fill / Fixed

When marking a comment as resolved, we are now automatically moved to the next one. I’m wondering if or how we can disable this behaviour?My work flow being to go from screen to screen of user flows, and not comments to comments, this is very disrupting as it can bring me anywhere in the file, and I need to find and navigate back to where I was. I understand this might be useful for reviewers that only goes through questions left by other people, but this probably not most users, so it would be useful to have the ability to disable this feature.

Text-style overrides like bold, underline, … won’t work on instances properly, now the instance must be rest for the bold overrides to come though. So a lot of screens needs to be rechecked and manual work is needed everywhere the instance is used. Any solutions for this?

I spend far too much time deleting that blurb when all I want to do is point Claude to the correct URL from the MCP. I have better prompts.Either make that bit go away, or let me copy just the URL.

I don’t use Figma all the time, I don’t want it to run anything on startup. It’s frustrating to manually remove Figma from Login Items, since it automatically adds itself there again. It would be nice to have at least an option to disable it in settings, or even better - remove that functionality at all, since it’s not user friendly. I want control over what and when the apps do at my workstation. P.S. If it’s needed for updates check - I’m more than okay to update on app start

Hello, as the title states, I am curious if GHES support for Code Connect is coming or is this a hard limitation and we should never expect that service? Thanks!

Figma Make is the best prototyping tool I have seen so far (yes, better, or at least more time efficient, than V0 and Claude Code for now). It also has an integration with Github, which is suuuper cool. Now… it would be REALLY gamechanging, if the connection with Github was a two way sync. If edited code could be pulled back into Figma Make, for team collaboration across multiple platforms. I understand that this is really tricky, because Figma Make can't interpret all types of code… but I'm putting it out there… 

I would like to “protect” or “lock” specific pages within a file from receiving library updates - similarly to how I can hide components from being published, but applied on the receiving end. This would allow me to update all of the components in my file much quicker if only one or two pages were “protected”, rather than needing to go through each page individually and apply the updates. The types of protected pages would likely be from a demo or a prototype version that captures the evolution of the product’s design phase.

Native Dev Mode annotations are valuable sources of context that get lost for anything using the MCP. Measurements and props, too, although I don’t think that’s nearly as important. My response from Github Copilot:This is a limitation of the Figma MCP server that powers my Figma tools — it currently exposes the layer/node tree but not the annotations or comments API endpoints.

With the new update, we have a great new feature, but unfortunately, it’s not usable with our component structure. Exposing all props of a nested instance also exposes props that we don’t want in the context of the consuming component. What if we could also select which properties to expose? This would lead to a cleaner sidebar with only valid props.

Hey there! I was also wondering if it is somehow possible to include also the layer of variant controls to be exposed or hid! I often have cases where I need to nest base components e.g. an icon wrapper providing me with the ability to select certain sizes, or color overrides and boolean props of an icon. I am now able to expose all of those or none, but I can’t restrict the users to only be able to select just some of those. What do you think about it?

This feature can create a copy of design file with all the variables and components intact.To convert, user can may have following option to choose for smooth conversion:a primary screen size copy existing screen to figma site file or leave blank (variables and components intact) choose 1 page of design file to be converted (limitation for time being)(not applicable in case of blank) keep fimga Make components intact

Hi there,I always use Ctrl + Option + Command + K to jump directly to the main component and also to return to the instance, but returning only works if the main component is still selected.Why does Figma require the component to remain selected in order to return? It feels like it should remember where I came from, even after selecting or editing other layers or components in between.At least the floating button “return to instance” could always be visible.Right now, the navigation state is lost as soon as selection changes, which breaks the workflow when working with component systems.Please make the “return to instance” behavior persistent and independent from selection state — especially for users working heavily with large component systems.Button: Return to instance

 I ran into a font issue while working with MCP use_figma and wanted to share it here. I have a font installed on my system (Pretendard) that works perfectly fine in the Figma UI — it shows up as "Installed by you" in the font picker. However, it's completely invisible to the Plugin API when running through MCP use_figma. listAvailableFontsAsync() returns around 7,600 fonts, but none of them are locally installed ones. It seems to only return Google Fonts.loadFontAsync() also fails, and trying to appendChild a component instance that contains text using the font throws a font load error — even into a non-auto-layout frame. Steps to Reproduce 1. Install a local font on your system (I tried both ~/Library/Fonts/ and /Library/Fonts/ on macOS) 2. Confirm the font shows up normally in the Figma UI 3. Run the following via MCP use_figma: const fonts = await figma.listAvailableFontsAsync(); const r

Are customer inquiries or bug report requests originally this easily ignored?Is it because I can't speak English and translate it?Simple inquiries come in response, but reports and handling of bugs are ignored without reply, even though only manual answers are provided and additional answers are continuously requested.Is it always like that? I've raised the issue in Figma Make where I keep going back to the previous version of work and keep using credits repeatedly, and I've sent 3 additional requests for answers since the last message 22 days ago saying I'll look closely, but I'm being ignored.

Hello, I couldn’t find a feature in Figma where we can constrain trigger or hotspot bounds to a vector shape instead of a rectangular bounding box. The current version doesn’t support the design use cases similar to those below (eg: interactive pie charts) where transparent pixels are ignored in a non-rectangular shape because the hotspot bounding box is always rectangular. It would be nice to constrain the hotspot area to the desired shape instead of a rectangle. Please check the attached Figma file. Hotspot bounds.fig (7.0 MB)

Feature Request: Reset Bounding Box / Auto-Swap Dimensions on RotationOne workflow improvement that would greatly help designers transitioning from tools like Illustrator is better handling of rotated objects in the properties panel.Currently in Figma, when a rectangle or shape is rotated 90°, the Width and Height values in the right-side Layout panel continue to reflect the object’s original, unrotated dimensions rather than its visual orientation.For example:- A rectangle created at 628 × 56- Rotated -90°- Still displays as W: 628 / H: 56This can become confusing when working with:- gradients- auto layout- constraints- responsive components- production handoff- precise UI sizingAdobe Illustrator recently improved this behavior by automatically updating dimensions based on orientation, or allowing users to use “Reset Bounding Box” to redefine the transformed state.Suggested improvements:

Figma has been a pain in a**. The entire Figma feels shit. Figma never fails to disappoint me everyday. If you are giving big a** boxes then it should be entirely clickable why do I’ve to stick my cursor to text. It happens everywhere in layers, design panel, variables. For each select I’ve to press at least 3 times then it selects fully and that too when I hit that small clickable text area. Everything is so irritating. And after making components why the hell does it need to add useless “State=” word in it. I cant even batch rename it. The rename box should be expandable so I can see the entire name if its big. The color picker should’ve pin feature. Thousand time I’ve to click that color to open it. And in variable when we are adding colors it comes in the way of variables.  If I’ve created H1 regular Text Style and want to create H2 Regular Text Style, the duplicate option adds the same style inside the H1, it should create some H

Request: Through the Figma MCP, access contents of comments made in Figma Design file.Reason: Can provide context for designs, review bugs, etc.Current response from OpenAI Codex with direct link to comment:No, not the comment itself.What I can see from that link is the node it points to:file: XXXXXXnode: XXXXXXscreen: /sign-up-2 (iOS)That screen contains:nav title Sign UpEmail and Password inputsSign Up primary CTAContinue with AppleContinue with Googledivider OrAlready have an account? Sign inbottom legal linksBut I still cannot read the actual Figma comment thread or the #XXXXXX anchor content from this session.If you want, paste the comment text here and I can map it to this exact screen and tell you what change it implies. 

I have noticed a regression on text property function in components. In the past, I was able to apply different text colors across variants, but this is no longer working. The text property now overrides styling in a way that prevents variant-specific color adjustments. In another case, the text property does not properly handle different variant states. For example, when creating an accordion component with open and closed states, the text property does not adapt correctly even though the text layer on the header remains the same. This limits the ability to manage dynamic components effectively and requires manual text update when designing variation of screen sizes and states. The text property was introduced to simplify updating text across multiple variants, but the current behaviour makes this workflow more difficult. At its core, this feature should allow users to update text values regardless of styling or variant differences, as long as the text layer is assigned to the prop

 When creating grids on Figma, it would be useful if one could pick a specific column or row and just drag it across the layout to reorder content.Sometimes the content is too complex to select each individual cell and just move it around with the arrow or dragging. It could be cool to drag the whole column or row to reorder content.I think this is a natural instinct for most people, and not being able to do it when designing is kind of restricting in my opinion. The handle could even be the current “circle” that appears above/aside the table.   

I'm excited for Bulk Create in Figma Buzz. It’s a lot more intuitive for our marketers to use, but at its current stage it’s actually more time consuming than our existing workflow, mainly because it doesn’t have the ability to bulk rename frames or the exported filenames. That means we still end up having to manually rename "Frame1.png" all the way to "Frame175.png".Here’s our use case: we need to create OpenGraph images for a website with over a hundred pages. We have two design templates: one with page title only, one with page title and a subhead.Currently, the marketing & web dev team maintain a spreadsheet of all the pages currently exist.We have the 2 designs set up as components and use a plugin called Scribe - Dynamic data in seconds to pull in the CSV and use a column we choose for naming the frames / files.I can see Bulk Create doing this as well, and even adding some common renaming & conditional naming option

Every time I exit Figma and come back, the previously selected sort order is lost, and it defaults to "Last modified" – "Newest first". Previously, the selected sorting option was always preserved.