
A Blender Shader AOV requires three connected decisions: declare the custom pass, write the intended material information into that named pass, and read its output in the Compositor. Merely adding a pass name does not establish that the material supplies useful values.
Key Takeaways
- Match the declared pass name and material AOV Output name.
- Use Value for one number and Color for color or vector information.
- Judge the auxiliary output separately from the beauty image.
Specify what the extra image must contain
Suppose a product animation needs an authored material signal for a later finishing adjustment. Write down what a bright pixel should mean before building nodes. This is a proposed production example, not a tested material setup.
A Shader AOV differs from selecting a region in a finished photograph. It creates additional per-pixel information during rendering. If the source is only a flattened exported movie, this guide does not reconstruct the missing material data.
Connect the declaration, writer and reader
The official Render Passes documentation describes creating the pass in Shader AOV, writing it with a material's AOV Output node, and reading it from Render Layers in the Compositor. Use the same name at the declaration and writer; avoid names that conflict with enabled passes.
For diagnosis, inspect one deliberately simple material contribution before extending the setup across the scene. Record the view layer, material and pass name. A correct-looking Combined image is insufficient evidence that this separate channel contains the expected signal.
Choose a data contract before grading
| Intended information | Documented AOV type |
|---|---|
| One scalar per pixel | Value |
| Color, normal or another vector | Color |
Do not substitute a color-selection mask merely because it resembles the desired result. The color-selection guide describes a different operation on existing image colors.
Inspect the result before making it a dependency
Review several representative frames and both affected and unaffected surfaces. Confirm that the auxiliary image follows the intended material signal rather than an accidental name collision. Only then connect the finishing operation that consumes it.
A normal or custom scalar is not automatically a valid depth map. The depth-edge guide explains why a downstream spatial effect also needs its own interpretation check. Acceptance here is a correctly authored auxiliary channel, not proof that every later composite is correct.
Related tasks
- ComfyUI Mask Editor: Choosing Between Simple HSL and LAB Color Select
- Fix a Lightroom Lens Blur Edge Before Increasing Blur
Sources and scope
- Blender Manual: Render Passes: Shader AOV declaration, AOV Output writer, Render Layers reader; shared nonconflicting name; Color stores vectors and Value one number.
Based on official Blender manual text retrieved through search-index results on October 23, 2026; direct HTTP 200 retrieval and hands-on application testing were not established. Version-specific controls must be checked against the installed release.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Mak Cézar / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.