Play uploaded frames or an external frame manifest at a chosen FPS, fit, autoplay, and loop setting while managing the much higher network and memory cost of frame-by-frame media.
Where: Select an image-sequence element → right sidebar → Media
Before you start
- Frames should use stable ordering and compatible dimensions; a manifest must resolve every listed filename from its base URL.
Key ideas
- Two frame sources: Frames can be uploaded into the project or described by an external manifest with a base URL and ordered filenames.
- Playback contract: FPS controls timing, fit controls framing, and autoplay/loop determine the default playback cycle.
- Sequence cost: Every frame is a separate image; resolution, frame count, compression, and preloading can make a sequence far heavier than encoded video.
Steps
- Prepare consistently sized, correctly ordered frames and choose uploaded frames or an external manifest.
- Insert/select the image-sequence element and add the frames or manifest base URL plus filenames.
- Set FPS, fit, autoplay, and loop, then size the element at the intended breakpoint.
- Preview the first load as well as repeated playback on desktop and a representative mobile device.
- Reduce frame dimensions/count or use encoded video when the sequence is too slow or memory intensive.
Tips
- Use zero-padded filenames so lexical and playback order match.
- Prefer the smallest dimensions and frame rate that preserve the intended visual quality.
Limitations and important notes
- A missing manifest frame can create a visible gap or failed load.
- Long, high-resolution sequences can exceed reasonable page weight and device memory.
Troubleshooting
Frames play out of order
Check the explicit manifest order or rename uploaded files with zero-padded numeric sequences before re-adding them.
Playback stutters on first view
Reduce frame weight/count, verify hosting latency, and consider encoded video when every frame does not require direct access.