Share Your Thoughts

Problem As a front-end programmer I don’t quite grasp the current concept of so called “Local Variables”. For starters, they’re not local, but global. And the thing with global vars is - they make a big mess, like always. For this reason any programming language considers global vars an anti-pattern. But currently, the only way to make a Figma component “stateful” is to keep its “state” in the global namespace. I use quotes for a reason: there is no real state at all, because in Figma there is no an entity like “state of a component”. This all makes flows unmaintainable and prevents us from transferring components between files and projects, because they get transferred without their “state”. So basically you can’t easily reuse components logic. It also doesn’t provide any level of isolation. For example, if I have more than one instance of the same component, how would I distinguish their variables/state

Hi folks! I’ve seen the posts regarding text overrides with nested interactive components but I’m seeing a similar issue with non-interactive components as well. In the example below, I’ve set my text layers to all use the same layer name and have the same hierarchy structure but if I swap one of the nested components it resets everything. Everything works perfectly if each atom component is used individually and not nested in another component though so I’m left 🤔. Any thoughts?

Mural’s tables auto adjust based on items within a cell. If you add another sticky note, the cell expands to accommodate the new sticky. Not having this in Figjam is killing me. 

Currently, when we have many files open in Figma (which is not uncommon in a work context), we tend to lose visibility and access to some of them when trying to switch tabs.Intuitively, I try to scroll horizontally through the open file tabs with no success, which makes navigation quite difficult. As a result, I either have to drag the entire Figma window to the side to expand the view or feel forced to close files just to access others.Is there any plan to improve this usability?Thank you.

It would be a big time saver to preserve the style and formatting of a text layer, when copying and pasting it from one file to another file. Right now the paste operation loses all formatting and I have to re-format the text all over again.

I browse various files in my org very often, and sometimes I’m in dev mode. This automatically subscribes me to notifications which is not what I want.I’d like to be able to set default preferences globally (like “subscribe by default: on/off”), similarly to how another topic states (which to my disappointment didn’t get any replies and was closed for some reason).Or at least the feature to ask me each time to confirm if I want to be subscribed, which obviously would be irritating, but not as irritating as receiving all those notifications and having to open the file to unsubscribe.Or at the very least, to be able to unsubscribe without having to open the file, either from emails or from desktop notifications.

Please make Dev Mode Annotations visible by all roles, not just Full Dev Mode seats. This can become costly for users needing context but not all the other dev-mode features. Here’s the scenario: We have a dashboard, with cards showing a customer’s account status. This status can be mapped from multiple back-end statuses, to show just one front-end status. For example, any of the following could be mapped to a single status known to the customer as “Completed”: canceled, terminated, sold, complete, etc. This is something that the developer needs to reference, but then also the PM needs to reference in writing tickets (who doesn’t need full dev-mode access), the QE needs to reference for testing automations, and various other individuals on our team. Placing it in a comment makes it less clearly attached to the specific piece of the design, and requires us to keep documentation dispersed among different tools (Jira, Confluence, Figma etc). Simply making Dev m

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.

Hi! I upgraded my Figma account from using the free version to the basic plan. Since I did that I can no longer switch to design mode when I could do that with my free account. Please can someone fix this asap. Otherwise I will downgrade my account.

When working with multiple shapes, you currently cannot edit the anchor points of multiple shapes at once whether they are unionized or not. At my studio, we are working on incredibly complex UI for vehicles, and products, and this feature would be much appreciated, and would greatly increase the speed of our workflow.

 Hi Figma Team,I’d like to suggest a feature improvement around managing shared design system files.Problem:In our team, multiple designers have edit access to the design system file. This sometimes leads to accidental or unintended changes, and it becomes difficult to track or control who modified key components. Even with version history, identifying and managing these changes is time-consuming.Suggestion:It would be helpful to have an option to “lock” a file (or specific pages/components) to prevent editing by default.Some possible approaches: Ability to lock a file so only selected users can edit Restrict editing of specific components/pages within a file Optional approval flow when someone tries to make changes Temporary unlock option for maintainers Why this helps:This will ensure better co

I would love edit multiple images at the same time and not have to wait till one is done! Very time consuming to have to wait when you have to do 6 or 10.

My suggestions is to allow users to include annotations and / or measurements  when they export images. Seems that we can’t currently do thisThe user benefits –allows users to share images with annotations and measurements when creating images to be shared wither wider stakeholders and creating documentation for other platforms. If we can’t export annotations and measurements, then for those instances requiring annotations in an export as an image, users won’t use the annotations feature, and revert to creating “Notes” manuallyHope this makes sense

 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

Searched and didn’t see any mention of this. If you have a file with a blue background that you wanna send to someone to test it can be rough. Custom colors would be cool, but at least being able to pick from like 2-4 would suffice. Thanks!

I use several whiteboards with my students.  We always use the marker option.  The marker option has thin and thick for the stroke mark.  For some students the thin/thick option are think on others it is thin. Looking at the pictures below, how can I get all of my boards to allows for the board 2 marker strokes.  I need thinner options. the screenshots from the different boards prove this is possible.  

When overriding a single element inside a slot in a component instance, Figma marks the entire slot as overridden. As a result, updates made to the main component no longer propagate to any elements inside that slot — even if only one element in the slot was actually changed. Expected behaviorOnly the modified element should be treated as overridden.All other elements inside the slot should remain linked to the main component and continue to receive updates.

This is a reference to a topic that was closed without resolution: Reorder objects in an autolayout component instance. Allow for order overrides Share an idea Reorder objects in an autolayout component instance. Allow for order overrides. Allow users to reorder (drag or arrow) objects inside a component instance that has auto-layout on it. Especially useful for components that have r

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.

Firstly great job Figma Font variables are here!!! Figma tutorial: Variables for typography The only thing missing is the use of percentages in the line-height property. You can not use a percentage in the line-height as it only accepts variables that are a number type. Although the variables for line-height caters for pixel (absolute) line-heights (10,12,14)- it does not accommodate relative line heights. In other words you can’t use percentage variables for line heights that are a percentage of the font size (100%, 120%,150%).

This is so annoying! Each month I need to search for the invoice in your unfriendly interface. Seriously now! Better unsubscribe the service than getting such frustration.

Simple one - slots should keep their pink color even when not selecting or dragging. 

Web performance is no longer optional, it’s a core part of the user experience. Yet today, 2026, exporting assets from Figma still requires external tools or manual workflows when teams want to use modern formats like WebP.Adding WebP as a native export option in the export panel would solve a very real and widespread problem:Smaller file sizes without sacrificing quality Faster load times for websites and apps Better alignment with modern frontend standards and performance budgets Reduced reliance on third-party tools or batch conversion scripts (love your plugins folks, but let’s be realistic, it should be a core feature)Right now, the gap between design and production increases unnecessarily because designers can’t export assets in the formats the modern world actually uses. This creates friction, slows down workflows, and introduces inconsistencies (e.i. WordPress native

I do not want my file to be copied. I just want the file that I share to export that can then also be exported. I need more option

Hi! Has the canvas panning keyboard shortcuts changed recently? I use Ctrl+Space+scroll wheel to pan and zoom the canvas but now that keyboard shortcut puts me into a Keyboard picking mode. Is this new? It really gets in the way of working.