Rendering in Blender from the Command Line: Still Frames and Animation

Blender’s command line lets you render scenes without the graphical interface, run jobs on a remote machine, and organize production steps with scripts. This guide is based on the command-line and animation workflows in Blender’s official documentation. The command-line arguments documentation is identified as Blender 5.2 LTS. Options are processed in the order they appear, so settings such as the scene, output path, and format must come before -f or -a, which start rendering.

1. Set up a still render and output file

First, specify the path to the .blend file and where you want renders saved. -b runs Blender in background mode, so the interface doesn’t open. Use -f followed by the frame number to render. This example renders frame 10:

blender -b file.blend -f 10

Set the output location with -o and the file format with -F. The example below saves the file’s second-to-last frame in OpenEXR format to /project/renders. -f -2 selects the second-to-last frame, not the last one.

blender -b file.blend -o /project/renders/frame_##### -F OPEN_EXR -f -2

The # characters in the filename determine the number of digits used for the frame number; for example, five characters create a five-digit field. Prefixing the output path with // makes it relative to the .blend file. OPEN_EXR is among the formats available if Blender was built with support for it; the documentation notes that it may not be available on every system. Other formats listed in the documentation include PNG, JPEG, TIFF, and HDR.

Pay attention to capitalization: -F sets the output format, while -f renders a frame. Because command-line options are case-sensitive, swapping them changes how the command behaves.

2. Render an animation with a frame range, engine, and threads

Use -a to render an animation. -s sets the starting frame, -e the ending frame, and -t the number of threads to use. The command below renders frames 10 through 500 using two threads and saves PNG files to a renders path relative to the .blend file:

blender -b file.blend -s 10 -e 500 -t 2 -o //renders/frame_##### -F PNG -a

To select a specific scene, use -S followed by the scene name; to select a render engine, use -E. -E help displays the available render engines. For -t, you can specify a value from 1–1024; setting it to 0 uses the system’s processor count. -j sets how many frames to advance after each rendered frame.

Because Blender processes arguments in order, set options such as the output path and format before the option that starts rendering. The documentation recommends placing -f and -a at the end of the command. To set the Cycles device, add the relevant option after a double dash; the documentation’s example uses OPTIX. The listed device options are CPU, CUDA, OPTIX, HIP, ONEAPI, and METAL.

blender -b file.blend -f 20 -- --cycles-device OPTIX

3. Use an image sequence for long animations

Blender typically saves animation frames as separate image files. The official manual recommends the image-sequence approach when the total render time is an hour or longer. Saving frames in still-image formats such as PNG preserves completed files if rendering is interrupted. The documentation also recommends turning off the Overwrite option when restarting a job to avoid overwriting existing frames.

Before rendering, check the image dimensions, pixel aspect ratio, frame range, and frame rate in the Format panel, and the output path and file format in the Output panel. Save Output must be enabled for Blender to write frames automatically from the Output panel. If it’s disabled, you need to configure a File Output node in the Compositor to save the frames. Once rendering is complete, check the files in the output folder.

An image sequence also offers flexibility for projects that need color and lighting adjustments, masking, compositing, or preparation for different output formats later on. You can add and edit the frames in the Video Sequencer, use an audio strip, and then output a video. The manual also notes that the Video Sequencer doesn’t support multilayer EXR files.

4. Adapt the workflow for architecture and visualization

For architectural animation, rendering individual test frames first and then rendering the approved frame range creates a more structured production workflow. Use -f for specific frames and -s and -e for the animation range. The command-line arguments also include options for specifying a list of frames and a range. Numbering output filenames with # makes it easier to track the image sequence.

Background mode lets you run renders through a remote shell; the documentation gives an example of running without an X server on Linux. However, using the command line alone doesn’t mean renders will be faster. You can limit the number of threads with -t; for Cycles, you can also select one of the devices listed in the documentation. If other work will be running on the workstation while rendering, consider the impact on CPU and memory usage.

Common mistakes

• Treating -f -2 as the last frame: it selects the second-to-last frame.

• Confusing -f with -F or changing the capitalization.

• Placing the output path or format after -a or -f; argument order matters.

• Assuming frames will be saved automatically from the Output panel when Save Output is disabled.

• Rendering a long job to a single video file: separate image frames preserve completed work after an interruption and make it easier to resume production.