Report a Problem

Figma now automatically hides/show the layer my mouse hovers, without dragging.  Rep steps:Clicked on the eye icon on layer 1 to hide it.Released mouse button.Moved mouse thru layer 2-5 without dragging.Layer 2-5 were also hidden when the mouse hovered on them. Latest version, happens on both of my accounts, happens on both web browser and the desktop app.Tried a different mouse, still happens.

Dear Figma Support Team,I would like to request your assistance in recovering two Figma design files that have gone missing from my account.These files were not deleted from my end, and no one else had access to them as they were created and managed under my account only. I last accessed these files approximately 2-3 days ago. I tried to open the link I shared with my mate (only view access); it displayed the message "Hmm, we couldn't find that one. This design file may have been deleted, moved, or made unavailable."The details are as follows:Number of missing files: 1 Known file name: MediPort or MediPort hi-fi Plan: Edu Owner: Same account Last accessed: Approximately 2-3 days agoSince these files contain important project work, I kindly request you to check if they can be restored from your end or if there is any way to recover them.Please let me know if you require any additional information to assist with the investigation.Thank you for your time and support. I look forward to you

When I toggle visibility of a layer or object in figma, and then move my cursor over another layer above or below it it hides or reveals those objects too, matching the action I just took. This is an awful bug and its disrupting my work flow. 

I’m writing to ask for some advice as I’ve recently run into a couple of frustrating issues while managing our Design System (D.S.). Every time I publish and update, things keep resetting, which makes me honestly afraid to touch any other components. 🥹Here is a summary of the two issues I'm experiencing: 1. GNB Component Properties Resetting to Default Context: About 3–4 months ago, I created a GNB component in our D.S. Figma file, pulled instances into our actual working design files, and set different properties (e.g., Menu A Selected, Menu B Selected) for each screen. Issue: Last week, I made some updates to the GNB in the D.S., published the changes, and updated them in the working files. Surprisingly, all the custom properties I had carefully set per screen reverted back to the D.S. Default! In the past, screen-specific property settings were preserved, but this time everything changed, forcing me to manually reconfigure the properties for every single screen. 2. Token Componen

Hello Figma Support,I am requesting a refund for a $30.00 invoice related to a paid Dev seat that was activated without my knowledge or explicit authorization. The affected member did not use any of the paid seat features during the billed period.Invoice ID: SVPHCIIZ-0005Invoice date: June 25, 2026Invoice total: $30.00The invoice includes a $15.00 seat adjustment and a $15.00 monthly charge for one Dev seat. Because this seat was enabled without my knowledge and the member did not use the paid seat functionality, please refund the full $30.00 charge and remove or downgrade the unintended paid seat.Please also confirm how we can prevent members from being automatically upgraded to paid seats without an admin's explicit approval.Thank you.

Hello Figma Support,Members on our team were automatically upgraded to paid seats without our intention or explicit approval. We would like to request a refund for the newly added seats and have the unintended paid seats removed or downgraded.Invoice ID: SVPHCIIZ-0006Invoice date: July 25, 2026Invoice total: $36.33Please review the automatic seat upgrades and refund the charges associated with the newly added seats. Please also confirm how we can prevent members from being automatically upgraded to paid seats in the future.Thank you.

When resizing a rectangle or ellipse, or any sort of shape object, dimensions are tethered to the relative top-left corner of the shape—meaning that any increasing or decreasing of the width and height would happen relative to the shape’s top-left corner. This is helpful, since I can rotate an object 180°, and that resizing anchor would move with it, allowing me to adjust dimensions from the bottom right corner. However, recently the shortcut associated with adjusting those dimensions (Cmd + Directional Arrows) now ignores this rule, making it so that resizing any shape with these shortcuts is always resized relative to the absolute top left corner, no matter the shape’s rotation. This requires me to make those adjustments solely using the Width and Height fields, which is pretty tedious. Similarly, corner radii are also now anchored to the absolute top-left. But when multiple objects of different rotations are selected, then it uses the relative top-left corner. So I have to use a wor

