November 3, 2026 Linh Nguyen

Checking a Rendered Blender Sequence (2026): Missing, Empty and Black Frames Before Delivery

Quick answerHow to check a rendered sequence
Checked Nov 2026

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.

iRender
Three problems a sequence check should catch
Schematic
0001ok0002ok0003ok0004missing0005ok00060 bytes0007ok0008tiny file0009ok0010okshot010_####.exr after a parallel renderMissing: an instance stopped or skipped the frame0 bytes: placeholder left when an instance stoppedMuch smaller than its neighbours: black or partial frame, check visuallyMissing, empty and unusually small frames are the three things to checkBlender Manual: Output Properties (Placeholders)
okmissing0 bytessize outlier
Schematic example

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.

iRender
check_sequence.py: find broken frames
Python 3
1# check_sequence.py: list missing, empty and unusually small frames
2# usage: python check_sequence.py folder start end [prefix] [ext]
3# example: python check_sequence.py D:\renders 1 240 shot010_ .exr
4import os, sys, statistics
5
6folder, start, end = sys.argv[1], int(sys.argv[2]), int(sys.argv[3])
7prefix = sys.argv[4] if len(sys.argv) > 4 else ""
8ext = sys.argv[5] if len(sys.argv) > 5 else ".exr"
9
10sizes, missing, empty = {}, [], []
11for f in range(start, end + 1):
12 # file names with 4-digit padding, e.g. shot010_0001.exr
13 path = os.path.join(folder, f"{prefix}{f:04d}{ext}")
14 if not os.path.exists(path):
15 missing.append(f)
16 elif os.path.getsize(path) == 0:
17 empty.append(f)
18 else:
19 sizes[f] = os.path.getsize(path)
20
21med = statistics.median(sizes.values()) if sizes else 0
22small = [f for f, s in sizes.items() if med and s < 0.5 * med]
23print("missing:", missing)
24print("zero bytes:", empty)
25print("under half the median size, check visually:", small)
Standard library only: runs with any Python 3, including the one bundled with BlenderScript by iRender; frame naming per Blender Manual: Output Properties

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.

ChecksAny Blender version

What to check after a sequence finishes

Fast checks first, visual checks last.

CheckHowFix
Every frame existsScript or file list against the frame rangeRe-render the missing range only
No zero-byte filesSort by size, or the script belowDelete placeholders, then re-render those frames
No black or partial framesSize outliers, then look at those framesRe-render; check memory and logs for that frame
Correct padding and namesFrame numbers sort in orderFix # padding or template in the output path
Smooth playbackLoad as an image strip and playCheck noise, flicker and boundaries between instances
RuleCheck before the server or workstation moves on to the next job.

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.

iRender
Re-render a range or a single frame
Command line
1# Render frames 120 to 135 again
2blender -b shot010_v03.blend -s 120 -e 135 -a
3
4# Render a single frame
5blender -b shot010_v03.blend -f 206
Delete zero-byte placeholders first; with Overwrite off, existing frames are skippedBlender Manual: Command Line Rendering

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.

iRender
Re-render only the frames that are broken
Schematic
1. After the run120ok121ok122missing123ok1240 bytes125ok126missing127missing128ok129ok2. Delete the zero-byte files120ok121ok122missing123ok124deleted125ok126missing127missing128ok129ok3. Render the range again with Overwrite off120ok121ok122re-rendered123ok124re-rendered125ok126re-rendered127re-rendered128ok129okblender -b shot.blend -s 120 -e 129 -aWith Overwrite off, Blender skips frames that already have a file, so a full-range render fills only the gapsBlender Manual: Output Properties; Command Line Rendering
existing framemissingzero bytesre-rendered
Example frame numbers

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

  1. Count: every frame in the range exists
  2. Empty: zero-byte placeholders removed and re-rendered
  3. Outliers: frames under half the median size viewed
  4. Names: padding and file names sort in frame order
  5. Playback: sequence played as an image strip
  6. 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

iRender
Works 1:1 like your own PC: we keep your setup, you just get more GPUs
IaaS render farm
Your workstationscene.c4d · .blend · .hip1 GPUYour iRender serverscene.c4d · .blend · .hipup to 8 GPUs=same setupWindows or Ubuntu desktopYour software, in the version you chooseYour plugins and scriptsYour licensesYour scene and render settings, unchanged1 GPUGPU power: the only difference1, 2, 4 or 8 × RTX 5090 / 4090✓ Only the GPU count changes: open your scene and render the way you do at home
Same on both machinesTip: upload the full project folder with relative paths so textures are found
  1. Render the sequence one Blender per GPU into the project output folder.
  2. Run the check script on the server and view any outliers.
  3. Re-render missing or empty frames from the command line.
  4. 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.

Accelerate your production pipeline with high-performance IaaS render farm services and dedicated bare-metal workstations powered by up to 8x NVIDIA GeForce RTX 5090 (32GB GDDR7), high-frequency AMD Ryzen™ Threadripper™ PRO processors, 256GB ECC RAM, and dedicated 2TB NVMe SSD storage tailored for your pipeline:
, ,

Linh Nguyen

Linh Nguyen works in customer support at iRender, helping artists render Blender and Houdini projects on multi-GPU servers. She has written more than 300 articles for the iRender blog, covering Blender, Houdini and practical GPU rendering.
Contact

iRENDER GPU

Render Farm Pricing
Quick Start
Multi-GPU Benchmarks
iRender GPU App
Blog
Documentation
The Render Farm
The Company
Terms & Conditions

INTEGRATIONS

Autodesk Maya
Blender
Cinema 4D
Houdini
Karma XPU
Lumion
KeyShot
Unreal Engine
Twinmotion
Redshift
Octane
And many more…

iRENDER TEAM

Elite support 7 days a week
SATURDAY – SUNDAY: 6:00 AM – 11:59 PM
(UTC+7)
Hotline: (+84) 912-785-500
Skype: iRender Support
Email: [email protected]
Address 1: 68 Circular Road #02-01, 049422, Singapore.
Address 2: No.22 Thanh Cong Street, Hanoi, Vietnam.

Contact
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →