Why Does My Blender Product Render Need a Different Masking Workflow When I Switch From Object Index to Cryptomatte?

Identify which pass produced the existing mask

Open the Blender project or retained multilayer render and identify the render engine, Blender version, enabled View Layer passes, and the node producing the product mask.

Blender's render-pass documentation describes Object Index as a pass storing a user-defined object ID at each pixel. An ID Mask node can turn a chosen numeric identifier into a mask. The documentation also states that Object Index and Material Index passes are not antialiased.

If the product isolation was built from Object Index, record the assigned ID and the corresponding ID Mask operation. Do not assume that an object name or material name automatically determines the numeric index.

Inspect the result against the original Combined render. A jagged outline may reflect the index pass's limitations, but a missing product component may instead have a different index or be absent from the rendered scene. Those observations require different repairs.

Understand what changes with Cryptomatte

Blender 5.0 documents a Cryptomatte node that can create masks for one or more objects or materials from a Cryptomatte render pass or compatible multilayer OpenEXR source.

The documented workflow enables the appropriate Cryptomatte pass, renders the scene, adds a Cryptomatte node in the Compositor, selects the desired objects, and uses its Matte or Image output.

The modern node can select object or material identities in the compositing stage rather than requiring the same numeric Object Index workflow. Blender's documentation illustrates correct handling of motion-blurred edges in Cycles.

Do not follow a historical tutorial that requires manually connecting individual Crypto Pass sockets without checking its version. Blender distinguishes the current Cryptomatte node from the older Legacy node.

Cryptomatte is not a substitute for correct geometry or material assignment. If the product's cap and body are separate objects, an object-based selection must include the intended components. If a material-based selection includes the same material on a prop, inspect whether the matte covers unwanted scene elements.

Hypothetical rotating bottle render

Hypothetical illustration—not an executed Blender render: a fictional bottle scene contains three objects: BottleBody, BottleCap, and DisplayStand. The bottle rotates during a short product animation, and the editor wants to isolate the bottle without the stand.

The existing workflow assigns BottleBody Object Index 1, BottleCap Object Index 2, and DisplayStand Object Index 3. An ID Mask selecting only index 1 would omit the cap. Even after the desired components are accounted for, the non-antialiased index boundaries may be unsuitable for the intended composite.

The proposed Cryptomatte workflow enables object identification and selects BottleBody and BottleCap in the compositor. It excludes DisplayStand. The reviewer would compare the resulting mask around the cap seam and the rotating silhouette, including any motion-blurred frames.

The example establishes an inspection plan, not a measured improvement. The actual rendered pass must exist and the chosen engine must support the intended workflow.

Choose the mask based on the delivery requirement

Use an Object Index workflow when its numeric selection and edge characteristics meet the actual compositing requirement. Use Cryptomatte when object or material selection and antialiased boundaries provide a better fit for the rendered scene.

Before switching, verify that the needed Cryptomatte pass was enabled at render time. A beauty render without the relevant identification data cannot automatically provide a valid Cryptomatte selection merely because a node is added afterward.

Keep the Combined render and the mask output available for comparison. Check translucent components, fine handles, seams, and motion-blurred edges over contrasting backgrounds. Blender's current Cryptomatte documentation also lists limitations, including unsupported volume objects; do not assume every rendered element is selectable in the same way.

If the result is intended for another compositor, confirm that the exported multilayer file contains the required passes and metadata and that the receiving application supports them.

Finally, compare the composite with the approved product reference. A clean mask can still isolate an incorrect model. The purpose of the render pass is to control compositing, not to certify product construction or the accuracy of a generated 3D asset.

Record your own observations

The filled rows are illustrative examples. Use the blank row for your own files and observations.

Download the editable CSV worksheet

What the references establish

• Blender 5.0 Manual — Passes: Documents Object Index and Material Index data, ID Mask usage, and the non-antialiased nature of index passes.
• Blender 5.0 Manual — Cryptomatte Node: Documents object/material selection, render-pass and multilayer OpenEXR sources, Matte/Image/Pick outputs, the current node workflow, motion-blurred edge handling, and limitations.
• Blender 4.3 Manual — Cryptomatte Node: Explains the distinction from Object Index and Material Index passes, including compositing-stage selection and antialiased mattes.