I usually render my animation into image sequence format, It usually takes a lot of time, so I turn off my monitor and come back later to check the rendered result then find that blender crashed before rendering all the frames.

Since rendering can be done from the command prompt I thought about writing a script (running in my OS) to automatically restart rendering from the last successful rendered frame until all frames are finished*.

But I believe this problem is facing a lot of people out there, is there a way to deal with it? instead of reinventing the wheel?

  • for example if the total render time is 8 hours I don't want come back to check my computer every 20 minutes (some times this is not available I'm asleep or away from my PC)
  • 1
    $\begingroup$ It might be overkill, but perhaps this is something like what you are looking for $\endgroup$
    – gandalf3
    Commented Nov 13, 2015 at 21:51
  • $\begingroup$ yeah it's an overkill, but you highlighted a good place to begin searching from, thank you :) $\endgroup$
    – Ahmed Ali
    Commented Nov 14, 2015 at 11:20

4 Answers 4


Blender actually can do this already; if you disable Overwrite in Render settings > Output, Blender will skip rendering frames where the output file already exists.

See Does Blender resume rendering after returning from hibernation in Windows 7?

On linux you could write a short shell script to restart the render in case of a crash, e.g.

#!/usr/bin/env bash
while true; do
    blender $@ # $@ contains all the arguments passed to the shell script

Save it in a file (e.g. persistent_blender.sh), give it execute permissions and run it like so:

./persistent_blender.sh -b '/path/to/file.blend' -a

Where the arguments tell blender to render the animation of the specified file.

Of course you could make something much nicer and handle all sorts of things (such as stopping when all the output files exist and have a size > 0).

  • $\begingroup$ this is not what I meant, I need a script to restart rendering automatically instead of checking my computer every short period of time. for example if the total render time is 8 hours I don't want come back to check my computer every 20 minutes (some times this is not available I'm asleep or away from my PC) $\endgroup$
    – Ahmed Ali
    Commented Nov 13, 2015 at 21:08
  • $\begingroup$ @AhmedAli You could write a simple loop which simply runs blender repeatedly until all the frames are rendered. $\endgroup$
    – gandalf3
    Commented Nov 13, 2015 at 21:27
  • $\begingroup$ I agree, I'm Just checking if somebody out there has already done this. $\endgroup$
    – Ahmed Ali
    Commented Nov 13, 2015 at 21:36
  • 7
    $\begingroup$ Why is blender crashing in the first place? $\endgroup$
    – user1853
    Commented Nov 13, 2015 at 21:36
  • $\begingroup$ Yes, why is Blender crashing? I render to image files almost 24 hours a day. Blender has never crashed doing this in 200 days. Windows has crashed, but not Blender. (2.72, 2.73 & 2.76,on W7 and W10, 20Gb RAM.) Do you know that it was just Blender that crashed & not the O/S? $\endgroup$ Commented Nov 18, 2015 at 13:31

I would write an Autohotkey watchdog script for that. Save this code as watchdog.ahk or smth.

  1. Uncheck overwrite images,
  2. open Blender file,
  3. then run this script, it will show the popup,
  4. start initial rendering manually and go to sleep =)

It'll restart Blender if it crashes, open the same file, and send ctrl-f12 again. /repeat/

TIMER = 5000
WinWaitActive, ahk_class GHOST_WindowClass
WinGetTitle, title, A
file := RegExReplace(title, ".*\[(.*)\]$", "$1")
if file=
    msgbox, CANNOT GET FILENAME FROM TITLE: "%title%"
TrayTip, blender, % "Now watching for " file
    IfWinNotExist, %title% ahk_class GHOST_WindowClass
        IfWinExist, ahk_exe blender.exe
            goto next
        TrayTip, blender, % "Restarting " file
        Run, C:\Program Files\Blender Foundation\blender\blender.exe %file%
        WinWaitActive, ahk_class GHOST_WindowClass
        Sleep, 2000
        Send, ^{f12}
    Sleep TIMER

PS: Pressing Shift-0 closes the script and removes it from Tray.

  • $\begingroup$ Worth mentioning this is for windows OS only. $\endgroup$
    – batFINGER
    Commented Jan 25, 2020 at 16:49

