Share Your Thoughts

Figma Slides’ inability to create charts is the only thing keeping me from moving our company away from Pitch. I’m sure charts are on the roadmap, and when they get here they’ll be great, but I was wondering whether it might make sense to offer a Datawrapper integration in the meantime. Datawrapper charts can be embedded on the web as iframes, and while it’s pretty clear from looking through Figma’s plugins that embedding an iframe on the canvas isn’t trivial (otherwise I’m sure we’d see all sorts of similar applications), I’m wondering whether it might be worth making an exception for Datawrapper given how long it might take for Figma Slides’ capabilities to catch up. In the meantime, I might experiment with simply exporting Datawrappers as image for use in Figma Slides, but if anyone else has found a better solution, please let me know!

Hello Figma Team,When I share a Figma prototype link with users outside my organization, I would prefer that the “Open in Editor” option is not visible to them.Currently, even external viewers can see this option, which may create confusion or unintended access expectations. It would be helpful to have a setting that allows us to hide or disable the “Open in Editor” feature specifically for users outside the organization.Please consider adding this as a configurable permission in future updates.Thank you for your support.Best regards,Rajnish Pal

We've been using Connected Projects at Sanofi to work with external agencies, and honestly? The feature falls short for how agencies actually collaborate with companies.The core issue: A single Connected Project is too limited when you're embedding an entire agency team into a client organization.Here's what happens today:Agency designers get access to one Connected Project They can use company libraries and embedded documentation That's itWhat's missing:1. Team-level connection, not project-levelWhen we onboard an agency, we're not collaborating on a single project. We're integrating their entire team into our design workflow across multiple initiatives. We need Connected Teams, not just Connected Projects.Think: Agency X works with us on 5 different products simultaneously. Right now, we'd need 5 separate Connected Projects, each requiring individual set

Please introduce compare changes to the publish screen (similar to how you have when comparing branches). Currently if you want to publish something all you see is a tiny thumbnail and no details of what the changes are.

Hi Figma Team ,I would like to open the “review and merge changes” window with a keyboard shortcut, since I use it quite often, like the publish dialog with option+3.Also “create branch” doesn't have a keyboard shortcut, or “see all branches”. This makes working with branches very mouse intense.Unfortunately they are not even in the Mac menu so I can't create a custom shortcut for them.Please fix this :) ​@seni maybe you know which team is responsible for this?Best regardsMikka

“Please add a feature that allows moving a note after it’s written. Sometimes the note falls in the middle of the design, and that’s really not good.”

Now that we have variables support for text styles, it’s taking a while to update all the properties to match text variables. It’d be really, really helpful to be able to apply variables to multiple text styles at once, by selecting all font styles that we want to apply a variable to and editing the property, since most of these are shared between different styles. With that feature, text migration to variables would be super easy and seamless.

Figma's current branching is a bottleneck. All branches must come from main.If one designer is working on Feature A (v1.1.0) and another is on Feature B (v1.2.0), the designer on Feature B cannot get updates from Feature A. They are blocked until Feature A is fully merged into main. This forces designers to either wait, or manually copy-paste work, which breaks components and causes errors. The Solution: We Need Git-Style Branching To fix this, we need three features that developers use in Git every day: Branch from Branch: Let me create a new branch from any existing branch, not just main. Update from Branch: Let me "update" my branch by pulling changes from any other branch (e.g., merge Feature A directly into Fea

e.g: when i  try this codecursor agent mcp login Figma ✗ MCP login failed Failed to load MCP 'Figma': MCP server "Figma" has not been approvedand  when i try this cursor agent mcp enable Figmacursor agent mcp login Figma✗ MCP login failed Unexpected error during MCP login: HTTP 403: Invalid OAuth error  response: SyntaxError: Unexpected token 'F', "Forbidden" is not  valid JSON. Raw body: ForbiddenIs this authorization method available now?  how?  or Have you considered terminal authorization?

Here’s my understanding of the current level of code syntax support in comments and annotations, which I discovered through trial and error: Annotations: inline code snippets are supported with markdown `like this`, but code blocks with triple backticks are not supported Comments: neither inline code snippets nor code blocks are supported Please expand code snippet support!  Annotation: Comment: 

When clicking “Review library updates” (with the blue notification dot on the library icon), the Manage Libraries panel still opens to the Recommended tab instead of Updates. This makes it easy to miss actual updates — especially since the Updates tab no longer displays any visual indicator to show that updates are available.The Recommended tab is useful, but it’s far less important than reviewing and accepting library updates, which happen more frequently and directly impact active work.Two improvements would make this clearer and more consistent: Default the panel to the “Updates” tab whenever updates are available. Add a visible indicator to the Updates tab itself (e.g., a blue dot or badge count), so updates remain obvious even if the user switches tabs or reopens the panel. These small changes would make library up

