The Commandline Renderer is a dedicated executable included with your installation that allows you to render projects without launching the full Cinema 4D GUI. This is the standard method for rendering on render farms or for automating render tasks in a pipeline environment.
This guide covers the common arguments (flags) used to control the Commandline Renderer.
Common Commandline Flags
Below is a list of the most commonly used arguments to control the Commandline Renderer.
| Flag | Description & Usage |
|---|---|
-render |
Required to start a render. Renders the specified scene file using the settings saved within the file. Example:Commandline.exe -render "C:\scenes\project.c4d"
|
-take |
Renders a specific Take instead of the main scene. Example:Commandline.exe -render "C:\scenes\project.c4d" -take "Main Camera"
|
-frame |
Renders a specific frame range (start, end, step). Example:Commandline.exe -render "C:\scenes\project.c4d" -frame 100 150 1
(Renders every frame from 100 to 150) |
-oimage |
Overwrites the save path and filename for the main image. Sequential frame numbers are added automatically. Example:Commandline.exe -render "C:\scene.c4d" -oimage "D:\renders\final"
|
-omultipass |
Overwrites the save path for Multi-Pass files. Example:Commandline.exe -render "C:\scene.c4d" -omultipass "D:\renders\mp\pass"
|
-oformat |
Overwrites the output format (e.g., JPG, PNG, EXR, TIFF, PSD). Example:Commandline.exe -render "C:\scene.c4d" -oformat PNG
|
-oresolution |
Overwrites the output resolution (Width Height). Example:Commandline.exe -render "C:\scene.c4d" -oresolution 1920 1080
|
-threads |
Defines the number of CPU threads to use. Commandline.exe -render "C:\scene.c4d" -threads 0
|
-nogui |
Starts Cinema 4D without the Graphical User Interface. Highly recommended for render farms to prevent windows from opening. Example:Commandline.exe -nogui -render "C:\scene.c4d"
|
g_logfile |
Saves all console output and render progress to a text file. Example:Commandline.exe -render "C:\scene.c4d" g_logfile="C:\logs\render.txt"
|
-minimalviewport |
Starts Cinema 4D with minimal Viewport settings to save resources. Example:Commandline.exe -minimalviewport
|
Examples
Simple Render (Windows)
Renders a scene using all saved settings.
"C:\Program Files\Maxon Cinema 4D 2024\Commandline.exe" -render "C:\Projects\MyScene.c4d"Complex Batch Render (Windows)
Renders frames 0-100 of a specific Take, overrides the output path and resolution, and runs without a GUI.
"C:\Program Files\Maxon Cinema 4D 2024\Commandline.exe" -nogui -render "C:\Projects\MyScene.c4d" -take "Shot_01" -frame 0 100 1 -oimage "D:\Renders\Shot_01" -oresolution 1920 1080Mac Terminal Render
Renders a scene on macOS.
/Applications/Maxon\ Cinema\ 4D\ 2024/Cinema\ 4D.app/Contents/MacOS/Cinema\ 4D -render /Users/User/Documents/Scene.c4d
Troubleshooting Tips
Common Issues
-
Spaces in Paths: If your file path or file name contains spaces (e.g.,
Program FilesorMy Scene.c4d), you must enclose the entire path in quotation marks (""). -
Order of Flags: While order often doesn't matter, it is best practice to put
-noguiat the beginning of your command string to ensure the interface is suppressed immediately.
Need help with licensing the Commandline renderer? Check out these knowledgebase articles:
- How do I license the Commandline renderer manually?
- How to Enable Automatic Login for Cinema 4D and the Commandline Renderer
If you have further questions or encounter issues with the Commandline Renderer, please submit a support ticket.
Comments
0 comments
Article is closed for comments.