Suggest a Feature

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.

Feature Request: Link LayersPlease add a "Link Layers" feature similar to Photoshop. It would be great to link multiple layers so they move together while remaining independent, without having to group them or change their layer hierarchy.

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.

This seems like a very large design oversight in Figma Slides. The help article says that “Published changes only apply to new slide decks that are made with the template.” Doesn’t this defeat the entire purpose of having a custom template where you can edit a style and have it apply to your entire presentation, instead of needing to manually tweak a header style on every slide? I expected this to work the same way instances update in Figma Design when you make a change to the main component, but even after publishing changes to a custom template in Figma Slides, my existing slide deck that pulls from that template isn’t updating colors & text styles. The published template changes would only apply to brand new slide decks, which means I’d have to define the template first and then create my slide deck. That completely goes against the general approach to how many of us create slide decks. For example, I don’t make the template before I start the slide deck. I make my slide deck fi

I created this sample logo using Figma’s newly 3D effect (Beta)I wish I can flatten this logo to make it vector and to add outline border as you can see on the “company bw” the shape of the logo can’t be seen on dark background. So if want to add an outline I will trace it using Pen tool and make a white. 

I'm really loving the new Spec feature! It's already made my workflow a lot more efficient!One suggestion: Specs can get quite long, so it would be great if we could collapse and expand sections. Thanks for the great work!

The problem:Right now, when creating complex interactive prototypes, you have to manually set up the same animation and trigger settings for every single new connection.The suggestion:Introduce a feature that allows users to copy properties from one prototype interaction and paste them onto a new or existing connection (e.g., using a shortcut like Cmd/Ctrl + Option/Alt + C and V while in Prototype mode). It should work exactly like copying fills and strokes between frames in Design mode. This would drastically speed up workflow efficiency, especially when fixing or rebuilding flows from scratch. Example: Copy the connection properties from other frames and paste in Interactions.  

When I write create long paragraphs with text tool on the Figma I get the unnecessary spaces on edges of the paragraph like below. But I think if there a hyphenation feature (like Adobe Photoshop) it could add dashes automatically on the texts and fix this issue. So, what do you think about this feature feedback?

Is there a plan to allow multiple values on variables soon?Its helpful to follow the way tokens are usually made on code, for example for padding:--button-padding: 12px 24pxIn Figma, this is important to allow, if not, we need to split the token into:--button-block-padding: 12px--button-inline-padding: 24pxAnd this gets more complex when you need border radius to be different in each corner (x4)Figma team, when will be this possible? Might be not relevant for a simple system, but it’s important for a multi-brand system where paddings are different, and already set with multi-values in the code side.  

I’ve been using Spec to write use cases and product requirements, and I love the idea of bringing product work into Figma, where design already lives. It creates a real chance for a closer exchange between product and design. Here are some suggestions from that experience:Integrations with FigmaSomething like a split view with the Spec and the prototype in Dev Mode. Let developers open a prototype with its connected Spec side by side. Even better if both stay in sync: as the developer navigates between screens in the prototype, the Spec scrolls to the flow step or rule that describes that screen. This way, devs always see the behavior and the requirements together, without switching tabs or searching for the right section. It would also work the other way around: from a section of the Spec, open the related frame or prototype screen. Embed a specific page or frame, not just a whole Figma file. Today I can embed a file, but pointing to the exact frame that matches a flow step would make

Storing credentials, secrets/tokens, in the admin panel so Figma and Figma Make can take advantage of paid features of the enterprise; Font Awesome Pro, organization level GitHub private packages, and other third party paid services.   

I absolutely love Figma Slides!! It’s so cool that slides automatically get grouped into bundles. However, I feel like if there was a way to label these groups, I can organize my rather large (100+ slides) presentation better. Thanks a lot for the amazing work, team! <3

