Lottie vs Video for Fitness AppsFile Size, Customization and Integration

A complete exercise library
can live inside the app

The library-level measurements are approximately 91.6 MB for Lottie JSON and 15.27 MB for dotLottie, covering the 1,603 animation assets in this snapshot.

For an offline-first fitness app, that changes the options. Instead of requesting each exercise preview during a workout, the app can include the licensed files and a compatible player, then load the animations locally. Loading animations from an app bundle is an established Lottie workflow.[3]

This can be useful for workouts with unreliable connectivity, compact wearable experiences or products that want exercise previews available immediately after installation.

Video can also be stored locally or cached. Offline playback is not exclusive to Lottie. The practical advantage here is the small size of the complete VFE collection, not a special billing rule. Initial distribution, updates, the player and the rest of the application remain separate from the animation-data total.[4, 5]

VFE provides downloadable assets, not an animation-hosting or playback API. Teams can bundle the files, host them on their own server or CDN, or combine local storage with downloads as needed.

Match the brand without
remaking the animation

A technically suitable exercise library still needs to fit the product visually.

With VFE, clothing, skin, hair and background colors can be adjusted through the customization tools. The Male variation also has a Simple hairstyle option. These are practical customization features of the library, not a requirement to manually redesign every exercise.

For Lottie playback, changing the palette does not require rendering a new video.

A red-and-graphite exercise can become a muted green version for another interface while retaining the same movement. The live library makes it possible to explore those choices before integration.

In a rendered video, the character’s appearance is already encoded into the frames. Changing specific clothing or skin colors generally means editing and producing another video version. With VFE’s vector source, those colors remain editable properties.[6]

The aim is simple: the exercise should look like part of the interface, not an unrelated clip placed inside it.

One source for different screen sizes and refresh rates

Different sizes, without separate resolution exports

An exercise may appear as a small item in a workout list, a larger demonstration during a session and a compact preview on a wearable.

VFE’s vector shapes can be redrawn at those different sizes from the same animation file. Making the display larger does not require adding more pixels to the stored asset.[6]

Video can also be displayed at different sizes, and existing footage can be transcoded into smaller versions without reopening the original animation project. But a smaller video export has a fixed raster resolution. Enlarging it later does not recover detail that was removed.[7]

With a vector source, display size does not have to become another export decision.

Different refresh rates, without a separate high-FPS video

The Assisted Chin Up source used above has a 24 FPS timeline. That does not mean a compatible Lottie player must display only 24 distinct updates per second.

With frame interpolation enabled, the player can calculate intermediate values between keyframes. In lottie-web, this allows updates on each browser animation frame, which generally follows the display’s refresh rate. The same source can therefore provide intermediate motion on higher-refresh displays without a separate 60- or 120-FPS export.[8, 9]

This is a capability, not a guarantee of 120 FPS on every device. Actual smoothness still depends on the animation, player and available processing power.

The file can stay the same while the way it is displayed changes.

The production advantage:
the library already exists

Choosing a format does not create the content.

Even after deciding on video or animation, a team still needs the exercises, a consistent style, usable organization and a way to adapt the collection to the product.

VFE addresses that work with an existing library organized by variation, equipment and major muscle groups. The nine categories cover Bodyweight, Dumbbells, Barbell, Cable Machine, Gym Machines, Resistance Bands, TRX, Stretching and Foam Roller. Male and Female are separate collections with substantial overlap, rather than an assumption that every exercise exists identically in both.

This lets a team start by evaluating suitable exercises instead of planning an entire production pipeline.

It also avoids an all-or-nothing purchase. Individual Animations, Equipment Packs, Single Variation and Full Library provide different starting points. Eligible earlier payments can count toward broader coverage or a higher license tier through the Fair Upgrade Policy (FUP). Update coverage follows the purchased scope.

Keep the vector source,
use the output that fits

Purchases are delivered as Lottie JSON through the Download Center. VFE Tools can be used for customization and supported exports, including dotLottie, MP4 and transparent WebM. Other permitted conversion workflows can also be used.

That means choosing VFE does not require using a Lottie player in every part of the product.

A team might use dotLottie for an offline exercise catalog, JSON in a customizable web interface and rendered video where the existing workflow expects video.

The important distinction is that the editable vector source remains available. A particular video export becomes an output of that source, rather than the only representation of the exercise.

Where video remains
the better choice

When the purpose is to show a real coach, spoken guidance, detailed technique or the subtleties of a person’s movement, video is often the more appropriate medium.

A stylized exercise preview and an instructional recording are not interchangeable. They can serve different parts of the same experience.

Video may also be the simpler integration choice when a product already has a mature video pipeline and needs only a small number of fixed previews. The compact MP4 examples above show why that option should not be dismissed.

The useful comparison is not “vector good, video bad.” It is whether the product benefits from a reusable, customizable exercise collection, or primarily needs finished footage.

Small files still need
a suitable implementation

File size measures storage and transfer, not everything that happens during playback.

A Lottie player must interpret and render the animation. Complexity, simultaneous animations and renderer choice affect performance. Video decoding has its own trade-offs and may benefit from efficient platform support. Neither file size alone nor format choice proves lower battery consumption or memory use.[8, 10]

The sensible check is to test representative exercises on the actual target devices, including the intended number of simultaneous previews.

VFE’s sample page provides files for that evaluation, with color and character options available before purchase.

Final thought

For a fitness product, the strongest argument for VFE is not a single file-size ratio.

It is the combination: a compact library, a consistent visual style, editable colors, scalable graphics, controllable motion and a practical route to offline playback.

Video remains valuable where realism and detailed instruction matter. VFE provides a different foundation for the recurring exercise previews that appear throughout an interface.