Skip to main content
Question

Figma Motion: Opacity only allows one blocks

  • July 8, 2026
  • 5 replies
  • 27 views

Loc Nguyen

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.

5 replies

Loc Nguyen
  • Author
  • New Member
  • July 9, 2026

Another test that I’ve conducted, using both textbox with “test”, one was using Opacity keyframe, while the other was using preset Opacity. Have a look.


Celyn_L
Figmate
  • Figmate
  • July 9, 2026

Hi ​@Loc Nguyen, Celyn from the Figma Community Support team here.

Thanks for taking the time to write this up and for including the videos. I understand that you're using Figma Motion for a live online contest, and that animations which previously worked are now behaving differently.

From what you've described, it sounds like elements with multiple opacity animations are no longer animating correctly, and delaying the first opacity animation causes the element to appear before it's meant to.

I've gone ahead and created a support ticket for you so the team can take a closer look. Your ticket number is #2005904.

When you have a chance, please reply directly to the ticket with:

  • A link to the impacted Figma file, and invite support-share@figma.com with Can View access. This won't affect your billing and will help the team reproduce the issue more effectively.

Thanks again for reporting this. I know this is especially time-sensitive given your contest, the team will investigate this further through your support ticket and will be in touch shortly.


Loc Nguyen
  • Author
  • New Member
  • July 9, 2026

Hi ​@Loc Nguyen, Celyn from the Figma Community Support team here.

Thanks for taking the time to write this up and for including the videos. I understand that you're using Figma Motion for a live online contest, and that animations which previously worked are now behaving differently.

From what you've described, it sounds like elements with multiple opacity animations are no longer animating correctly, and delaying the first opacity animation causes the element to appear before it's meant to.

I've gone ahead and created a support ticket for you so the team can take a closer look. Your ticket number is #2005904.

When you have a chance, please reply directly to the ticket with:

  • A link to the impacted Figma file, and invite support-share@figma.com with Can View access. This won't affect your billing and will help the team reproduce the issue more effectively.

Thanks again for reporting this. I know this is especially time-sensitive given your contest, the team will investigate this further through your support ticket and will be in touch shortly.

Hi, appreciate for the notice! I had invited you to the file!


Celyn_L
Figmate
  • Figmate
  • July 9, 2026

Thanks for the update ​@Loc Nguyen!

When you have a chance, could you also reply to your support ticket with the URL to the file? That will help the team locate it more easily 🙏


Loc Nguyen
  • Author
  • New Member
  • July 9, 2026

Thanks for the update ​@Loc Nguyen!

When you have a chance, could you also reply to your support ticket with the URL to the file? That will help the team locate it more easily 🙏

Hi again, here’s the link: https://www.figma.com/design/yzuja2nbBgrAW4hsnIYg2E/Kisiovision-2027?node-id=64-164&t=OMkXTBoTAKclTpxj-1