Here is an example of how this may be achieved using python (version 3.6+).

The script runs Blender in a loop until all files are rendered. If blender crashes the missing file is rerendered. If Blender freezes a timeout restarts the process (I limit render time in Blender by setting Render Properties|Render|Time Limit).

The example is for mac. On windows and linux you need to make sure that path to Blender install folder is stored in the PATH variable.


import os
import subprocess
from glob import glob

class Data:

def main():

    data = Data()
    data.start_frame = 1
    data.end_frame = 250
    data.blender_path = "/Applications/Blender.app/Contents/MacOS/Blender"
    # data.blender_path = "blender" # on windows and linux
    data.project_path = "path_to_project/example.blend"
    data.out_path = "path_to_output_folder"
    data.next_frame = 1
    data.render_timeout_seconds = 120

    state = "INIT"

    while True:

        if state == "INIT":
            state = "CHECK_OUTPUT"

        if state == "CHECK_OUTPUT":
            if are_files_rendered(data):
                state = "DONE"        
                state = "RUN_BLENDER"

        if state == "RUN_BLENDER":
            state = "CHECK_OUTPUT"

        if state == "DONE":

def are_files_rendered(data):

    expected_files = set([f"{frame:04}.png" for frame in range(data.start_frame, data.end_frame + 1)])
    existing_files = set([os.path.basename(path) for path in glob(data.out_path+"[0-9][0-9][0-9][0-9].png")])
    missing_files = sorted(list(expected_files - existing_files))
    if missing_files == []:
        return True
    def file_name_to_frame_number(file):
        return int(file.split(".")[0])

    data.next_frame = file_name_to_frame_number(missing_files[0])

    return False

def start_blender(data):

    command = f"{data.blender_path} -b {data.project_path} -o {data.out_path}#### -f {data.next_frame}"

        subprocess.run(command, shell=True, timeout=data.render_timeout_seconds)
    except subprocess.TimeoutExpired:

  • $\begingroup$ Hey there, seems to be a life saver... BUT massive n00bness hinders me: I copy/pasted this into a txt file, renamed it to .py, installed Python and altered the path to Blender: $\endgroup$ Commented Feb 27 at 8:22
  • $\begingroup$ C:\Program Files\Blender Foundation\Blender 3.6\blender-launcher.exe Running it just does something for a second or so, then it closes. Nothing happens. Rrender timeout is set to 120 s, a frame in 50% res takes close to 5 minutes per frame to even start rendering,- do I need to set this to something like "400" to even work? And the frame start/end frame also needs to be set according to the projects, correct? $\endgroup$ Commented Feb 27 at 8:29
  • $\begingroup$ Render Properties|Render|Time Limit - is that referring to Blender offline rendering, i.e. command line? Sorry, never tried this. $\endgroup$ Commented Feb 27 at 8:35
  • $\begingroup$ I set the time limit in the Bender project file to 100s (the option is available only when using Cycles). There are other options, like Max samples, but I wanted the render to finish overnight, so I set a time limit. In addition, I added a time limit on the Python subprocess that runs Blender from the command line because sometimes the render process hangs. $\endgroup$ Commented Feb 28 at 16:10
  • $\begingroup$ According to this the path to Blender perhaps needs to be changed to: C:\Program Files\Blender Foundation\Blender 3.6\blender.exe. The Python script should print out the command that runs Blender. You can copy, paste, and run it directly from the command line to see if it works. $\endgroup$ Commented Feb 28 at 16:48

I encountered the same rendering crashes and resolved them by creating a small Java tool which monitors blender and restarts it externally if the blender process disappears. As the problem seems to be quite widespread, I decided to provide the tool as freeware. You can get it here:


I also made the observation that - all other things being the same - blender crashes much less frequently when rendering from the command line instead of in the user interface. So if you are rendering with Ctrl-F12, I would recommend to first try switching to command line rendering with

blender -b scene.blend -a

If that does not solve the problem already, you might use Blender Tender to get blender restarted externally and not loose any time or sleep with overnight renders.

As for the question of why it is crashing: As it is much more stable without the user interface, this hints at some rare synchronisation problems between render engine and UI/preview window.


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .