Skip to main content
Question

Figma motion feedback - export quality and other

  • July 10, 2026
  • 3 replies
  • 39 views

Cristiane

Hi

I have just used Figma motion for a quick animation and in general it works ok, but I have noticed a few things:

  • Gif export is low quality even it’s set to High. Grey colours show pixelated. I tried to export it at 2x and resizing the file. It does help with image quality but it obviously increases the file size which is the reason for exporting as gif in the first place.
  • Trying to scale or rotate a layer automatically creates a keyframe when I don’t want to, this doesn’t happen with position. 
  • I can’t keyframe component properties, it would be really helpful

In all, it’s a great addition to figma. However, I have experienced some glitches on the desktop app, I hope having all of this stuff added doesn’t affect overall performance. It seems to improve when I quit the app and restart again. 

 

Thank you.

3 replies

adamsmasher
Figmate
  • Figmate
  • July 10, 2026

Hey, ​@Cristiane! Thanks so much for your feedback on Motion. Seems like you gave it a pretty decent test drive!

 

Let’s address each of your points individually:

  • Gif export is low quality even it’s set to High.
    • The quality setting doesn’t actually apply to the GIF export (hence why when switching to GIF you don’t see the option shown), and GIFs by their nature can sometimes look like that at smaller sizes, particularly depending on how many colors and gradients there are in the source. Having said that, I’m going to check with the team for more info on what is expected here. Could you provide a screenshot of what you are animating on the canvas, and what it looks like as a GIF? I’ll share that with the team.
  • Trying to scale or rotate a layer automatically creates a keyframe when I don’t want to, this doesn’t happen with position. 
    • Do you have auto-keyframe enabled? This option is right next to the play button over to the left of the Motion panel. With this enabled, I was able to move to different points in the timeline and rotate/scale and it automatically created a keyframe for me.
  • I can’t keyframe component properties.
    • Which properties did you want to keyframe? I did a quick test with the opacity property and was able to create keyframes for it (this is with the auto-keyframe option enabled). 
  • Overall performance
    • Could you provide a bit more info on what you were seeing that improved after restarting the app?

Thanks!


Cristiane
  • Author
  • New Member
  • July 13, 2026

Hi, thanks for the reply

  • for the gif, I have experience using After Effects and Photoshop to create animated gifs, and I know the settings that would cause this kind of pixelated effect in Photoshop. No gradients have been used, they are all flat colours. Gif is attached.
  • For the scale and rotate, no, the auto-keyframe feature is turned off. I did try it again this morning after turning on everything, and it did the same thing again, only scale and rotation, position doesn’t create any keyframe
  • There’s a screenshot of a button component where I was trying to change the State property, but no keyframe available
  • For the performance, it was lagging a bit, a bit unresponsive. Also when clicking on a layer, then trying to click on its immediate child layer, it still selects the whole layer, this is something that happened before a while ago, the trick is to click on the canvas and try to select child layer directly. Restarting the app seems to always fix it. 

I can get around basically everything, but the colour quality could be an issue for me using figma motion, that would be my priority please. Thanks for your help.


adamsmasher
Figmate

Thanks for answering my questions, ​@Cristiane! My turn to follow up on your replies. :)

 

  • Export Quality.
    • Our team is looking into this! Thank you again for reporting it.
  • No keyframes created for the Position property when they are for scale and rotate.
    • Thanks for clarifying this! Hmm… I did a test specifically with the position of a layer and it did create keyframes for me. Here’s how I did it (in case it’s different than your own steps):
      • Turned on auto-keyframe.
      • In the Motion timeline, I moved the playhead forward to the ending frame for the animation.
      • I clicked and dragged the layer to a new position.
      • This resulted in a keyframe being created for position at the beginning of the timeline, and at the location where I had dragged the playhead.
  • No keyframe created for changing a component state property.
    • This is expected, but hopefully this is something we can support - our team is definitely aware of this.
  • Performance concerns.
    • Ok! Let me know if you are still seeing lagging and unresponsiveness - I’ll create a ticket for you with our Technical Quality team so they can help you with that. I don’t want you to have to keep restarting the app.