emotesize

Lottie inspector

Preview a Lottie, see what makes it heavy, and catch the After Effects features that break on Android, iOS or the web before your users do.

Drop a Lottie .json or .lottie to inspect it

Shows what makes it heavy and what may break on Android, iOS or the web. Nothing is uploaded.

What the inspector checks

FeatureWeb (lottie-web)Android / iOS
ExpressionsSupportedIgnored: bake to keyframes
Layer effectsA few (fill, tint, some blurs)Mostly ignored
Layer stylesMostly ignoredIgnored
Blend modesSupported in SVGIgnored or limited
Merge pathsSupportedAndroid: opt-in flag. iOS: supported, slower
3D layers and camerasPartialLittle or none
Text layers without glyphsNeeds web fontsNeeds font files in the app
External imagesServed next to the JSONBundled, e.g. setImageAssetsFolder

Support changes between player versions. Treat this as a list of things to test, not a verdict. See Lottie not working on Android or iOS for fixes.

Questions

Why does my Lottie look different on Android or iOS?

Each platform has its own renderer, and each supports a different subset of After Effects. Expressions, most effects, layer styles, blend modes and 3D layers are the usual culprits. The inspector flags each one it finds.

Does lottie-android support expressions?

No. lottie-android and lottie-ios ignore expressions, so those properties stop animating. Bake them into keyframes in After Effects before exporting.

Why are my merge paths missing on Android?

lottie-android only draws merge paths after you enable them with enableMergePathsForKitKatAndAbove(true), or enableMergePaths in Compose. They also cost more to render.

How much memory will my animation use?

Images use width × height × 4 bytes each once decoded, whatever their file size. The inspector adds them up. Vector layers use far less, but many track mattes and masks add offscreen buffers.

Is my file uploaded?

No. The inspector reads the file in your browser and sends nothing anywhere.