Share Your Thoughts

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. 

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

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 an explicit “symmetric crop / content-aware crop” option. 

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 temporary workaround is to manually insert an instance of the master component inside the component in Buzz. However, this introduces additional issues: I can no longer apply Auto La

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. They should not need to unlock the template or gain full editing freedom. The template should remain structurally protected while allo

It’s a distraction to look at the files that I won’t be using again. I want few files to be stored but not as active ones. It’s better if we have tabs or statuses for the files like active and archived. Did you guys feel the same?

Another post requesting some way to differentiate pinned tabs from each other.The option to change the favicon, colored, or letting the title run into an ellipses — one of these or all of the above. As it stands right now,  having them as a small squares with no way to tell them apart doesn’t make them nearly as useful.

I’d love to be able to copy and paste conditionals/variables statements, this would save time and errors. For example, I used a similar if statement multiple times and just needed to change 1 or 2 variables and numbers. But to do so, I had to re-write the statements every time.

I really like the idea of having the UI panels auto hide/show on hover from the left and right edges. It makes the whole experience feel much cleaner and more focused, especially when you want to fully immerse yourself in the working space. You still get quick access to the panels without them constantly being in the way, which feels nice and intuitive.

I’m often going through my Recents to find my files, and will often click on the file I’m looking for that comes up first - whether it’s the prototype or the design file. It’s annoying that they’re saved differently. I wish they were condensed into one item that could give me the choice (open as proto? open as design?). Though, also, I’m also almost never trying to open up the proto from my library. I’m almost always going to the design file.  

I think Buzz is a great idea - along with social media templates, maybe email templates could be a cool addition as well (if Buzz is a bucket for all things promotional)

Our team is automating workflows with AI, and we’re loving Figma Make. Only thing is, we can’t collaborate via comments like we’re used to in Figma. Any way to drop comments/feedback right in Make so we’re not bouncing between tools or risking things getting lost?

In the Figma editor, you can change the blend mode and opacity for Sections. But blendMode and opacity properties is missing in both Plugin API and REST API, so it is not possible to read/write it. Please add these properties to the SectionNode object.

I prefer to use my mouse to drag font size up and down to dial things in but the interaction zone must be 1 pixel in size at the moment. In comparison, the drag zone for line stroke is massive and never an issue. I’d be so happy to have this improved, although my mouse accuracy has gone up as a result XD 

All the time I work with component variables and for content on the screens I need to pick random variables. Would be very nice to have the button to not change each instance manuallyThank you

Team-Scoped Commenting for PrototypesDesigners frequently need feedback from multiple teams (Product, Engineering, Marketing, Legal, Leadership) on the same prototype. Today, separating feedback requires duplicating files or links, which introduces version drift and overhead.Proposed solutionEnable team- or audience-scoped commenting on a single prototype link. One shared prototype URL Comment visibility determined by: Email Domain Team / workspace group Reviewers only see comments from their assigned group(s) Designers see all comments across groups Key capabilities Create multiple “feedback groups” per prototype Group-only or designer-only comment visibility Optional group switcher for users who belong to multiple teams Per-group export and filtering for synthesis Value Eliminates duplicate prototypes and links Reduces cross-team bias and noise Supports sensitive or staged reviews (e.g., Legal, Exec) Preserves a single source of truth while improving f

As a math and science teacher who uses Figma every day, I would like to request that superscript and subscript be added as options in text boxes on FigJam boards. Please! It would be so helpful when typing exponents, chemical formulas, and more. Thank you! -A dedicated and loyal Figma enthusiast