Blender Output Paths for Multiple Cameras (2026): Path Templates, Frame Numbers and Split Renders
Blender 5.0 added path templates to the render output path and the compositor’s File Output node. Write variables in braces, such as //renders/{scene_name}/{camera_name}/{blend_name}_####.exr, and Blender substitutes the scene, render camera and file name at render time. For a sequence split across GPUs, turn off Overwrite and turn on Placeholders so instances skip frames that already exist.
- Template: {blend_name}, {scene_name}, {camera_name}, {resolution_x}, {fps}.
- Frames: #### in the path becomes the zero-padded frame number.
- Cameras: bind cameras to markers or render each camera as its own job.
- Split renders: Overwrite off + Placeholders on.
Multi-camera projects tend to fail at the last step: renders from different cameras land in one folder and overwrite each other, or frames from parallel jobs collide. Blender 5 path templates fix most of this inside the output path itself.
This guide covers path template variables, frame numbering, how to switch cameras across a timeline or across jobs, and the two output options that let several Blender instances share one sequence safely.
Checked against the Blender Manual (File Paths, Output Properties, Markers, Command Line Rendering), November 2026.
1. Path templates in Blender 5
Path templates substitute expressions written in braces when the path is used. The Manual’s example turns //my_render_dir/{blend_name}.png into //my_render_dir/dance.png for a file named dance.blend. Templates currently work in the render output path in Scene properties and in the compositor’s File Output node (Blender Manual: File Paths). The field keeps the template; substitution happens while rendering.
One template in the output path replaces three hand-edited paths. The table lists every variable the Manual documents for render output paths and File Output nodes.
Path template variables
Variables the Manual lists for render output paths and File Output nodes.
| Variable | Resolves to | Typical use |
|---|---|---|
| {blend_name} | Name of the open .blend without extension | Version in the file name, e.g. shot010_v03 |
| {blend_dir} | Folder of the open .blend | Keep renders next to the project |
| {scene_name} | Current scene name | One folder per shot when shots are scenes |
| {camera_name} | Current render camera | One folder per camera |
| {resolution_x} / {resolution_y} | Render size including resolution scale | Separate preview and final renders |
| {fps} | Scene frame rate (numeric, supports format specifiers) | Delivery naming |
| {node_name} | Name of the File Output node | Pass outputs from the compositor |
2. Frame numbers and padding
In the output path, # characters are replaced by the frame number, padded with zeros to the number of # signs (Blender Manual: Output Properties). Use enough padding for the longest shot, for example #### for up to 9999 frames, so files sort correctly in compositing software. Numeric template variables such as {fps} also accept format specifiers, like {fps:###}.
File browsers and compositing apps sort names character by character, so without padding frame 10 lands between frame 1 and frame 2. Zero-padded numbers have the same length and sort in frame order.
3. Switching cameras
Two common ways to render several cameras:
- One timeline: bind cameras to timeline markers so the active camera switches at each marker (Blender Manual: Markers). With {camera_name} in the path, each segment writes to its own folder.
- One job per camera: render the same frame range once per camera, for example from the command line with a different camera each time (Blender Manual: Command Line Rendering). This suits multiple GPUs, since each instance can take one camera.
Because the camera changes at each marker, a single animation render produces three camera folders, and each segment can be checked or re-rendered on its own.
4. Several instances on one sequence: Overwrite and Placeholders
The Output panel has Overwrite and Placeholders. With Overwrite off, Blender skips frames whose files already exist; with Placeholders on, it creates an empty file for a frame when it starts rendering it (Blender Manual: Output Properties). Together, several Blender instances can render the same range into the same folder without rendering a frame twice. After the run, check for zero-byte placeholder files left by a stopped instance and re-render those frames. For the full one-Blender-per-GPU setup, see multi-GPU rendering in Cycles.
The placeholder is what stops two instances rendering the same frame, and it is also why a stopped instance leaves an empty file behind. Our guide to checking a rendered sequence finds those files automatically.
An output checklist before a multi-camera render
- Template: output path uses {camera_name} and {blend_name}; field is not red
- Padding: enough # for the longest shot
- Cameras: markers bound, or one job per camera planned
- Parallel: Overwrite off and Placeholders on when instances share a range
- Format: EXR or PNG chosen per delivery; one format per sequence
- After: zero-byte placeholders found and re-rendered
For paths, caches and other scene checks, see our 10-point Blender Cycles pre-flight checklist.
Managed farms usually set output naming for you. On an IaaS server the output path is the one in your file, so templates, padding and the Overwrite/Placeholders options behave exactly as on your workstation.
Rendering several cameras on an iRender server
- Upload the project folder to iRender Drive before you start the server; uploading is free and does not use rental time.
- Start a server with RTX 5090 (32 GB) or RTX 4090 (24 GB) GPUs and connect by remote desktop.
- Start one Blender per GPU, one camera or frame range each, with Overwrite off and Placeholders on.
- Check for empty frames, download the folders and shut down; multi-GPU servers are billed per minute.
Frequently asked questions
1. How do I put the camera name in the Blender output path?
In Blender 5.0 and later, use the {camera_name} template variable in the output path, for example //renders/{camera_name}/frame_####.png.
2. Which paths support templates?
The render output path in Scene properties and the output paths of the compositor’s File Output node.
3. How do I render several cameras in one animation?
Bind cameras to timeline markers so the active camera changes at each marker, or render one job per camera.
4. How can two Blender instances render the same sequence?
Turn off Overwrite and turn on Placeholders. Each instance skips frames that already have a file.
5. Why did my animation render fail with a path error?
A broken template, such as a missing closing brace, marks the field red and stops an animation render. Fix the template or escape braces with {{ and }}.
Render your Blender 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. You install Blender once; your server image is saved between sessions, so Blender and your add-ons stay installed.
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 Blender on it:
Two Blender runs we recorded on our servers: 120 frames at 1080p on 4x RTX 5090 at 72 seconds per frame, and the same 4K scene on 4x RTX 5090 and 4x RTX 4090 at 87 and 108 seconds per frame per GPU:
New users get a 100% bonus on the first top-up (minimum $50). See plans on the Blender render farm page or download the iRender GPU app.




