A render pass is one component of the render that Blender saves separately so you can use it on its own. The default output is the Combined image (the full beauty render). Render passes are the other outputs you can ask Cycles to write alongside it: the diffuse light, the glossy reflections, the depth map, the object IDs, the noise estimate.
The reason to care is separation. With the pieces split out, you can lift the highlights without touching the shadows, mask one object cleanly, fade things by distance, or rebuild the lighting without re-rendering. None of that is possible from one flat image.
Open the Passes panel and you’ll see 30+ checkboxes with cryptic names. That doesn’t mean 30 things to learn. They fall into about five categories tied to specific jobs.
A single pass looks weird on its own
Open one of the non-Combined passes for the first time and you’ll often think something is broken. The Diffuse Color pass shows the material without any lighting on it. The Direct pass shows lighting without the material’s color. Each one is correct. They aren’t meant to be looked at in isolation. They’re ingredients that Cycles combined to make the beauty image.
Beauty breakdown
Many render passes are not meant to look “complete” on their own.
Diffuse passes split the surface color away from the light that hits it.
Mental model: Diffuse beauty needs Color + Direct + Indirect
Click each pass to add it to the equation. Click again to remove it.
Recombined beauty
ResultWhat the surface looks like when Color, Direct, and Indirect work together.
Why this matters
A single diffuse pass is not “the diffuse result.” Blender is giving you ingredients, not the finished beauty by default.
The naming gives you the rule:
- Color passes give you the material contribution without lighting.
- Direct passes give you first-hit lighting without the material baked in.
- Indirect passes give you bounced light only.
A flat, washed-out, or grayscale-looking pass usually isn’t broken. It’s one slice of the calculation that the Combined image already mixed together for you. Knowledge check Why can a pass look wrong on its own and still be correct? Because most passes are one ingredient in the beauty image, not a finished picture. The renderer separates the calculation into pieces so you can manipulate them in comp. A piece on its own usually looks incomplete.
Pick passes by the comp job, not by guessing
Most pass-related pain comes from turning on passes you might need. Don’t. The shorter, more useful question is: what specific job am I trying to do in comp? Pick the passes that exist for that job.
Choose the pass
The best pass depends on the job, not on what looks coolest in the Render Layers node.
Recommended passes
Cryptomatte style
Smooth edges and overlapping contributors are exactly why Cryptomatte survives real compositing better.
Why
The manual calls Cryptomatte easier to set up than Object/Material Index, usable in other compositors, and able to handle multiple objects per pixel. In Cycles it also works with transparency, motion blur, and depth of field.
Watch out
Object Index and Material Index still exist, but the manual notes they are not anti-aliased, so they are rougher masks.
A few passes to know
Depth vs Mist
Both encode distance from the camera. The difference is the range:
- Depth stores raw distance in scene units. It’s not anti-aliased and becomes noisy when the render uses depth of field or motion blur.
- Mist is already mapped into a clean
0.0to1.0range, configured via the World settings. Easier to grade for haze, atmospheric fade, or fake depth-of-field effects.
For anything visual, Mist usually wins. Use raw Depth only when you need the exact distance value.
Object Index / Material Index vs Cryptomatte
All three give you per-object or per-material masks. Cryptomatte is the modern default: easier to set up, supports multiple objects per pixel, and works through transparency, motion blur, and depth of field.
Object Index and Material Index still exist for older or constrained workflows. They’re not anti-aliased, which makes their masks rougher.
Denoising Data
Three sub-passes (Denoising Albedo, Denoising Normal, and the noisy combined image) that the Denoise compositor node uses to denoise more intelligently than working from beauty alone. Enable this whenever you plan to denoise in comp instead of at render time.
Vector
Stores motion vectors for the Vector Blur compositor node, so you can add motion blur in comp instead of at render time. Important gotcha: this pass is disabled when render-time Motion Blur is on. Pick one or the other.
Shadow Catcher
Outputs only the shadows collected by objects marked as shadow catchers, so you can multiply them onto existing footage or a plate. Not a “general shadow pass.” This is for VFX integration specifically.
Five pass categories
Read the Passes panel as five categories instead of 30+ checkboxes:
- Beauty ingredients.
Combined,Color,Direct,Indirectpasses you can recombine or rebalance. - Masks.
Cryptomatte,Object Index,Material Indexfor isolating things. - Data passes.
Depth,Mist,Position,Normal,Vectorthat drive compositor effects. - Denoising support.
Denoising Datafor theDenoisenode. - Debug passes. Sample count, ray bounces, things you only enable when troubleshooting.
If you don’t have a use for one of these categories on this shot, leave the related passes off.
Starting points
Practical defaults for common jobs:
- Comp-flexible beauty:
Combined+Denoising Data+ any pass tied to a job you know you have. Save as MultiLayer EXR. - Cleaner denoising in comp:
Denoising Data(feeds theDenoisenode). - Object or material masks:
Cryptomatte. Index passes only for constrained workflows. - Distance-driven fade or fake depth:
Mistfor visual work,Depthfor exact distance. - Motion blur in comp:
Vectorpass. Disable render-time motion blur. - CG shadows on real footage:
Shadow Catcher.
The real trap
The main mistake isn’t forgetting a pass. It’s turning on passes you don’t have a comp job for, then expecting each one to look like a finished render.
Try this in Blender
10 minTake one Cycles shot and enable only these passes:
CombinedDenoising DataMistCryptomatte Object
Then inspect each one in the Render Layers node and ask:
- Which one is a beauty image?
- Which one is really a mask or helper?
- Which one would only make sense inside the compositor?
What to remember
Render passes give you separation: instead of one finished image, you get the renderer’s intermediate calculations as separate outputs.
The useful question isn’t “which passes should I turn on by default?” It’s “what comp job am I trying to do?” Pick the passes that exist for that job, leave the rest off. Knowledge check When might raw Object Index or Material Index still be acceptable instead of Cryptomatte? When the masking job is simple and the limits don’t bite. Index passes fall short when you need soft edges, multiple objects per pixel, or reliable behavior through transparency, motion blur, or depth of field.