Hello! 🤠I was very excited to see the addition of Auto Layout Grid today! Having flexibility for both Rows and Columns at the same time is a game changer.That said, I immediately ran into not being able to set a column width to “Hug” within a table, which is a bummer. In the attached video, I want the “Audited By” column to Hug to the longest table cell content. I show both the current solution today, and what I am trying to do with Auto Layout Grid.I can manually adjust the width of the column, I guess, but as you can see, it makes it hard to ensure correct padding without a lot of careful tuning of the width. Anyone have any solutions? Will this be coming as a fast-follow feature? Thank you!

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.

In regular auto layout, a layer set to Fill can end up smaller than its own content.It would be great if a layer set to fill could respect the content's size as a minimum. Grid already behaves this way, so I'm mostly asking for the two to be consistent.In css I think the term is intrinsic sizing. 

When I undo, I want undo only changes that I’ve made to a document, not what I’ve selected. I find the existing behavior to be unintuitive and counter to basically all other applications. However, I realize some people like it the way it is, so we can we get a user option to only include document changes in Undo?

This makes it easier to use components in designs for different screen sizes. And then you don’t have to calculate every time what 40% or 60% of the width is. This also makes it easier to design scalable applications that grow with the width of the screen.

Hi Figma team!I'm a product designer working closely with developers on mobile and tablet app design.We've encountered a couple of challenges when developers inspect our designs in Dev Mode. Current challenges: Auto Layout is difficult to identify in Dev Mode. It's not easy for developers to tell whether Auto Layout has been applied to a frame. Unlike Design Mode, where Auto Layout is clearly indicated, Dev Mode doesn't make this obvious. Prototype connections are difficult to inspect in Dev Mode. Developers can't easily identify which screens or dialogs are connected through Prototype interactions. To check transitions, they need to use the Preview button, making it less convenient to understand the overall screen flow. Suggested improvements: Make it easier to identify which frames have Auto Layout applied in Dev Mode. Make Prototype connections and interactions visible and easier to inspect in Dev Mode, without having to launch Preview.  These improvements woul

Our team uses Codex with Figma to build and maintain a shared component library. Multiple designers work with their own agents, each with different tasks and context. Developers may also have their own coding agents working on the corresponding implementation.We can already see other collaborators’ agents and their working status in Figma. That made us wonder: could these agents collaborate with one another around shared design assets, with their owners’ permission?The gap we encounterAn agent can inspect a shared component, but it may not know why another designer made certain decisions, which business constraints apply, or which questions remain unresolved. Today, we have to copy context and questions between separate conversations, relay the answers, and reconcile the results ourselves.A workflow we would find useful1. A designer’s agent updates a component and shares an approved brief describing the goal, changes, constraints, asset version, and open questions.2. Another designer a

Hello, Lastly I faced a problem with the wrap mode. I need to be able to fix a max number of items per line before wrapping to the next line (with a min/max width per item of course). It’s for the sake of simplicity because I don’t want to remove wrap mode just for that. Should be clear enought, if you have any further question ? 🙂 Cheers, Xavier.

The library we are using in our company can be modified by several people in the team. When I want to publish changes to the library, sometimes I would see changes I didn’t make. Or sometimes it was a change I actually made that had an impact on another component, but it’s difficult to understand right away given that you can’t have a close look at what has changed exactly (the preview is so tiny!) It would be great to have some kind of before/after preview each time I hover one of the components in the “changes” list. It would reduce the risk of publishing wrong components that are not well built. Because right now I always have to ask my team if they have touched anything in the library which is getting tiresome to be honest. Thanks ✨

Would Figma consider supporting Variables for variable font axes in the future?We're using Google Sans Flex and switch between two visual modes:Formal - `Rond = 0`Friendly/Cute - `Rond = 100`Example of the ROND (Round) axis in Google Sans Flex. We use this setting to switch between formal and friendly typography styles.​​​​​Currently, font axis values such as Round (ROND) cannot be controlled by Variables. Because of this, we have to maintain two separate text-style systems even though everything else is identical.after add rondIf variable font axes could be bound to Variables, we could switch typography modes through Variables and maintain a single text-style system instead.Example concept: Variable Font axes such as Weight and ROND could be connected to Figma Variables, allowing typography modes to switch automatically.This would be especially useful for design systems that use variable fonts to express different brand personalities across themes or modes. 

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. 

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.