Glim Guides · Comparison

Glim vs Lottie for AI product UIs

Honest comparison of Glim and Lottie for AI waiting states, chat companions, and ambient presence — when each wins, when to combine them.

2026-07-22 9 min read For AI product builders

Lottie is the industry default for shipping designer-made motion to the web. Glim is a companion library built around a four-state AI mind. They overlap in “something should move,” but they solve different jobs.

Quick comparison

DimensionGlimLottie
Core jobReadable AI presence (idle/thinking/talking/listening)Play vector animations from After Effects / tools
State modelBuilt-in four-state mind + themesYou invent state → animation mapping
AuthoringPick a creature + APIDesign / export JSON, then integrate
DependenciesZero (single glim.js)Player runtime + asset files
Best forAI latency, copilots, agent UIsBrand motion, onboarding, empty states

When Lottie is the right call

Lottie is excellent at performance of a designed clip. It is not opinionated about what “thinking” means in your product.

When Glim is the right call

Glim’s API is deliberately small: mount, setState, say, react, setTheme, destroy. That is the surface area AI product builders actually wire to streams and tool calls.

Can you use both?

Yes. A common pattern:

  1. Glim for the always-on companion beside chat or an agent panel.
  2. Lottie for rare ceremonial moments (first success, plan complete).

Do not stack both in the same 40×40 corner. One composition, one job.

Bottom line

Choose Lottie when the artifact is an animation file. Choose Glim when the artifact is a mind users can read while the model works. For AI products, the mind usually matters more than the clip.

Try Glim free. Offline starter + MIT creatures. No fake checkout.