Share Your Thoughts

Within CSS padding spacing, it goes:Padding: TopBottom LeftRight;While figma visual editor has: Padding: LeftRight Top Bottom; 

Hello everyone!Somehow Figma design started to show tags on video in canvas. Not in jam, not in dev mode or prototype, just basic canvas.Didn’t find any options to turn it off, figma support agent didn’t help.I have no HTML tags option in right sidebar, no annotations enabled and such, how can I turn them off? 

hey there! variables seems to be super nice but what i am missing is that if i make a colour alias to a specific collection - i can’t set the opacity separately (e.g. colour 50 with 20% opacity) So basically i want the colouyr to be from another collection and i want to set the alpha seperatly (controlled as rgba - since i dont need it as opacity) Example how we can fix this in token studio:

Coming from a design org where designers with full-seats have a variety of workflow-types. Some designers leverage AI heavily while others do not, thus some designers burn through AI credits and others have a generous amount that go to waste in that AI credit cycle. This trend can vary, of course, so as an admin, I think it would benefit our organization with some type of allocation or redistribution of AI credits to those seats who rely on them during a given credit cycle—credits that are technically available within our organization. It could even be a designer-to-designer interaction where Designer A shares 1000 credits with Designer B if they know they don’t need all their credits that cycle.Is anyone else seeing this trend in their organization, or see this as a potential scenario? I want to make sure we’re getting the most for our money and optimizing resources across the team.

I’d like to suggest an improvement that would streamline the design process—especially when working with components.Currently, when resizing or aligning elements, I need to press the ALT key to view spacing measurements (such as padding, margin, and distance between elements). This adds unnecessary friction, especially during frequent adjustments.My suggestion is to add a toggle in the settings that allows users to always show spacing measurements by default. This way, whenever an element is selected, its padding, margin, and size can be instantly visible—without needing to hold down a key or guess the values.This feature could be customizable. For example: Always show padding/margin/size values when selecting an element. Let users choose which measurements they want to see by default (padding, margin, width, height, etc.). This wouldn't overcomplicate the UI but

I need the option to be able to share a presentation with clients in a way that doesn’t allow for members of my team to make updates that client will see while they are reviewing. This would also be incredibly helpful for internal reviewing. This could be in allowing a link to only be updated manually and/or adding an additional layer of permissions. Generally my pain points are: Designers have accidently make updates to a working file and it threw off clients who were actively reviewing the work and added confusion My company uses Page Proof for internal routing already but our clients are happy to use Figma to give us feedback. I need to be able to facilitate internal conversations around client feedback without the client seeing the discussion. Page Proof allows links which works well with Figma, but if the designer forgets to make a duplicate page the comments don’t align with the prototype anymore. Duplicating pages to “archive” ro

I would love to be able to create one prototype across the pages in a file that resembles an actual website. This would be ideal for bigger projects and would be easier to maintain as well. We can connect the component libraries across all the pages anyways. A way to connect the prototype would be great in my opinion and that will give Figma a big leg up on other platforms. What do you guys think?

The way that it works already when selecting fonts from the menu for text without a class applied

We’ve been moving toward a D2C workflow, and we found that component documentation is great context for AI, so we’re starting to put specs and behavior definitions there.The problem is that we also want this to work as shared documentation for designers and engineers, but right now it’s not very visible in either Design Mode or Dev Mode, so people may never discover it.Annotations could help surface it, but since they can’t display the documentation directly yet, the only workaround is to duplicate the content there—which breaks the single source of truth.Therefore, it would be helpful if annotations could directly surface linked documentation content.

Hey We’re in a situation where different billing groups have different billing contacts but that's not possible, so right now it's manually to send the billing out to the right people for every quarter. Also… billing groups don't support billing possibilities. so even though they are grouped like the bill is split it is just a hallucinated separation of billing. why even bother then? please fix

Describe the problem your experiencing and how your idea helps solve this Every time I enable Auto Layout (AL), the detail setting is set to Hug Contents. I realize that in some cases, it makes sense, but not always. We use the fixed width/height quite often, and changing it manually every time to fixed is pretty annoying. Probably introduce a user setting for default AL behaviour or remember the last setting used. Meaning that if I used Fixed the last time, it would be the initial setting next time I enable AL. Add as much context as possible (screenshots, Figma files, mockups, etc.) AL is a versatile tool, and more flexibility would make it even more user-friendly. Ask questions to bring the community into the conversation (e.g. Does anyone else experience this? Is anyone using a plugin or workaround to help solve this?, etc.

Hi,The addition of annotations and measurements to Design mode is such a great decision.However this is rendered almost useless if the annotations and measurements can’t be made visible to View Seat users.Often annotations are used for communication with a range of stakeholders, not just designers and developers. It’s not viable to upgrade every stakeholder to a Full or Dev seat to engage with this content.

I don’t use Figma every day. I don’t want it to open every time I boot my computer. This is a very annoying user experience. I don’t want to have to remove it from system settings every time I Figma updates. Perhaps, you should stop adding it to my system settings every time there is an update. I don’t want Figma to open every time I boot my computer. You are forcing me to open an application that I don’t want open when I boot my computer. This is a terrible user experience. I know other designers are annoyed by this as well. Stop adding it to my system settings every time Figma updates. It’s just dumb that Figma does this. I will use Figma when I need it.

Please add the ability to group pages in Figma.For large projects with many pages — such as a UI kit — it would be much easier to navigate if pages could be organized into groups or folders.This functionality already exists on other platforms.  

Hi,I’ve encountered this bug testing out slots.  I’ve created a desktop component with a slot that uses components and both have variable widths for desktop and mobile. If I drag that instance with slotted components into a frame/section that’s set to mobile it will shrink down, but if I drag it out, the slotted components remain mobile size.Attached is a screenshot of the discrepancy.The instance functions perfectly fine if I manually set the desktop/mobile modes through the appearance panel though. Ps. I love the possibility of slots and can’t wait when it’s out of beta.

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.

 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

Is it possible to obtain a free subscription to the Professional package for non-profit organizations, and what evidence is required for this? Thank you for your response!

I’d like to suggest adding a native option in Figma to mirror (flip) an image directly within its image settings.Currently, when working with components, if I need to mirror an image inside a card, I have to flip the entire card to achieve that effect. This becomes especially problematic when the card is a component, as it interferes with layout, constraints, and overall usability.As a workaround, I’ve been manually mirroring images outside of Figma (on my computer) before importing them back into the component. However, this adds unnecessary friction to the workflow and slows down iteration.Having a simple “flip horizontal / vertical” control within the image properties would make the process much more efficient, especially when working with reusable components and design systems. Thank you!

If I add an instance of a component that in its master form is set to fill, and I am adding it to a frame with auto-layout, I want that instance to be automatically set to fill. That instances are always added as fixed width when the master is set to fill is an annoying inconvenience, especially when nested components also get set to fixed, thus requiring a whole process of fixing widths.

We create and share our design system components with the whole company and we’d like to have a more rigorous process when we publish modifications of the Figma file. If the publish description would be required instead of optional, designers could not forget to add a description to their modifications anymore.

Sections are useful for organising the canvas. However, when I want to keep editing things within a section I keep selecting and moving the section accidentally. Therefore, I would like to be able to lock the section position without locking the elements within the section.

I’m often facing this problem. When I tried to resize the layers panel, it sometimes accidentally dragged the slide which is really annoying. Furthermore, the cursor hitbox for resizing the layers panel is too narrow (it’s really on the edge of the layers size) so that the cursor turns into vertical double-sided arrow. I hope Figma can figure out to fix the layers panel resizing issue. 

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 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