Figma is a powerful design tool that allows designers to create and collaborate on projects seamlessly. However, as the number of projects grows, organizing your workspace can become a daunting task. Finding specific projects can be difficult, especially if your workspace is cluttered and disorganized. Fortunately, Figma provides users with the ability to create folders and subfolders to keep their projects organized and easily accessible. One of the most useful features of Figma is the ‘Drafts’ section, which allows you to save incomplete or unfinished projects. This feature is especially handy when you need to work on multiple projects simultaneously, but don’t want to clutter your workspace with unfinished designs. The ‘Drafts’ section gives you the ability to save your progress, so you can come back to it later. To add a folder to your Drafts section, follow these easy steps: Click on the ‘Drafts’ section located on the left-hand side of your Figma das

When adding a conditional on click interaction in Figma, the boolean only switches the variable on/off and there is no option to smart animate the boolean variable.

Multiple times per week I go to hit CMD + A or CMD + W in regular use and accidentally quit everything. Maybe some people like being able to quit quickly but it’d be nice to have an option to turn on a “Hold CMD + Q to Quit” blocker like Chrome has. Or just a confirmation to quit. 

@Figma ^^^ This issue has comments disabled, but it’s still a problem. When are you going to fix it?

I’m hoping for a Figma Make integration for Gitlab like they did for Github so I can more easily share the code with developers at my company. I think the workaround is to ‌download a zip from Figma Make and place into a project in an IDE like VSCode to then connect to Gitlab. It’s not ideal, especially for designers.Hopefully I’m not missing a better solution that exists.

When using Auto Layout for an entire page flow, not everything is spaced equally. For example, imagine a page like: Toolbar Heading Paragraph Input Button To put all of these into a single Auto Layout and give equal spacing to all of it is not typically how it’d work (eg, Toolbar + Heading might be close together, but more spacing around above and below the Input). To use the benefits of Auto Layout, I wrap these objects into their own Auto Layout frames and then use the padding within these nested frames to create the spacing between elements. It’d be great to be able to apply margins to objects (like text frames or other frames) without having to first nest them into their own individual frames. This would be closer to how CSS typically works as text elements (h1, h2, p, …) don’t need to be nested in a div to have margin added to them.

I think it would be really cool to have a feature on our community pages to have a section for portfolio. The idea would be you can share projects/case studies as well as bucket items. I’d love to just use my Figma community profile but I don’t want to share projects that others can download at times. There could be something pretty cool here. 

This is a regression in Crop behavior.Previously, it was possible to adapt a 16:9 image to a fixed 1:1 (768×768) exportby symmetrically pulling the left and right crop edges toward the center.The content itself was not edited, only the visible area was adjusted.This workflow exported a correct 768×768 image without empty paddingand without cutting important text.Currently, Crop enforces strict aspect ratio behavior.When adapting 16:9 → 1:1:– using Fill crops important content– using Fit / Scale results in empty bands (letterboxing)This removes a previously available and widely used workflowfor preparing fixed-size marketing assets where content cannot be modified.This is not a design request but a regression.There is currently no way to reproduce the previous behaviorusing Crop, Mask, Frame + Clip content, or Image Fill.Please consider restoring the previous Crop behavioror providing

Why you placed this button so far? It would be nice to group all the buttons together. Now I have to move my cursor far from other actions I’m working with.  

Figma Desktop opens but the main hub never loads. Browser works perfectly.I cannot open menus, create new files, or access settings.Full cache reset, deleting Figma Agent, reinstalling, disabling GPU via flags, and reinstalling older builds did not resolve it.This started immediately after the 126.0.4.0 Windows update. Anything else I can check? I use the browser sometimes but it takes a while especially when I am using fonts that I installed and takes longer to load.

I’m experiencing an issue when copying components from Figma Design to Figma Buzz.Steps to reproduce: Create a master component in Figma Design. Copy this master component from Figma Design. Paste it into Figma Buzz. Expected behavior:The pasted component in Buzz should become an instance of the original master component, maintaining a live connection to the master in Design.Actual behavior:In Buzz, the pasted component retains all its properties and structure, but it is no longer linked to the original master component in Figma Design. The connection to the source component is lost.When I make updates to the master component in Figma Design afterward, only changes to nested components propagate to Buzz. Changes made directly to the top-level master component do not sync.Workaround and related issues:A t

I’d like to suggest a small but useful feature improvement for overlays.Currently, when opening an overlay, we can only apply a colored background with reduced opacity. It would be great to have an option to blur the background while also applying a color tint (blur + color combined), similar to native mobile UI patterns.

Similar to linking the string variable to component properties to update the variantWhy not component linking with same solution? Just need to have same structured nameThis enables component usage mapping, figma make also can easily configure the global component if we have this function ready and running

I would love to see the ability to define a set of brand colors within a Figma Buzz template that end users can easily apply to (parts of) text.Specifically, it would be great if template creators could: Add a predefined selection of brand colors to the template. Make these colors available as text color options for users of the template. Allow users to apply these colors to specific words or text selections (not just entire text blocks). Use case:For branded social posts or marketing materials, users often want to emphasize or highlight a specific word in a headline or sentence using a brand color.At the moment, users can technically change text colors by unlocking the template. However, this removes all restrictions.What’s missing is a controlled middle ground: Users should be able to select a word and apply one of the predefined brand colors.