Guide
Long-form articles on Lottie file size, the WebP/frame-skipping pipeline, and best practices for designers and developers shipping animations to production.
Why your Lottie file is 70 MB
The structural reason designer-exported Lottie files explode in size — embedded PNG frame sequences, base64 overhead, and why traditional vector optimizers can't help.
Best practices for shipping Lottie
Concrete rules of thumb for designers (how to export from After Effects), developers (how to integrate without bloat), and product managers (when to use Lottie vs MP4 or WebM).
How the lottie-mini compressor works
A technical walkthrough of the in-browser pipeline — PNG decode, WebP re-encode via libwebp.js, frame stride, and timeline rewriting — and why it stays 100% local.
Lottie vs GIF vs MP4: which animation format should you use?
An honest comparison of Lottie, GIF, and MP4 across file size, transparency, scalability, interactivity, playback control, and browser support — with a decision table and guidance on when to use each.
How to embed Lottie in React
A practical guide to rendering Lottie animations in React with lottie-web and lottie-react — playback control, cleanup, SSR, and TypeScript notes.
dotLottie vs JSON: which Lottie format to ship
Plain .json versus the .lottie zip container — multiple animations, themes, file size, player support, and a practical workflow for choosing between them.
After Effects export settings for small Lottie files
The Bodymovin settings and composition habits that decide whether your Lottie file is 40 KB or 40 MB.
Lottie in action — 6 live demos
Six ways to use Lottie, each playing live with the code: loading spinner, success checkmark, like button, hero animation, playback control, and scroll-scrubbed morphing.