Skip to main content
bmpq1352
New Participant
September 1, 2026
Question

Figma Motion exporting problem

  • September 1, 2026
  • 10 replies
  • 293 views

When rendering motion to MP4, the resulting video has different quality and colors (it becomes darker) than what's displayed in Figma.

For the simplest example, I took a PNG and added keyframes at the beginning and end that don't change anything. Then, in the export, I selected MP4, high quality, and 30 fps. (It shows the file should be approximately 23 MB.)

After rendering, the MP4 file is saved as a 300 KB file with poor quality. This happened recently; everything was fine before.

 

How can I fix this?

Thanks

10 replies

Gayani_S
Figmate
Community Support
September 2, 2026

Hey ​@bmpq1352, thanks for reaching out!
The file size difference actually makes sense here. The number you see before exporting is just an estimate based on target bitrate, and it can be off by a lot depending on the content. Since your test animation doesn't actually change between keyframes, the export ends up compressing much more efficiently than that estimate expects. A smaller file doesn't automatically mean lower quality, those are separate things, and it's really the quality and color shift I want to dig into with you.
A few other people have told us their exported video looks different in quality or color than what they see in Figma Motion. We're aware of this and looking into it.

To help narrow this down, can you tell me what operating system and browser (or Figma desktop app version) you're using to export?

In the meantime, here's our guide on Export animations from Figma if you want to double-check your Format, Size, Frame rate, and Quality settings. Figma Motion is still in open beta, so we're still refining things like export quality.

Thanks for your patience and let me know what you find!

bmpq1352
bmpq1352Author
New Participant
September 2, 2026

Thanks for answer!

I use Windows 10 (22H2) and latest current app version - (126.8.16), same problem in web version -Chrome 145.0.7632.110.

 

I think the export problem started after I tried to use this plugin - Motion Export with Alpha

 

Thanks for help!

ksn
Figmate
Community Support
September 2, 2026

Hey ​@bmpq1352 - thanks very much for the follow-up. Stepping in for Gayani to give some additional info.

As Gayani mentioned, Motion is still in beta. You mentioned the issue started after using the Motion Export with Alpha plugin. Using a beta feature alongside a third-party plugin increases the chance of compatibility issues, which is likely what's causing the unexpected behavior here.

Since this is a third-party plugin, I'd recommend reaching out to its creator for support — their contact information should be listed on the plugin page. They'll be better equipped to troubleshoot issues specific to the plugin itself, and they may find something that can help you. However, I do have to emphasize again that Motion is in beta, and there is no guarantee on future compatibility with this plugin.

Thank you for understanding!

 

 

bmpq1352
bmpq1352Author
New Participant
September 3, 2026

Sorry, I expressed myself incorrectly. I don't use this plugin for rendering; I use Figma's native export. I meant that the problems started after I tried use it, and now Figma's export is broken.

Thanks

djv
Figmate
Community Support
September 3, 2026

Thanks for clarifying, ​@bmpq1352!

Installing or trying a plugin shouldn’t affect Figma's native export. But what you're describing lines up with two separate things we're already tracking:

  • The file size. As Gayani mentioned, that pre-export number is an estimate based on target bitrate. Your test animation barely changes between keyframes, so it compresses far below the estimate. 300 KB here is expected, not a symptom.
  • The quality and color. This one is real and our engineering team is actively working on it. We're limited by the browser's video encoder today, which shows up most as banding in dark or near-black content, and we have higher-quality export options in development.

Two things may help us narrow things down:

  1. Does the export look dark in every player, or only some? Try opening the MP4 in Windows Media Player, VLC, and a Chrome tab. If it looks correct in one and dark in others, that points to a color-tagging issue we have a fix rolling out for.
  2. Is your source PNG particularly dark or gradient-heavy? If you can share the file URL link (or a copy), we'll pass it to the team, since they prefer using real customer files to tune export quality.

Here's our Export animations from Figma guide in the meantime. Let us know, and we can continue troubleshooting this together. 

bmpq1352
bmpq1352Author
New Participant
September 3, 2026
  1. export look dark in every player, chrome and in figma.
  2. source PNG particularly dark - 

    Thanks

Jaycee Lewis
Figmate
Figmate
September 3, 2026

Hi ​@bmpq1352 👋 I opened a support ticket for this. The ID is 2111958 and the email subject line is Figma Motion — MP4 export renders darker and lower quality than canvas playback (Windows, native export). Please keep an eye on your email (and spam folder if necessary) for the email and any replies from our team. Thank you! — Jaycee

Kuba Tokarski
New Participant
September 13, 2026

Hi 👋
@Jaycee Lewis ​@djv I'm also experiencing the exact same issue with MP4 exports on macOS. An animation that exported perfectly a few weeks ago now renders drastically darker, despite using the exact same project and render settings.

I compared the media files in VLC and found a clear change in the underlying color matrix used by the encoder:

  • Old (Correct) Render: Encoded using ITU-R BT.601

  • New (Bugged) Render: Encoded using ITU-R BT.709

I'm attaching screenshots comparing the original canvas, the old vs. new renders, and the VLC codec data to help illustrate this.

Hope this helps the engineering team pinpoint the exact regression!

 


 

 

bmpq1352
bmpq1352Author
New Participant
September 16, 2026

Hi
Could you please create a separate topic with these explanations?
It seems like Support is no longer reading my thread, and they might miss your comment. 😥

Thanks