I would verify the frame range, missing numbers and interpretation rate before stretching an imported image sequence. The files do not necessarily carry the same timing assumptions as a video container. A correct first frame and filename pattern do not prove the sequence is complete.
On this page
Our recommendation
I recommend a sequence manifest containing pattern, frame range, count, rate, colour and alpha information. Verify those fields on import and preserve the original files until the rendered deliverable passes.
Check identity and completeness
Keep the original sequence folder intact and separate unrelated images. Confirm a consistent naming pattern and the first and last intended numbers. Count the actual files and inspect gaps or duplicate versions. A range calculation gives the expected count only when every number in that range exists exactly once.
FFmpeg’s image-sequence documentation exposes options such as input frame rate and start number, illustrating that these are interpretation choices. Check the corresponding supported controls in the application you use. Avoid relying on a default rate that differs from the render specification.
Calculate and inspect duration
For a constant-rate sequence, expected duration is frame count divided by frames per second. Compare that with the imported clip and the source render manifest. If the duration differs, establish whether the issue is missing frames, rate interpretation or an intended edit before applying a speed change.
Inspect the beginning, a moving section and the final frame after import. Check alpha, colour interpretation and ordering as separate requirements. Keep a short reference video when handing off a sequence so the recipient can compare timing and appearance without guessing.
A numbered render
Frames 1001 through 1240 inclusive imply 240 frames if none are missing. At 24 fps that is ten seconds; at 30 fps it is eight seconds. If the folder contains only 239 required files, changing the import rate does not recover the missing frame. Reconcile the range and count before editing.
Before you act
- Compare actual count with the inclusive number range.
- Set the intended interpretation rate.
- Inspect the final frame, colour and alpha separately.
Use the Frame-rate duration converter to apply the guide to your own setup.
Keep exploring
- Calculate duration at fractional frame rates without rounding away drift
- Verify a transparent video export over a contrasting background
Sources and research notes
Research checked on 21 October 2026. Product specifications are manufacturer statements; examples and buying judgements are our analysis. No hands-on product test is implied.
Build on what you just learned
Your next useful step.
Check compatibility, frame rate and compression.
OBS Hybrid MP4 or MKV? Choose for recovery and the editor you use
I would choose a recording container that tolerates an interrupted write, then test it in the actual editor.
Read the guide →H.264 vs H.265: editing cost and delivery compatibility
Choose the codec the whole workflow can handle, at an acceptable quality and file size. A smaller recording is not automatically easier to edit,…
Read the guide →