When auto-keyframe mode is enabled in Figma Motion, property changes made through the Plugin API behave inconsistently:Stroke width (strokeWeight) — changing this via plugin correctly adds a keyframe at the current playhead position  Position (x, y) and Rotation (rotation) — changing these via plugin does NOT add a keyframe, even with auto-keyframe toggled on Steps to reproduce:Enable Motion mode and turn on the auto-keyframe toggle Select a node From a plugin, set node.strokeWeight = someValue → keyframe is added automatically From the same plugin, set node.x = someValue or node.rotation = someValue → no keyframe addedExpected behavior: All property changes made via the Plugin API should respect the auto-keyframe toggle, just like changes made through the UI do.Workaround: Manually call applyManualKeyframeTrack for TRANSLATION_X, TRANSLATION_Y, and ROTATION at the desired time — but this requires knowing the current playhead position, which is also not exposed in the Plugin API (a sep

I would like to use the private NPM registry feature but before I do I have two quick questions:Is the auth token provided in Resources → npm registry → “View Configuration” generated per-user, as in is it specific to me or is it the same for all admins? Can I cycle or regenerate that token if necessary? If so, how?Thank you! 

Hi everyone,I’m testing the new Figma Motion feature and everything feels very intuitive so far, but I’m running into an issue with video playback.The Motion animation itself works correctly, but any video used inside the animated frame stays frozen on its first frame. This happens both in the Motion preview and in the exported MP4.At first, I thought the issue might be related to using the video as a background fill. However, I also tried placing the video as its own separate layer/object inside the frame, and the result is the same: the video still does not play. It remains frozen on the first frame.So the issue does not seem to be related to the video being used as a background. It seems more like Figma Motion is treating video fills/video layers as static images.What I have checked so far:The video is inside the animated frame. The video was tested both as a background fill and as a separate layer/object. The Motion keyframes work correctly. The issue happens both in the Motion pre

It worked completely fine before last release. It’s disrupting my workflow tremendously. Is that expected? or is it a bug?

I need to update my payment details because the “Ship To” and “Bill To” addresses on the receipt must be the same.However, when I tried to use the same Visa card, Figma informed me that the card had been declined.I may have entered the wrong expiration date several times while trying to recall it. In my bank’s app, I could see that Figma had attempted to place a pre-authorization hold, but the bank declined it because the expiration date was incorrect.I later found my physical card and entered the correct expiration date, but Figma still showed that the card had been declined. I contacted my bank manager, who confirmed that the bank had not received any further payment or authorization requests from Figma after that.Could you please check whether there may be an issue or restriction on Figma’s side that is preventing the card from being processed?

I accidentally moved my package.json file while organizing imported images, due to some images glitching back outside the folder. I worked too fast, and moved the package.json into the folder instead.Since then, my preview has been broken and the AI cannot fix the error by itself.Duplicating the Project only recreates the same situation, and the rollback to another version is equally impossible, as I simply get a “unable to restore version”. Another possible solution, which is to open the project with preview disabled and then try to roll back, produced the same results.  Is there a feature for this? Or does it have to be handled by support? I already opened a case, but it appears this takes quite a while.

I have a component (Select Field) that is appearing correctly in the library, however when designers at my org bring it over into their files via the asset panel, it shows up without the actual field- just the title and supporting text. When inspecting the layers, the field layers are not present in the component.Beyond that, when a user pastes in the component directly from the library file, Figma prompts them with an update that incorrectly removes the layers again.Does anyone know what is happening? I have never seen this one before and have no idea how to go about fixing it.

Hello! I have been trying to be a big advocate for Slots at our organization, and I have been enjoying the flexibility they bring. That said, there are some interaction aspects of Slots that are making the overall experience of using Figma worse. These seem like a Bug.The one I want to point out there is “selecting other elements becomes harder when a Slot is in place”. When trying to select layers on a totally different frame or section, if there is a Slot in a component “under” those layers on a different frame, dragging a box out selects both groups of items, which doesn’t make any sense to me.If you take that same scenario and detach the component, the problem no longer exists. This seems like an inconsistency with how Slots are architected in Figma, or something. Really frustrating!The recording below perfectly demonstrates this issue.

 I can not see a <Annotate for agent> button on any new created Figma make.

Was the copy link to selection action removed?

I am creating a personal hub where tiles link to various places related to my workflow. Some of these tiles link to Figma files, but Figma Make’s AI agent won’t let me paste Figma URLs in the chat box. I had to bypass it by breaking the URL with specific characters while asking the Figma Make agent to remove those specific characters (Example: giving the agent https://www.figmddda.com/design/WIM and telling it to remove the ‘ddd’). A better solution is Figma just allows us to paste in Figma links then add a dialogue explaining situations where pasting Figma frames would be better - because my situation needs the Figma URL, not a frame.

When importing SVGs stop converting <circle> tags into <path> tags.Please stop. It breaks my workflows.Please please overhaul your SVG engine. It is so buggy and broken.

The description of changes that is added in the library when publishing is no longer showing in the design files when reviewing updates. The post here mentions the function 🔗.I’m using the desktop app on Mac. Enterprise plan. I followed all steps from the Quick fixes on troubleshooting checklist.I’m not sure if the feature changed or it’s a bug since the new UI, because I noticed that the help article doesn’t mention the description. 

Just got the UI update for Figma’s Desktop client, and Assets tab is now in a completely seperate tab from File. I used to be able to tell at a glance whether there’re updates pending. Now I need to manually click on the Assets tab every. single. time. just to look out for that blue dot.It’s important for me to work with updated components. Lots of projects, lots of libraries.Feels liek a backward change. Like XD.How can I see the blue dot the moment I open a design file?  Or, how can I roll back to the previous UI? 

Apparently, I’m running an online contest and I relied on Figma Motion as the on-screen graphic. Now the way the animation works is that I tend to use preset animations (e.g. opacity, position). For example, a simple text would have an entrance and an exit animation, consist of Opacity + Position > wait > Opacity + Position. There are two Opacity to allow smooth entrance and exit. Now everything works fine, until one day when Figma Motion started to break down. Figma Motion only accept one opacity per element, according to my testing, and only if the animation start at 0s then it will work fine. Delaying the animation will result to the element being exposed before its initial animation. I will also attach a “before everything crashes” video and a “testing crashed” video. I appreciate your attention, and to hope this issue will be fixed asap.

I seem to be getting a weird behaviour when prototyping with components. Noodling a component sometimes refuses to connect up unless using the interactions side menu . Any ideas on what might be causing this?

I think there may be a bug with the horizontal constraints.When I apply the Top and Left constraints, the vertical constraints work as expected. However, the horizontal constraints do not.More specifically, it seems that the Left and Right constraints are reversed: When I select the Right constraint, the element actually behaves as if the Left constraint were applied. The left edge remains fixed, while the right edge moves. Conversely, when I select the Left constraint, it behaves as if the Right constraint were applied. In other words, the horizontal constraint behavior appears to be inverted.Could you please verify whether this is a known issue or a bug in the software?