Skip to main content
Javiera Villarroel
New Member
July 28, 2026
Solved

When I open an overlay, all animations play. How can I stop it?

  • July 28, 2026
  • 4 replies
  • 144 views

Hello! 
I am somewhat new designing stuff in Figma, and I have an issue with some animations.

I animated a velocimeter in the Motion section to play just when clicking on it, but every time I open an overlay on the same page it triggers the animation to start all over again. I don’t really know how to stop it, and need some help because I couldn’t find any info about this issue.

Best answer by adamsmasher

Hi ​@Javiera Villarroel and ​@Greg Szriftgiser! Just wanted to let both of you know that we released a fix for the overlay issue specifically. Let me know if you have any other issues with it, and thank you both again for your patience while our team worked on this!

4 replies

djv
Figmate
Community Support
July 31, 2026

Hi ​@Javiera Villarroel, thanks for reaching out! 

I completely understand how this must be affecting your workflow. From what you've described, it sounds like opening an overlay elsewhere on the page is re-triggering the velocimeter animation rather than just leaving it alone. That shouldn't happen if the animation is only meant to fire on its own click interaction. A few things that'd help us pin down what's going on:

  1. Is the velocimeter animation set up as a component with a Motion timeline, or as an on-click prototype interaction (or both layered together)?
  2. Does the overlay you're opening live on the same frame as the velocimeter, or a different one?
  3. Does this happen every time you open any overlay on that page, or only a specific one?
  4. Would you be able to share a screen recording? That'll let us see the exact setup and try to reproduce it on our end.

One thing worth trying: check whether the velocimeter's animation is nested inside the same frame as the overlay trigger. If so, try moving the overlay trigger to a separate frame/component so it's not sharing a timeline context with the animation. It's not guaranteed to fix it, but it's a useful data point either way. We'll continue troubleshooting together as soon as we hear back from you!

Greg Szriftgiser
New Member
August 22, 2026

Hello, I'm having a similar issue.

I have a fading animation track placed on a toast notification using Motion:
 

The fading animation track created on the Toast Notification component instance.

This Toast component instance is placed at the root of the Screen frame the toast is appearing on.

Elsewhere on this screen, and inside another frame “Content” for that screen (i.e. different parent frame than the Toast Notification), I have a button that triggers an overlay menu when clicked. This button is actually part of another Component Instance:
 

Here is the hierarchy of that screen: selected are the Button triggering the overlay, and the Toast Notification featuring the Motion fade animation.

When I play the prototype and click on the Button instance to open the overlay, the Toast Notification reappears, plays its animation again. This motion animation is configured to NOT loop. It's triggered without any interactions aside from arriving on that screen from the previous one. It's not nested in the same frame as the button.
Any ideas?
 

adamsmasher
Figmate
Figmate
August 22, 2026

Hey, ​@Greg Szriftgiser! Thanks for your post and for using Motion. That’s definitely not ideal that your animation loops when using an overlay.

 

Good news - our team is aware of this and is working on a fix regarding Motion timelines replaying when viewing a prototype with an overlay, so that should be resolved soon. I’ll keep an eye on this on our end and update here again once the fix has been released. In the meantime, let me us know if you have any other questions!

adamsmasher
Figmate
Figmate
September 9, 2026

Hi ​@Javiera Villarroel and ​@Greg Szriftgiser! Just wanted to let both of you know that we released a fix for the overlay issue specifically. Let me know if you have any other issues with it, and thank you both again for your patience while our team worked on this!