Recently active topics

Hi Figma Team,I’d like to request the ability to temporarily hide the selection bounding box and handles of an active object without deselecting it.The Problem: As a UI design tool, our canvases are filled with rectangular containers and elements. When fine-tuning pixel-sensitive details—such as adjusting complex borders or multiple effects on rectangles—the selection bounding box directly covers the edges and working area, making it very difficult to accurately judge visual contrast. Industry Standard: Other industry-standard tools like Adobe Illustrator and Photoshop already solve this by letting users hide bounding boxes (e.g., Hide Bounding Box / Show Transform Controls). Having a similar toggle or shortcut in Figma would greatly improve high-precision UI work. The Solution: A quick shortcut or option to hide the transform handles/box on the canvas while the layer remains selected.Thank you for your incredible work on Figma!Best regards,Aleix

What should we improve onto make it more useful and help you find the right tools faster?🔹 Add more free tools🔹 Improve website design🔹 Make tools faster🔹 Add better search and categories🔹 Add more AI tools🔹 Improve the user experience🔹 Something else?What would make you more likely to use or recommend ToolsFlash? Share your ideas in the comments! 👇

 What would you like to see improved in our font designs?👉 More stylish fonts👉 More fancy fonts👉 Better readability👉 More unique designs👉 More fonts for Instagram & social media👉 Something else?Tell us your ideas in the comments! 👇 https://www.fontblast.com/ 

Figma’s current image crop is non-destructive, which is useful, but I’d love to have an option to permanently delete the pixels outside the crop.For example, add a “Delete Cropped Pixels” option when cropping an image.The workflow could be: Crop the image. Choose Delete Cropped Pixels. Everything outside the crop is permanently removed. The image can no longer be uncropped or moved to reveal the deleted areas. Normal non-destructive cropping should still remain available.This would be especially useful when working with large images because it could help reduce unnecessary image data and keep Figma files lighter.Photoshop already has a similar Delete Cropped Pixels option, and having the same choice in Figma would make image editing much more flexible.

Hey everyone 👋Some of you might remember when I first shared Free Transform here. Thank you so much for the love and feedback since then. Today I'm back with something I've been pouring a lot of heart into.A bit of context: I've been designing in Figma for over 7 years, much of it graphic work, not just UI. And for all those years, one thing kept bugging me. Any time a piece needed warping, perspective, or a mockup, I had to hop over to Photoshop or Illustrator, do the transform there, export, and bring it back into Figma. Worse, once it was back, it wasn't editable anymore. One small change from the client meant doing the whole round trip again.Free Transform started as my way out of that loop. Free Transform Pro is the part I always wished I had, so the whole graphic workflow can finally stay in Figma:Plane Warp: pin artwork onto any four-point surface. Screens, packaging, signage, done in seconds. Pin Warp: drop a few pins and bend layers naturally, like Puppet Warp. Liquify: push,

Before today, I could select an image, draw a closed vector shape in it, and use Paint to remove or add the image fill within that vector shape. This allowed me to cut out parts of an image using vector geometry, without using a mask.For example:1. Select an image.2. Enter vector editing.3. Draw a closed vector shape over the desired area.4. Use Paint to remove/add the image fill inside that vector shape.If the vector shape was not closed, Figma simply would not allow the fill operation. It did not switch to Crop.Now, when I select Paint, Figma immediately switches to Crop → Custom. The vector shapes can still be created, but I can no longer use Paint to edit the image fill through those vectors.This is particularly important because I have existing Figma files where image cutouts were created using exactly this workflow. They were made with vector geometry, not masks. The objects are still clearly vector-based, but I can no longer edit their image fills using the previous method.I als

Hi , we have an user that is reporting problems to log in Figma. She is requested to add the verification code but she never receives it. I think this is related to this known issue  

I’m having an issue with Figma MCP and I’d really appreciate your help.I’m using Claude Desktop with the Figma MCP connection to work on one of my Figma files. I recently got approved for Figma Education, and I upgraded my team to the Education plan. My account also has a Dev seat.However, Claude is still unable to make actual Figma MCP tool calls. Every time it tries to read or modify anything in my Figma file, it returns:“You've reached the Figma MCP tool call limit on the Starter plan.”What makes this confusing is that the MCP whoami check works and reports my account as:Plan: Student / Education Seat: Dev Role: AdminI contacted the Claude/Figma assistant about this, and it suggested that I first re-authenticate the Figma MCP connection. I did that, but the same Starter-plan error remained.I also discovered that I had previously restricted Claude’s access directly in Figma, so I re-enabled the necessary permissions and tried again. The connection still works, but actual MCP calls co

Since today, right-clicking a folder in the Figma file browser no longer opens the context menu. Nothing appears. This worked normally until yesterday, and I haven't changed any settings, extensions, or permissions.I'm the team owner/creator and have a Full seat, so it shouldn't be a permissions issue.Steps to reproduce:Open the Figma file browser Go to my team Right-click any folderExpected: The context menu appears with folder options.Actual: No menu appears.Environment:OS: macOS version Figma: Desktop app Account: Team owner, Full seatAlready tried: [e.g. restarting the app, logging out and back in, incognito window]

I’d like Figma’s Slack integration to post a notification when someone creates a named version history entry in a file.the message including the title and description of version history entry.

I’d find it useful to set an aspect ratio for cells in Grid Auto Layout. For example, I could set the columns to fill the available width and give each cell a 1:1 aspect ratio. Its height would then automatically match its width, even when the grid is resized.

