Rendering in Blender from the Command Line: A Guide to Stills and Animation

What will you learn in this guide?

You don’t always need to keep Blender’s graphical interface open to render. The command line can process a single frame or an animation range from a saved .blend file, and lets you set the output location with a command. You can also use this method to configure render options and create automation scripts.

In this guide, we’ll build a basic command, look at the difference between rendering a still and an animation, review an OpenEXR output example, and cover common argument-ordering mistakes. The guide is based on the options in Blender’s official command-line manual; it does not cover installation steps for a specific operating system.

Requirements and preparation

You’ll need a saved .blend file containing the scene to render, and a Blender installation that can be launched from the command line. The official manual does not specify a particular version number, minimum hardware requirements or user account requirements. Before using the examples, it’s a good idea to check the command options for your installed Blender version with blender --help.

In the commands, file.blend stands for an example scene file. In practice, replace it with the file’s path. Likewise, /project/renders/ is an example output directory; the location you use must exist in your working environment.

One important point: arguments are applied in the order they appear in the command. So settings such as the output location and format should come before -f or -a, which starts the render. The manual recommends placing the render-start option at the end of the command.

Step-by-step: render from the command line

1. Check the command options. Blender’s help output is one way to access the list of command-line arguments. Checking it can help confirm that Blender is available in the terminal and let you review the options.

blender --help

Review the help output to see the command options available in your installation. You can also consult Blender’s command-line arguments manual for options such as selecting the scene to render and specifying the final frame.

1. Render a single frame in background mode. -b runs Blender in the background without opening the graphical interface. The command below renders frame 10 from file.blend.

blender -b file.blend -f 10

This example does not specify an output folder or file format, so the current scene settings may be used. If the output location and format matter for your delivery, check them in the command or the scene settings. Starting a render from the command line does not change the scene’s camera, lighting or material decisions on its own; it simply runs the render via a command.

1. Render the animation range using the scene settings. -a renders the full animation using the settings saved in the .blend file.

blender -b file.blend -a

The manual also includes an example specifying the render engine, start and end frames, and thread count:

blender -b file.blend -E CYCLES -s 10 -e 500 -t 2 -a

In this example, -E CYCLES selects the Cycles engine; -s 10 sets the starting frame, -e 500 sets the ending frame, and -t 2 specifies the number of threads to use. These are example values from the manual, not necessarily the right settings for every project. Match the frame range to the intended section of your animation.

1. Add the output path and format before rendering. In the still-render example, -o sets the output name and location, while -F specifies the image format. The command below shows how to save the frame before the last frame in OpenEXR format to the example directory.

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

Here, ##### is a filename pattern that gives the frame number a five-digit field. -f -2 renders the frame before the last one. To render a different frame, put the desired frame number after -f. Uppercase -F specifies the image format, while lowercase -f renders a frame; they are not interchangeable. Command-line options are case-sensitive.

1. Consider running Blender remotely. Because Blender can run from the command line without a graphical interface, you can run a render in an environment that does not require a display session. The official manual gives examples of running without an X server on Linux and rendering from a remote shell over SSH. In this setup, the scene file must be accessible from the remote environment. The manual does not provide steps for transferring files or setting up a remote machine, so those preparations depend on your working environment.

Common mistakes

A frequent issue is placing the render-start option before the other settings. Blender processes arguments in order, so putting options such as -o and -F after -f or -a may not produce the expected result. As a safe habit, leave the option that starts the render until the end of the command.

Another mistake is confusing -f with -F. Lowercase -f starts a frame render, while uppercase -F selects the image format. Also remember that -f is used for a single frame, while -s and -e specify an animation range.

Remember to replace the example file and folder paths with the paths for your own project. A command running successfully does not guarantee that the scene looks right, so check the render and the saved files. If the format or location is not what you expected, first review how the relevant options are written and ordered.

Impact on architecture and visualization workflows

Architecture firms and visualization teams can render saved Blender scenes without keeping the interface open, or run renders on a remote machine. For a single interior or façade image, you can use -f; for an animation delivery, use -a. Setting the animation range with -s and -e lets you choose which section to process at the command level.

Key points to watch are the scene file and output path, choosing a file format suitable for delivery, and setting the thread count deliberately. The sources do not specify particular hardware requirements or render times, so don’t assume a command will run at the same speed on every computer. Access to files and the Blender installation on the remote machine are also part of a remote-rendering workflow. The sources do not provide information about licensing costs or paid account requirements.

Next steps

Start with a test render of a single frame to confirm that the file is saved to the right location and in the right format. Then adjust the start and end frames in the animation example to match your scene. Keep the argument order in mind when adding options to a command; if the result differs from what you expected, consult the output of blender --help and the official command-line manual. For more advanced automation, review the full set of command-line arguments; check the relevant manual instead of guessing at undocumented options.

Source and license

This article has been adapted into Turkish based on Blender’s official “Rendering From The Command Line” manual. The source is licensed under CC BY-SA 4.0.