October 10, 2026 Maddie Quach

Cinema 4D and Redshift Command-Line Rendering: Batch Files, Logs and GPU Selection

Batch renderingRendering Cinema 4D and Redshift from the command line
From Maxon documentation

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.

iRender
What a Cinema 4D Command-Line Render Does
Schematic
render.batone line per job(saved next to scene)Commandline.exe-nogui -renderno viewport, no GUIFrames on diskscene save pathor -oimage overrideg_logfileprogress + messagesone text file per jobScene settingstakes, AOVs, tokensall read from the .c4dCheckframe count + logbefore the next jobOverrides on the command line (-frame, -take, -oimage, -oresolution) win over the scene; everything else comes from the saved scene
rendereroutputlog
Schematic · from Maxon Cinema 4D command line documentation

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):

Settings checklist
Commandline.exe (Cinema 4D installation folder)
-nogui → first argument // no interface
-render “scene.c4d” → required; uses the saved scene settings
-take “name” → render one take instead of the main take
-frame start end step → e.g. 0 239 1
-oimage / -omultipass → override the save paths (frame numbers added)
-oresolution w h → override the resolution
g_logfile=”path” → progress and messages to a text file (no dash)
Redshift only
-redshift-gpu id → repeat per GPU; ids from AllComputeDevices in preferences.xml
Check → frame count in the output folder + end of the log

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.

iRender
Render one scene without the interface
cmd
1:: one job: frames 0-239 of the saved scene, no GUI, with a log
2"C:\Program Files\Maxon Cinema 4D 2026\Commandline.exe" -nogui -render "D:\project\shot010.c4d" -frame 0 239 1 g_logfile="D:\project\logs\shot010.txt"
Edit the Cinema 4D path, scene and rangeMaxon: Cinema 4D and the Command Line

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.

iRender
Smoke-test a sequence before the full render
cmd
1:: quick test: every 10th frame at half HD, written to a test folder
2"C:\Program Files\Maxon Cinema 4D 2026\Commandline.exe" -nogui -render "D:\project\shot010.c4d" -frame 0 239 10 -oresolution 960 540 -oimage "D:\tests\shot010" g_logfile="D:\tests\shot010_test.txt"
Overrides apply to this run only; the scene file is unchangedMaxon support: Commandline Rendering Arguments

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.

iRender
Queue several scenes in one batch file
cmd
1@echo off
2set C4D="C:\Program Files\Maxon Cinema 4D 2026\Commandline.exe"
3
4:: render several scenes one after another, one log per scene
5for %%S in ("D:\project\shot010.c4d" "D:\project\shot020.c4d" "D:\project\shot030.c4d") do (
6 echo Rendering %%~nS
7 %C4D% -nogui -render %%S g_logfile="%%~dpnS_log.txt"
8)
9echo All jobs finished
Save as render_all.bat; %%~dpnS = scene path without extensionMaxon: Cinema 4D and the Command Line

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?

CompareThree ways to batch

Which batch method fits the job

Based on Maxon documentation

MethodGood forKeep in mind
Commandline.exeUnattended jobs, scripts, logs, GPU selection per jobRenders the saved scene; one license per machine for Redshift GPU
Render QueueSeveral scenes or all takes from the interfaceRenders saved scenes; Open With All Takes adds each take as a job
Team RenderSpreading frames across several machines on a networkEach 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?

CompareNeutral guide

Which farm type fits command-line batches

Both farm types run batch renders; the difference is who writes and controls the batch.

SituationUsually a better fitWhy
Standard jobs, no custom scriptsSaaSThe farm’s submitter builds and runs the commands for you
Your own batch files, logs and GPU splitsIaaSYou run Commandline.exe on the machine exactly as on your workstation
Overnight queues of several scenesEitherBoth can queue; on IaaS the batch file is the queue
Studio pipeline with its own submit toolsEitherPick 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

iRender
How iRender works: your computer controls your own multi-GPU server
IaaS render farm
Your PC or MacNo powerful GPU neededRemote desktopLive screen1:1 like your PCYOUR OWN GPU SERVERbare-metal · not sharedGPUGPUGPUGPUGPUGPUGPUGPU1, 2, 4 or 8 × RTX 5090 (32 GB) or RTX 4090 (24 GB)Threadripper PRO · 256 GB ECC RAM · 2 TB NVMe SSDFull admin access · your setup is saved between sessions1Register, top upFirst $50+ top-up doubled2Upload your projectiRender Drive, free3Start and connectRemote desktop, any OS4Render, shut downBilling stops, per minute✓ Your workstation, just more GPUs: no queue to wait, no farm plugin, no job submission, no settings changed
Your mouse and keyboardServer screen streamed back
Schematic, not to scale

An iRender server is a full Windows machine, so the batch files from this guide run on it unchanged:

  1. Upload the project and your batch files to iRender Drive before you start a server; uploading is free and does not use rental time.
  2. 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.
  3. Run a smoke test (every tenth frame at half resolution), then start the full batch.
  4. 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.

ChecklistCommand-line render checklist
0 / 10 done
Tip: tick each item as you set up the job; the ticks reset when the page reloads.

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.

Accelerate your production pipeline with high-performance IaaS render farm services and dedicated bare-metal workstations powered by up to 8x NVIDIA GeForce RTX 5090 (32GB GDDR7), high-frequency AMD Ryzen™ Threadripper™ PRO processors, 256GB ECC RAM, and dedicated 2TB NVMe SSD storage tailored for your pipeline:
, , , , , , ,

Maddie Quach

Maddie Quach, from iRender's customer support team, has written more than 100 articles for the iRender blog on Maya, Houdini, Arnold, Karma XPU and Redshift.
Contact

iRENDER GPU

Render Farm Pricing
Quick Start
Multi-GPU Benchmarks
iRender GPU App
Blog
Documentation
The Render Farm
The Company
Terms & Conditions

INTEGRATIONS

Autodesk Maya
Blender
Cinema 4D
Houdini
Karma XPU
Lumion
KeyShot
Unreal Engine
Twinmotion
Redshift
Octane
And many more…

iRENDER TEAM

Elite support 7 days a week
SATURDAY – SUNDAY: 6:00 AM – 11:59 PM
(UTC+7)
Hotline: (+84) 912-785-500
Skype: iRender Support
Email: [email protected]
Address 1: 68 Circular Road #02-01, 049422, Singapore.
Address 2: No.22 Thanh Cong Street, Hanoi, Vietnam.

Contact
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →