velements vs Lottie

Lottie or video: which one does your animation belong in?

Lottie ships an animation as data that a player draws at runtime. We export a rendered video file. The right choice is decided almost entirely by where the animation is going to play.

When Lottie is the right answer

  • For an icon or a small interface animation on a website or in an app, Lottie is the better answer: smaller, vector-crisp and controllable from code.
  • If the animation has to react to state (a toggle, a progress value, a theme change), a runtime player is the only sensible option.
  • A design team already working in a Lottie pipeline has tooling and conventions that a video file does not fit into.

When we are

  • No video editor takes Lottie. If the animation is going on a timeline in Premiere, Resolve, Final Cut or CapCut, it has to be a video file, and that is most of what editors need.
  • Effects that players constrain or approximate (real blurs, soft shadows, complex masking, dense particle work) render exactly as drawn when the output is video.
  • Nothing has to be added to the page. A transparent WebM in a video tag needs no library, and it is still a fraction of the weight of an animated GIF doing the same job.

The short version

Going into a video edit: video, every time. Going into a web page or an app as a small interface flourish, especially one that reacts to state: Lottie. Going into a web page as decorative motion that nothing needs to control: either works, and a transparent WebM avoids shipping a player.

Ready to create?

Decide by trying it

Open a preset, put your own words and colors in it, and see whether the output belongs in your edit.