Cinema 4D and Redshift Command-Line Rendering: Batch Files, Logs and GPU Selection
Commandline.exe renders a saved scene without the interface. Check these before a batch job:
- Basics: -nogui first, then -render with the scene path; the saved scene settings are used
- Overrides: -take, -frame, -oimage, -oresolution change one run without editing the scene
- Logs: g_logfile writes progress and messages to a text file
- GPUs: -redshift-gpu picks which GPUs a Redshift job uses
- License: every machine running the Commandline renderer with Redshift GPU needs its own Redshift license
Rendering from the Cinema 4D interface is fine for one shot. For a night of renders, several shots, or splitting one server into separate jobs, the command line is simpler and more predictable: a batch file starts each job, writes a log, and moves on to the next one without anyone clicking Render.
This guide covers the Cinema 4D Commandline renderer with Redshift: the arguments that matter, ready-to-copy batch files for single jobs, smoke tests and queues, how to choose GPUs for a Redshift job, licensing, and how command-line rendering compares with the Render Queue and Team Render.
Checked against Maxon’s Cinema 4D command line documentation, the Maxon support article on Commandline arguments, Redshift Command-line Rendering and GPU Selection, and Maxon’s Redshift licensing article, November 2026.
1. What does a command-line render do?
The Commandline renderer ships in the Cinema 4D installation folder. Given a scene with -render, it renders with the render settings already saved in that scene (Maxon: Cinema 4D and the Command Line). Takes, AOVs, output paths and tokens all come from the .c4d file, and a few arguments can override them for one run.
Because everything comes from the saved file, the most common command-line surprise is rendering an older version of the scene. Save before you start a batch, and keep each job’s log: g_logfile writes the console output and render progress to a text file, and unlike the other arguments it has no leading dash (Maxon support: Commandline arguments).
2. The arguments you will use (step by step)
Settings checklist (copy or follow line by line):
Step 1: Start with -nogui and -render
Maxon’s support article recommends -nogui for render farms and placing it at the start of the command so no interface opens. Wrap any path with spaces in quotation marks.
Step 2: Set the range and take
-frame takes a start, end and step; -take renders a named take instead of the main one. For many takes, see our guide to Cinema 4D takes and tokens with Redshift.
Step 3: Add a log
Add g_logfile= with a path for each job, so a failed frame can be traced the next morning.
Step 4: Smoke-test before the full range
The overrides make quick tests cheap: render every tenth frame at half resolution into a test folder, check the frames and the log, then start the real job. The scene file is not changed.
Maxon lists -oformat (for example JPG, PNG, EXR, TIFF, PSD) and -threads as further overrides; -threads 0 uses all available CPU threads.
3. Queue several scenes in one batch file
A batch file runs its lines one after another, so a list of scenes becomes a render queue that keeps going overnight. The example below loops over three scenes and writes a log next to each one.
Each job starts only when the previous one has finished. Check the frame count in each output folder and the end of each log before you treat the night as done; our Redshift sequence QA guide lists what a finished job can still hide.
4. Choosing GPUs for a Redshift command-line job
For Redshift, -redshift-gpu followed by a device id selects a GPU, and repeating it selects several, for example -redshift-gpu 0 -redshift-gpu 1. The device ids are listed in the AllComputeDevices line of Redshift’s preferences.xml. Choices made on the command line are not saved to the preferences, so Cinema 4D opened normally keeps its own GPU selection (Maxon: Command-line Rendering and GPU Selection).
Maxon notes that selecting a subset of GPUs per job is useful for rendering several frames at once on one machine. When that helps, and how to measure it, is covered in our Redshift multi-GPU guide, which includes a two-job example for a 4-GPU server.
5. Command line, Render Queue or Team Render?
Which batch method fits the job
Based on Maxon documentation
| Method | Good for | Keep in mind |
|---|---|---|
| Commandline.exe | Unattended jobs, scripts, logs, GPU selection per job | Renders the saved scene; one license per machine for Redshift GPU |
| Render Queue | Several scenes or all takes from the interface | Renders saved scenes; Open With All Takes adds each take as a job |
| Team Render | Spreading frames across several machines on a network | Each Team Render Client node needs its own Redshift GPU license |
On licensing, Maxon’s support article is explicit: a Cinema 4D subscription includes one Redshift GPU license for the main workstation, and any extra machine running Team Render Client or the Commandline renderer needs its own Redshift license to use Redshift GPU; Redshift CPU is included with both (Maxon: Redshift licenses and render nodes). The Render Queue renders saved scenes, and its Open With All Takes and Open With Marked Takes commands add each take as a separate job (Maxon: Render Queue).
6. SaaS or IaaS render farm for batch jobs?
Which farm type fits command-line batches
Both farm types run batch renders; the difference is who writes and controls the batch.
| Situation | Usually a better fit | Why |
|---|---|---|
| Standard jobs, no custom scripts | SaaS | The farm’s submitter builds and runs the commands for you |
| Your own batch files, logs and GPU splits | IaaS | You run Commandline.exe on the machine exactly as on your workstation |
| Overnight queues of several scenes | Either | Both can queue; on IaaS the batch file is the queue |
| Studio pipeline with its own submit tools | Either | Pick the farm that supports your submit workflow |
Rule of thumb: if the batch file is part of your workflow, a machine you control runs it unchanged; if not, a submitter is less to manage.
Running a batch render on an iRender server
An iRender server is a full Windows machine, so the batch files from this guide run on it unchanged:
- Upload the project and your batch files to iRender Drive before you start a server; uploading is free and does not use rental time.
- Start a server with RTX 5090 (32 GB) or RTX 4090 (24 GB) GPUs. Cinema 4D and Redshift are pre-installed; adjust the Commandline.exe path in the batch file to the installed version.
- Run a smoke test (every tenth frame at half resolution), then start the full batch.
- Check frame counts and logs, then shut down. Multi-GPU servers bill per minute; 1-GPU servers have a one-hour minimum.
Command-line render checklist
Tick each item before you leave a batch running.
Frequently asked questions
1. How do I render a Cinema 4D scene from the command line?
Run Commandline.exe from the Cinema 4D installation folder with -nogui and -render followed by the scene path. It renders with the settings saved in the scene.
2. How do I render only some frames or one take?
Add -frame with a start, end and step, for example -frame 0 239 1, and -take with the take name. Both override the scene for that run only.
3. How do I save a log of a command-line render?
Add g_logfile= followed by a file path. It writes console output and render progress to a text file; note it has no leading dash.
4. How do I choose which GPUs Redshift uses on the command line?
Add -redshift-gpu followed by a device id, and repeat it for each GPU. The ids are in the AllComputeDevices line of Redshift’s preferences.xml.
5. Does the Commandline renderer need its own Redshift license?
For Redshift GPU, yes. Maxon states that any extra machine running the Commandline renderer or Team Render Client needs its own Redshift license; Redshift CPU is included.
6. Why did my batch render an old version of the scene?
The command line renders the saved .c4d file, not what is open in the interface. Save the scene before starting the batch.
7. Can I change the output path without editing the scene?
Yes. -oimage overrides the image path and -omultipass the Multi-Pass path; frame numbers are added automatically.
8. Can I run these batch files on an iRender server?
Yes. iRender servers are full Windows machines with Cinema 4D and Redshift pre-installed on 1, 2, 4 or 8 RTX 5090 or RTX 4090 GPUs, so Commandline.exe and batch files run as on your own workstation.
Render your Cinema 4D and Redshift 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. Your server image is saved between sessions, so your plugins and settings stay installed. Cinema 4D and Redshift are pre-installed on every server.
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 Cinema 4D and Redshift on it:
Two Redshift runs we recorded on our servers: 150 frames at 1080p on 4x RTX 5090 at 40.84 seconds per frame (about 1h 42m), and a 301-frame cloth simulation at 1080p on 1x RTX 5090 at 21.3 seconds per frame:
New users get a 100% bonus on the first top-up (minimum $50). See plans on the Cinema 4D and Redshift render farm page or download the iRender GPU app.