C’EST UNE catastrophe ABSOLUE QUI M’A RAMENER À PERDRE TOUT MON TRAVAIL PARCE QU’IL N’YA PAS DE L’ACTION “ TRADUCTION DE TEXTE “ DANS L’INTERFACE DE DISCUSSION AVANT L’ENVOIE DE PROMPTS , EN TRAVAILLANT SUR MON PROJET SUR “ FIGMA MAKER “ .. C’EST UN HANDICAP MAJEUR POUR MOI ?????.. C’EST incompréhensible  D’ALLER SUR UNE AUTRE PLATEFORME POUR TRADUIRE UNE PHRASE ET RETOURNER SUR “ FIGMA POUR TRAVAILLER ????????????????????

Looking to better understand gradient behavior in Figma.The example below shows a setup for a Skeleton loading layout/animation. The gradient sits above a background layer with a light grey color.skeleton reference I want the gradient to provide a small white highlight wave, animated across the background layer. It has stops of 0%, 24%, 48%, and 100%. Three of the stops are fully transparent (to match the CSS). Even when set to fully transparent (#00000000), a fill color is present in the transitional areas. This should transition from white to transparent.Currently, Figma requires setting the transparent color to match intended visual styling, here requiring setting the transparency to match the background layer. This feels like an unexpected setup step, and clunky.Is this intended? How does this align to CSS?  

Trying to export any groups, it exports blank PNGs - works fine on SVG output.Latest Figma version on Win11.Tried different projects etc. 

I get nervous having edit-access to a Figma file sometimes, especially as an engineer. I don’t want to accidentally make a change to something in the file. It would be great if there was a way to switch myself to a read-only mode (temporarily) to avoid accidentally breaking/changing something. For now, I’ve just been creating a new branch. If I change something on the branch, then I don’t need to worry.

I have this prototype issue that I’m facing when I interact with an interactive Button component I’ve created and placed inside another component that uses Figma Slot.To provide some context, I’ve used slots in the component when the Accordion component is in its expanded state to provide flexibility when designing its contents.In a design that I’ve made, I’ve placed an interactive Button component inside the Accordion component’s slot. When I place this accordion component in a new component (I call it a design template), the Button’s states (Hovered, Pressed state) breaks, resetting it to the default state when hovering or pressing it in Prototype view.If I place just the Accordion component somewhere else outside the design template component, the Button’s states interaction works just fine in the Prototype view.I’ve attached a video of the issue that im facing.

IssueSmart Animate has suddenly started producing a dark/gray visual artifact behind layers that use semi-transparent gradient fills during the transition.I have been working on the same Figma file and the same component for the past four days. The prototype animation was working correctly until a few hours ago. I did not make any changes to the component structure or animation setup that would explain this behavior. The issue occurs both in the Figma Desktop app and in the browser. What happensThe component uses Smart Animate with a Custom Bezier easing. During the Smart Animate transition, layers containing gradient fills with reduced opacity appear to reveal a dark/gray background or compositing layer behind them. It looks as if a dark surface is temporarily being rendered behind the semi-transparent fill during the animation.The darkening does not appear as an overlay on top of the entire component. It specifically appears behind the transparent/semi-transparent areas of the gradie

Upon creating ideations with Figma make and publishing it as Figma Site, and sent to end users.The end users must have a facility to add comments to the figma site. 

I used to have an option whenever I selected multiple frames and layers to group them into a section, in the right hand sinde panel. It’s gone now since the latest update. Why??? Also, now for some reason, when I tried to get around this limitation and try to do it manually, sometimes when I ⌘+G them and go to the dropdown to select the group type, I have Section grayed out (not always, but in certain circumstances). Why???

On the vertical bar on the left (as per screenshot) how can I swap the 'Agent' button to the 'Assets' one so it's under 'File' instead?    

Hi! First, thanks to the Figma team for all the hard work. Now, let’s talk about Figma Slides Templates. To edit the template styles, I have to select a slide first — which feels a bit unintuitive. In Figma, when you click on the canvas without selecting anything, you can access the file’s styles. Can we bring that same concept into Slides?When I open the template selector, I can edit the styles there through a dropdown. Is that really the best or only way to manage styles in Figma Slides? I don’t think so.Colors & Text Styles: I can delete them, but only through a pretty complex interaction — right-click?Layout Grid: How can I set a default grid? Right now, I have to manually add my custom grid to every new slide I create. If we can't set a default, the feature kind of loses its purpose. :(  

Hi there,An old issue, that was previous solved, has returned. Attempting to add a FigJam sticker from the Cat Cafe collection fails with an invalid image error. See the old issue for additional context.(I’m using FigJam in the browser, Firefox on macOS 26.)Cheers!

I’m trying to upgrade an older Figma Make file to the new Make file foundation by following Figma’s official guide: https://help.figma.com/hc/en-us/articles/43572389630103-Upgrade-your-Figma-Make-files In my case, the upgrade does not complete successfully. It takes around one minute before showing the message “We couldn’t update your file.” I have tried multiple times, but the same error keeps occurring.My current environment is Windows 11 with the latest version of Figma. I also tried upgrading the file on another device running macOS, using a different network, but the upgrade still failed.For additional context, this Figma Make file was created in December 2025. I have another Figma Make file that was created around the same time, and it is experiencing the same upgrade issue.In this situation, is there any way to force the file upgrade or resolve the issue? I also understand that these files may no longer be eligible for upgrade after October if they are not upgraded beforehand.I

Hi guys! I’m also interested in this improvement.

Vertical wrap is now available when auto layout is set to vertical flow. Build multi-column layouts that stay responsive as content is added, removed, or adjusted.What’s new:→ Overflow content wraps into a new column instead of extending past the frame.→ Matches CSS flexbox behavior, bringing auto layout closer to CSS.Learn more.