Share Your Thoughts

ProblemToday, applying edit guidance in Figma Make relies on a manual copy-paste workflow (for example, repeatedly pasting guidelines.md and/or CSS adjustments into each new Make file). There is no native way to save a pre-approved “style set” and re-apply it across prototypes, which adds friction and increases inconsistency risk. Current behavior Designers must manually copy/paste the same edit guidelines (and any related CSS tweaks) into every new Figma Make file. Updates to guidance require repeating the same manual steps across multiple files. There is no centralized, reusable, permissioned style context that can be applied with one action. Expected behaviorProvide a first-class way to create, manage, and apply reusable “Style Sets” (approved guidelines + optional CSS) to Figma Make files.Proposed solutionAdd “Style Sets” to Figma Make: Create Style Set Compose and save a named bundle containing: Guidelines (markdown-style instructions) Optional CSS overrides

I have a deck slide longer than the slide therefore I want to scroll to see the rest of the slide. I thought I could do this with a prototype as a workaround but you have to click the prototype to view it so therefore it won’t work. Is there any plan to release this feature after beta, as this is a big blocker for me and my team at present when we have longer pages in our slide decks. Thanks guys.

Hello. With all the updates to auto layout, it would be wonderful if when an engineer is reviewing the designs, they could actually resize a frame to see how the designer intended for the responsive breakpoints to work. Especially since CSS now supports container responsive in some browsers which is essentially how Figma works. Right now, the only option would be to copy and paste frames side by side of different sizes to show that interaction but it only gets you so far and letting the actual engineer modify that width to see the responsive intentions you baked into the design would be way more helpful and less “noise” on the screen for them to review.

It’s nice to add ability to change opacity of desktop Figma app. It will help to make pixel perfect designs

I need a good quality PDF export from Figma with at least the following features editable text export with font embed image export settings, dpi, rgb/cmjn/graysacle, image format, image compression, crop hidden parts full gradient and effects support (shadows, blurs, etc…), if not supported by pdf, then rasterize using above compression settings hyperlinks to urls on any object, no only on texts Today, no plugin seems to be doing the job correctly. PDF’s are dramatically heavy and editable text is not supported… Hey guys, Adobe bought you for 20Billions, I really hope it’s not intended to kill Figma’s roadmap… You’ve published a great PDF export roadmap in 2018… five years ago…

Background:When a new image is imported to replace an existing cropped image, the imported image can often be skewed (the workaround is to select Fill for the mage fille and reselect Crop and the skewing issue will go away). This also can happen to copying/pasting image fills.The skewing is often subtle, and can sneak into production before it is caught. Designers should be alerted to the anomaly. Possible Solutions:One of the following options (or all) could alert designers of the issue: Option 1: Bottom of screen message during/after import:Use a standard status message at the bottom of the screen when an imported image will be skewed.Option 2: Indicator on the image/crop tool:Downside of doing this alone is that the alert is only visible if you pop up the panel. Option 3: Indicator on the image itself when selected (maybe more subtle than this one, but even a colored info dot could flag the issue): 

 Dear Figma Team,I’d like to share a small but impactful usability suggestion regarding image adjustment controls (Exposure, Contrast, Saturation, Temperature, etc.).Currently, these values can only be adjusted using sliders. While this works for quick changes, it becomes difficult to achieve precise and consistent values, especially when working on detailed UI or design systems.Suggestion:It would be very helpful if each slider also included: + / – buttons for incremental adjustment, and/or A numeric input field to manually enter exact values This would: Improve precision and control Help maintain consistency across designs Reduce trial-and-error when fine-tuning visuals This pattern is common in professional design and editing tools and would significantly enhance the overall editing experience in Figma.Thank you for continuously improving the product. Hope you’ll consider this enhancement. 

Would be great to have a native skew and shear tool in Figma. Even with plugins, I’m not finding a way to control the skew anchor. Just something simple like Illustrator’s Free Transform, where you can skew an object and choose where the effect starts from.

I know this is already a topic in another thread but maybe adding more threads is the move to get this to be updated?The feature I’m requesting:Just make libraries and color choosing context consistent across the board.For no rhyme or reason we have to jump through hoops to get the colors already defined to show in the library tab in context to the gradient stop color pickers. Why the disconnect? Are we channeling Adobe here? If there’s an original UX reason behind this pattern, I don’t really care - it’s the IMPACT that matters and the impact is: pure frustration.Thank You 

It would be great if you could add the option to align multiple objects to a key object (like in Adobe Illustrator). You can see more here: Select & Align to Key Object | Illustrator Tutorial If anyone else wants this or has other alignment suggestions please upvote this topic and comment.

Hello there, I am currently having issues viewing the guides on my design when the brand colour is pretty much the same as the guides. Take a look at the screenshot. A suggestion for the guides colour:

Once you add/attach a library to Figma Make it appears impossible to remove it again from the file. Reverting the file to a previous version before the library was added does not help. Telling Make to ignore the library file and not use it also doesn’t help. We need to be able to remove a library from a Figma Make file. Library file settings in Figma Make 

We just wrapped the big announcements at Config, and we know there’s a lot to take in.This thread is your space to share reactions, ask questions, and let us know what you're excited about (or still curious about) with regard to Figma Buzz. Our team will be actively reading and sharing relevant takeaways with the product team.  What we’d love to hear from you:What aspects are you most excited about — and why? Where do you still have questions or want more clarity? Anything that didn’t quite land for you yet?  A few quick reminders:If you need help with a specific account or file issue, please get in touch with a specialist on the Support Team. A note on Community Guidelines: Posts that veer off-topic or become unproductive may be moderated to keep the focus on the product at hand. Keep feedback focused on Figma Buzz — this helps everyone follow along.

In the new mindmap mode, I can’t select multiple nodes and move them to another node at once, moreover I can’t cut and paste them to another node

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 setup and maintenance.2. Access shared files, not just librariesWe embed in libraries a lot of information (Usage documentation / Do's

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

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 updates easier to notice and act on, especially in large files with many linked components.

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.