Use animated images, video and Lottie
These instructions are reviewed against the app source. Final-installer walkthroughs are still pending. Check platform availability and requirements before installing. Windows is an updates list, outside the 1,000 beta places.
Import media into your project so local previews and portable copies can use the registered files. Start with a small file you have permission to use.
Import and preview
- Open Assets, choose the media section and use Upload media.
- Choose a supported file and wait for validation to finish.
- Select the containing frame, then insert the asset from its thumbnail.
- Select the inserted layer. In Design, set its dimensions, fit and available playback options.
- Open the page Preview to test playback, pause and controls.
- Check the narrower breakpoints. Media geometry and supported playback settings can have local overrides.
The design canvas keeps media paused for editing. A still image there does not mean the imported animation is broken. Autoplay does not enable sound and respects reduced-motion preferences.
Supported inputs and practical limits
| Input | What to expect |
|---|---|
| JPEG, PNG, SVG | Local image assets; editable SVG geometry uses the separate vector import workflow |
| GIF, animated WebP, APNG | Animation preserved for web output; the file controls image looping |
| MP4 | Validated H.264/AVC video, with optional AAC audio |
| WebM | Validated VP8/VP9 video, with optional Opus/Vorbis audio |
Lottie JSON or .lottie | Supported shapes, solids, embedded raster images and precompositions |
An extension alone does not guarantee a supported codec. MODO rejects unsupported files instead of silently treating them as a different format.
Lottie expressions, external resources, audio/video layers and live text are not supported by the accepted subset. Convert text to paths in the source animation. Multi-animation .lottie files use the initial or first animation; their state machines and themes are not imported.
Native output
Generated iOS and Android apps include native players for supported local media. The first native build can need downloads for its dependencies.
WebM export to iOS additionally needs a local FFmpeg installation with the required H.264 encoder. MODO prepares an MP4 copy for iOS; the original stays in the project. Animated images have export limits for frame count and decoded size. An export error should be resolved before treating the output as complete.
These runtimes have been tested on simulators. Check the exact output on your intended devices before distribution.
See text, images and fonts, vector tools and native delivery.
Need a correction? Tell us