Blender Cycles Render Passes, Multilayer EXR and Cryptomatte (2026): A Compositing Setup That Survives Changes
Cycles can split each frame into light, data and matte passes that you combine in compositing. Saved as OpenEXR MultiLayer, every frame keeps all its passes in one file, so a grade or a matte change does not need a re-render. Cryptomatte gives anti-aliased mattes picked by object, material or asset.
- Enable: View Layer Properties › Passes: only the passes you will use.
- Save: Output Properties › File Format: OpenEXR MultiLayer.
- Mattes: Cryptomatte Object, Material or Asset, picked later with the Cryptomatte node.
- Memory: each pass adds a buffer; Denoising Data adds memory and render time.
Rendering only the beauty image means every client note sends you back to the render queue. Render passes split the same frame into lighting components, data and mattes, so many changes can be made in compositing instead, in seconds rather than hours.
This guide covers which Cycles passes to enable, how the light passes add back up to the beauty, how Cryptomatte works, and how to save everything to multilayer EXR without filling the GPU. For compositing workflows in Blender, see compositing an animation in Blender.
Checked against the Blender Manual (View Layer Passes, Output Properties, Cryptomatte node), November 2026.
1. Which passes Cycles can render
Passes are enabled per view layer under View Layer Properties › Passes. The Manual groups them into Data, Light, Cryptomatte, Shader AOV and Light Groups (Blender Manual: Passes). A few details matter in production: the Depth, Position, Object Index and Material Index passes are not anti-aliased; the Vector pass is disabled when Motion Blur is enabled; and Denoising Data includes Denoising Albedo, Denoising Normal and the combined image before denoising, for use with the Denoise node.
Which Cycles passes to enable, and what for
Grouped as in View Layer Properties › Passes; descriptions follow the Blender Manual.
| Group | Passes | Typical use |
|---|---|---|
| Data | Combined, Depth, Mist, Position, Normal, Vector, UV | Depth and Mist for fog and depth effects; Vector for Vector Blur when motion blur is off |
| Light | Diffuse, Glossy, Transmission (Direct, Indirect, Color), Volume, Emission, Environment, Ambient Occlusion, Shadow Catcher | Grade lighting per component and rebuild the beauty |
| Cryptomatte | Object, Material, Asset, with Levels | Anti-aliased mattes picked in compositing |
| Shader AOV | Color or Value outputs you define in materials | Custom masks and utility data |
| Light Groups | One limited Combined pass per group of lights | Relight in compositing without re-rendering |
| Denoising Data | Denoising Albedo, Denoising Normal, noisy Combined | Denoise later with the Denoise node |
2. How the light passes rebuild the beauty
Diffuse, Glossy and Transmission each come as Direct, Indirect and Color passes. The Manual’s diagram shows how they combine: Direct plus Indirect, multiplied by Color, for each component, then added together with Emission, Environment and the other light passes to give Combined. Once that sum matches the beauty, you can grade each part on its own: lift the indirect bounce, tint the reflections, or tone down an emission.
3. Cryptomatte: mattes without Object IDs
The Manual describes Cryptomatte as a standard for creating mattes in compositing. Cycles can output Object, Material and Asset Cryptomatte passes; Levels sets how many objects can be distinguished per pixel. Unlike Object and Material Index passes, the objects to isolate are chosen in compositing, and the mattes are anti-aliased and take motion blur and transparency into account. It can also be used in other compositing software that supports Cryptomatte.
In Blender, add a Cryptomatte node, pick the objects in the viewer, and use its Matte output as the mask (Blender Manual: Cryptomatte node).
4. Saving to OpenEXR MultiLayer
Set Output Properties › File Format to OpenEXR MultiLayer. The Manual describes it as saving the rendered view layers and their passes to a multi-layer OpenEXR image (Blender Manual: Output Properties). Each frame becomes one file holding every pass, which keeps image sequences tidy and lets another compositing application read the same layers.
Keep the frame number in the file name with # characters, and render into a folder inside the project, so the sequence lands in the same place on any machine. Plan disk space: a multilayer EXR with many passes is far larger than a PNG of the beauty.
With separate images, a 20-pass shot becomes 20 folders that all have to stay in sync. A multilayer EXR keeps every pass of a frame together, so a missing or re-rendered frame is one file.
5. Passes and GPU memory
Every enabled pass is another full-resolution buffer. On a heavy scene close to the card’s limit, a long list of passes can be what tips a frame into system memory. The Manual notes that the Denoising Data passes increase memory usage and render time and should only be enabled when denoising in the compositor is required. If memory is tight, lower the Tile Size, since tiles are cached to disk; our guide to Cycles GPU memory covers the other options.
Geometry and textures stay the same whatever passes you choose; the buffers on top grow with every pass. That is why trimming unused passes, and keeping Denoising Data off unless you denoise in the compositor, can be enough to keep a heavy frame on the GPU.
A passes checklist before a long render
- Passes: only the passes your compositing will use, enabled on every view layer that needs them
- Rebuild: light passes add up to Combined on a test frame
- Cryptomatte: Object, Material or Asset enabled, Levels high enough for overlapping objects
- Motion: Vector pass only if Motion Blur is off
- Output: OpenEXR MultiLayer, #### in the file name, folder inside the project
- Disk: enough space for the full sequence of multilayer files
For paths, caches and other settings to check before any farm render, see our 10-point Blender Cycles pre-flight checklist.
Both farm models can render multilayer EXR. On a submission (SaaS) farm, check that the output format and passes in your .blend are kept and how large files are returned. On an IaaS server the frames are written to the server’s drive, where you can open one in the compositor before downloading the sequence.
Rendering passes 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.
- Render one frame to multilayer EXR and check the passes and Cryptomatte in the compositor.
- Render the sequence, download the EXRs and shut down; multi-GPU servers are billed per minute.
Frequently asked questions
1. How do I enable render passes in Blender Cycles?
In View Layer Properties › Passes, tick the Data, Light, Cryptomatte or other passes you need. They are set per view layer.
2. How do I save all passes in one file?
Set Output Properties › File Format to OpenEXR MultiLayer. Each frame is saved as one EXR containing every view layer and pass.
3. What is Cryptomatte in Blender?
A pass type for creating anti-aliased mattes in compositing. You pick objects, materials or assets with the Cryptomatte node instead of assigning index numbers before rendering.
4. Why is my Vector pass missing?
The Blender Manual notes that the Vector pass is disabled when Motion Blur is enabled in the render settings.
5. Do render passes use more GPU memory?
Yes. Each pass is another buffer, and the Manual notes that Denoising Data increases memory use and render time.
6. Can I use Blender Cryptomatte in other compositing software?
Yes. The Manual says Cryptomatte can be used with other compositing software that supports it.
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.




