Split PBR Maps

Here's the whole trick of Split PBR Maps: it takes in the five PBR maps - basecolor, normal, height, roughness, metallic - and returns exactly the same five maps. That's it. The "split" is a pass-through. If you looked at the source and thought "that's a return statement," you'd be right.

So why does it exist? Routing. The generate nodes already expose all five maps as separate outputs, but the graph doesn't always let you use them conveniently. This node gives you a clean, named breakout point wherever you need one - pull a single map out of the middle of a chain, fork one map off to an upscaler while the rest go straight to save, or reorganize a graph where the maps got tangled. It's plumbing, and plumbing is allowed to be boring.

When you actually need it

Honest take: if your Generate PBR (Text) or Generate PBR (Image) node is sitting right there on the canvas, you don't need this - just wire its outputs directly. It earns its place in two situations:

1. You've combined maps into a preview grid (PBR Preview Grid) or run them through some other node and now want individual maps back out for separate processing.
2. You want a stable place to fork routing - e.g., send normal to one consumer and basecolor to another without redrawing wires through the whole graph.

Inputs and outputs

Five IMAGE inputs in: basecolor, normal, height, roughness, metallic. Five IMAGE outputs out, with the same names. Wire each output where the corresponding map needs to go.

There's nothing to configure and nothing to break - no parameters, no compute, no model load. The only way it fails is if you wire the wrong map into the wrong slot, and the names make that hard to do. If you're about to spend real time here, you're probably overcomplicating your graph.

Install

It's part of the pack, so install the whole thing: ComfyUI Manager → search "StableMaterials", or clone https://github.com/P5ina/comfyui-stable-materials into custom_nodes and pip install -r requirements.txt, then restart. It'll be waiting under the StableMaterials/utils category.

This is the sort of node that looks pointless until the day it saves you from untangling a messy graph - and then you're glad it's there. It's the utility player of the pack: never the star, always available, zero drama.