Checking a Rendered Blender Sequence (2026): Missing, Empty and Black Frames Before Delivery
After a Blender animation renders, check three things before delivery: every frame in the range exists, no file is zero bytes (a placeholder left by a stopped instance), and no frame is far smaller than its neighbours, which often means a black or partial frame. A short Python script finds all three; then play the sequence as an image strip to catch flicker and noise.
- Missing: compare files with the frame range.
- Empty: zero-byte placeholders from stopped instances.
- Black: size outliers, then a visual check.
- Playback: load as an image strip in the Video Sequencer.
Long renders rarely fail all at once. More often one frame is missing, one is an empty placeholder, or one came out black, and nobody notices until the edit.
This guide gives a quick order of checks for a finished Blender sequence, a small Python script that finds missing, empty and suspiciously small frames, and how to re-render only what is broken.
Checked against the Blender Manual (Output Properties, Command Line Rendering, Image Strips), November 2026.
1. Why frames go missing in parallel renders
When several Blender instances share a sequence with Overwrite off and Placeholders on, each instance creates an empty file for a frame when it starts and skips frames that already exist (Blender Manual: Output Properties). If an instance stops mid-frame, its empty placeholder stays, and the others skip it. A crash, a full disk or memory running out on a heavy frame can also leave gaps or partial frames.
2. A script to find missing, empty and small frames
This script uses only the Python standard library, so it runs with any Python 3, including the one bundled with Blender. Pass the folder, frame range, file prefix and extension; it assumes four-digit padding.
Size alone does not prove a frame is broken; a frame of a black title card is small too. Treat the third list as frames to look at, not frames to delete.
What to check after a sequence finishes
Fast checks first, visual checks last.
| Check | How | Fix |
|---|---|---|
| Every frame exists | Script or file list against the frame range | Re-render the missing range only |
| No zero-byte files | Sort by size, or the script below | Delete placeholders, then re-render those frames |
| No black or partial frames | Size outliers, then look at those frames | Re-render; check memory and logs for that frame |
| Correct padding and names | Frame numbers sort in order | Fix # padding or template in the output path |
| Smooth playback | Load as an image strip and play | Check noise, flicker and boundaries between instances |
3. Re-rendering only what is broken
Delete the zero-byte files, then render just the missing frames from the command line with -s, -e and -a, or single frames with -f (Blender Manual: Command Line Rendering). With Overwrite off, a full-range render also fills only the gaps. See the full list of options in the command line arguments reference.
Here is what the range command does to a sequence with gaps. Blender walks through every frame in the range, but with Overwrite off it only renders the frames that have no file yet.
Because only the gaps are rendered, the second pass costs only the time of those frames, and the frames that were already correct are left untouched.
4. Visual check: play it back
Load the sequence as an image strip in the Video Sequencer (Blender Manual: Image Strips) or in your editing software and play it. Look for flicker in noise or denoising, frames that jump in lighting or motion blur at the boundaries between instances, and wrong cameras or passes. Related guides: denoising Cycles animation and output paths for multiple cameras.
A sequence check before delivery
- Count: every frame in the range exists
- Empty: zero-byte placeholders removed and re-rendered
- Outliers: frames under half the median size viewed
- Names: padding and file names sort in frame order
- Playback: sequence played as an image strip
- Backup: checked frames downloaded before the machine is reused
Before rendering, use our 10-point Blender Cycles pre-flight checklist to avoid most of these problems.
Both farm models deliver frames you should check. On an IaaS server you can run the script and play the sequence on the server itself, and re-render gaps before you shut it down.
Checking a sequence on an iRender server
- Render the sequence one Blender per GPU into the project output folder.
- Run the check script on the server and view any outliers.
- Re-render missing or empty frames from the command line.
- Download the checked frames from iRender Drive and shut down; multi-GPU servers are billed per minute.
Frequently asked questions
1. How do I find missing frames in a Blender render?
Compare the files in the output folder with the frame range. The Python script in this guide lists missing frames, zero-byte files and size outliers.
2. Why are there empty files in my render folder?
With Placeholders on, Blender creates an empty file when it starts a frame. If that instance stopped, the empty file remains.
3. How do I re-render only some frames?
Use the command line with -s and -e for a range and -a to render it, or -f for a single frame.
4. How can I tell if a frame is black without opening every file?
Look for frames much smaller than their neighbours, then view only those.
5. Should I check the sequence before downloading?
Yes. Re-rendering gaps on the same machine is quicker than finding them later in the edit.
Render your Blender projects on iRender
iRender is an IaaS GPU render farm: you rent a bare-metal server with 1, 2, 4 or 8 NVIDIA RTX 4090 (24 GB) or RTX 5090 (32 GB) GPUs, an AMD Ryzen™ Threadripper™ PRO CPU, 256 GB ECC RAM and a 2 TB NVMe SSD, connect by remote desktop and work on it like your own workstation, with full administrator access. You install Blender once; your server image is saved between sessions, so Blender and your add-ons stay installed.
Multi-GPU servers are billed per minute (1-GPU servers have a one-hour minimum), and sessions of 3 hours or more get 10% off. Our 4-GPU and 8-GPU servers are liquid-cooled; in our own measurements the GPUs hold 60–70°C under sustained render load. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.
This quick start shows how to start a server and render Blender on it:
Two Blender runs we recorded on our servers: 120 frames at 1080p on 4x RTX 5090 at 72 seconds per frame, and the same 4K scene on 4x RTX 5090 and 4x RTX 4090 at 87 and 108 seconds per frame per GPU:
New users get a 100% bonus on the first top-up (minimum $50). See plans on the Blender render farm page or download the iRender GPU app.




