Suggest a Feature

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?

Need: the ability to move an annotation to another side of a component/frame/whatever, anywhere I want so that it is not blocking anything.

I think it would be amazing if there is a font filter Option for the style like, Handwriting, serif, sans!

Organization would be immensely helpful if we could create folders for our drafts. I want to be able to organize my drafts into different categories (such as UI kits, Ideas, Wireframe kits, iOS, Android, etc…) so I can find files easily. Right now, the drafts page is a huge jumbled mess and I can’t create Team pages for everything. Maybe something as simple as being able to add ‘tags’ to each file, similar to Zeplin.

I need to see the full list of a designer files to transfer ownership to new team member

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.

When using typographic tokens and variables that have pre-determined values for the line-height, the only way to alter the line-height is to detach the variable from the text element and then manually edit the values in the "Type settings" palette. This essentially defeats the purpose of using tokens and variables and makes the detached item hard to update quickly in the future.Please consider adding more typographical overrides in the "Type settings" palette so that we can change the values without breaking the variable connection.  

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.

Is there a way to add ‘Match Size’ when using the Paste to Replace function? (CMD+Shift+R) I have tried a few plugins, but Paste to Replace is more smooth and quick.

Hi everyone,Is there an option to cancel the export action?While the action is running it shows this nice “Exporting...” info:But I could not find a way to abort the action.And if one made the mistake to choose export 1064 x instead of w it takes quite a while until the export action is done. Meanwile I cannot edit anything else.Why not add a little (x) next to “Exporting...” to give a possibility to stop the action? This would be great!Best, Sarah​​​​​

Is there a way to auto-play a Figma Slides presentation? I created a Slides deck for use at a high school career day booth and I’d like to just start it and let it go through the slides automatically and then repeat until I stop it. Any built-in or creative solutions to achieve this?

Right now I’m not able to refresh a page in figma make preview. I have to close the tab and again preview it to refresh it.

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.

Right now it seems like the ‘default’ variant is set based on which variant is ‘upper leftmost’ in the variant container frame. Instead, I suggest decoupling arrangement from precedence, and using the property ordering functionality to determine the default variant. The default variant should simply be the one with the first value for each property, regardless of where it’s placed in the variant frame. This would allow teams to set defaults directly from the properties panel, without having to move components around. See this thread for some more context: How to set defaults / precedence of variants with multiple properties?

Dear Figma,I wanted to bring to your attention that we are in the 21st century, and there are devices specifically designed for designers, such as tablets. I own an iPad, which has an amazing display and can be used with a keyboard and mouse. However, I currently use it only for viewing my designs because Figma, the professional tool I rely on, does not fully function on my iPad. This leaves me with a few options: sell my expensive iPad to buy a PC or laptop, which is less comfortable for me, wait for an iPad update from Figma before GTA VII, or use it solely for watching movies. I wanted to remind you that tablets exist for a reason, and it would be beneficial if Figma could support them more fully.

With the increasing popularity of iPads among creative professionals and the device's capabilities now rivaling many laptops — especially with Apple Pencil support and desktop-class processors — it’s surprising that a leading design platform like Figma hasn't released a fully functional iPad app. Is this a matter of strategic prioritization, where Figma believes the current user base doesn’t demand it strongly enough to justify development resources? Or is it due to technical limitations, perhaps stemming from the complexities of maintaining feature parity with the desktop/web version on iPadOS? Alternatively, is Figma's vision more aligned with a cloud-first, desktop-class browser experience, where portability across devices takes a backseat to collaborative infrastructure? If so, does this approach overlook the rising trend of mobile-first or tablet-based design workflows? It would be insightful to understand if Figma simply hasn't seen en

It would be highly beneficial if we could create Variables for Effects (Drop Shadows, Layer Blurs, etc.) just like we do for Colors and Numbers. Currently, handling different shadow intensities for Light and Dark modes is tedious because we have to switch Styles manually.By adding this feature, switching between Light and Dark modes would become much more seamless and effortless, as shadows could automatically adapt to the active mode.

 I’m building a component library for Figma Slides and ran into some issues:Users can use my published variables / styles inside the components, but they can’t use those same styles directly when creating content themselves in Slides.For example, I built a dark/light mode switch with variable colors. Works great in the components. But if someone adds a new text box, they can’t pick those colors from the library.Would be really useful if published library styles/variables were available directly in Slides, so native content can stay aligned with the rest.

ContextWith the Figma MCP server's `get_design_context` tool becoming a key part of design-to-code workflows, there's a friction point around how variable group separators are handled in CSS output.Figma uses `/` to create variable groups (e.g., `blue/600` creates a `blue` folder containing `600`). This is great for organizing variables in the Figma UI. However, when the MCP generates code, the `/` is preserved literally in CSS custom property names: `--blue/600`.The ProblemIn Tailwind CSS — the default output framework for `get_design_context` — the `/` character is reserved as the opacity modifier delimiter:bg-blue-500/75  →  background-color: rgb(59 130 246 / 0.75)So when MCP output includes `bg-[var(--blue/600)]`, Tailwind's parser interprets `/600)]` as an opacity value, producing broken CSS.The MCP works around this by escaping slashes as `\/`, but JavaScript consu

One important feature is missing = Merging cells 😦 Is this feature included as an improvement in the near future?

Hi Figma team and community,This is related to a similar issue reported here:MCP rate limit not acknowledging subscription I'd like to suggest an improvement to the error messaging around API and MCP access for Dev seat users.Current situation:When a Dev seat user tries to access a Figma project via the API or MCP without having edit permission granted at the project level, they receive this error:> "You've reached the Figma MCP tool call limit for your View seat on the Professional plan. Upgrade your seat or plan for more tool calls."This is misleading in two ways:1. The user already has a Dev seat — not a View seat.2. Upgrading the plan is not the fix. The actual issue is that edit permission hasn't been granted for that specific project. There is

Hi Figma team,My team and I have been experimenting with slots recently. I'd like to propose a feature enhancement: when a component with properties is added via a slot, those properties should be accessible directly from the main component.Ideally, these nested properties would surface automatically, eliminating the need to click deep into the component hierarchy to make edits.

Does anyone know how to turn off Figma’s auto-formatting? I’m trying to type '- ', but it looks like Figma is assuming this text must be a bulleted list. I’m having a similar issue when using text that’s in the format of an email address or a url. Figma is changing these to unwanted links. I’d like to turn off all text auto-formatting.

I’d like there to be a quick way to restart a figma make prototype preview. currently, I have it pasted in my Figjam for a design review meeting, and once i go through the interaction, theres no way to easily start from the beginner. 

Is there a way to turn off the AI chrome when sharing the prototype in "Make"? When sharing in the prototype view, I was expecting it to just share the screens but when I shared the link, it showed the make file with the AI chrome. Is this a big? Or will this be an enhancement?