Help others

 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.

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

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. :(  

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

I have been experiencing unusual behavior in Figma for several days. When I use Spacebar + mouse to pan, the canvas moves unpredictably in different directions while the spacebar is pressed. Refreshing Figma temporarily resolves the issue, but the glitch reoccurs frequently. I am using Figma Web.

Why is this menu here? Why can’t I close it? If it’s supposted to be there (it’s not), why can’t I move it?I want to work on the icon behind the menu, but after asking a completely useless agent for help I can’t even see the icon.  

Issue with raster images. All Jpgs, PNGs and one .mp4 file appear correctly within the editor and internal preview but when viewing “Share” prototype link, the preview link loads with blanks — for any of those files. Vector assets appear fine. What is the issue? I have tried all of the following with clearing cache multiple times: copying / re-pasting the images re-uploading each image asset duplicating the file to try a new prototype link Clearing cache restarting testing in incognito and on mobile / different devices (same blanks appear)Seems to be an issue with the link itself / Figma server?Please advise. 

I encountered an issue where, immediately after deleting a Team, two important files that were in Drafts became inaccessible. There may be other affected files, but these are the two I noticed missing.I need to regain access to these files as quickly as possible. They are very important files containing ongoing work that took me a significant amount of time to create, and I urgently need them back.Please help me resolve this issue.

Hi Figma team,I'd like to request a per-account option to disable the AI sparkle (✦) icon that appears when hovering over elements in the editor.Currently, the only way to turn off Figma AI features is at the team admin level, which requires admin access and affects all team members. There's no way for an individual user to opt out of the AI hover trigger on their own account.For users who don't use Figma AI, this icon adds visual noise to the editing experience and can interfere with the workflow — especially when working with dense layers or small elements, where the sparkle icon overlaps with other controls.Requested behavior: add a toggle in user account preferences (e.g. Account Settings → Editor preferences) to show/hide the AI sparkle icon on hover, independently from team-level AI settings.Thank you for considering this!

Hi, I have this issue in Figma Make. If I comment in one page and switch to another page, the comments still appear in all pages whenever the page is opened. 

Hello,I want to downgrade seats to our annual subscription due to the non usage. I opened ticket #2145509 more than 48 hours back and there is no response.  For my account, I do not see any options to change seats. My renewal is coming up on Sept 26th and I would like my account seats get downgraded before that. ThanksKalyan  

I’ve had this recurring issue for a long period of time across many versions of Figma. I initially put it down to typing errors, but I ended up with the errors so often that I started paying careful attention.When I input a value for a variant property, the final letter periodically drops off, creating naming errors. 

When I was trying to make a placeholder layer, I noticed that the text bounding box was behaving weirdly when I used symbols (like `()`, `{}`, `[]`) at the start and end of the text layer, and when I had left or right alignment applied. As you can see below, the text bounds end before one of the symbols.  

I have turned on 2-factor authentication on an education account, and it still blocks me from publishing a plugin. I don’t know what the issue is. Please help me resolve. 

I ran into some weird behavior around Figma Motion during plugin development.Having the Motion timeline open in Figma, with any layer containing animations selected, causes that layer’s entire tree to get a hidden duplicate with a new ID. The duplicate tree only shows up in currentPage.children, not in Layers list in Figma’s UI.Also, if the duplicated layer contains any component sets, calling getMainComponentAsync on an instance node will return a new duplicate component that’s neither part of the original or the duplicated tree. The component in both the original and duplicated tree share the component’s original ID, but the one returned by getMainComponentAsync has a new different ID.Repro steps:Create a new Design document with some frame layers Use a plugin to check currentPage.children to verify that the root layers match between Layers list and what’s returned by the API Add animations to any layers, open timeline, and make sure you have a layer containing animations selected Ch