2🐕Do not retain brightness

The name on this one is doing the explaining for you, and it's worth taking literally. Most color-transfer techniques quietly protect the brightness (luminance) of the image being changed - they'll happily shift hue and saturation toward a reference, but they lock the original's exposure in place so you don't accidentally blow out a dark scene just because your reference photo was shot in bright sun. That's a sensible default, and it's presumably what the rest of ergouzi's color-migration nodes do. Do not retain brightness is the deliberate exception: it lets the target's brightness move too, so a bright, high-key source can genuinely brighten a dark target, not just recolor it.

That makes it the node to reach for when a color mismatch between two images is really an exposure mismatch, not just a tint mismatch - matching a subject shot in flat, dim lighting to a background plate shot in daylight, for instance, where nudging hue alone won't be enough to make the two halves of a composite look like they were lit the same way.

Inputs and output

Same shape as the pack's other migration nodes: source_image (supplies the color and brightness target) and target_image (what gets changed), both required, no strength dial - this is a direct migration, not a blended adjustment. Output is result_image.

Installing it

Through ComfyUI Manager, search "Comfyui-ergouzi-Nodes" and install. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/11dogzi/Comfyui-ergouzi-Nodes.git

Restart ComfyUI afterward. No model downloads - this is pixel-level math, loads instantly. And the usual note for this whole pack: the English repo you're installing from is the frozen branch; the author's active work continues on a separate Chinese-first sibling repo, so treat this as stable rather than current.

Common issues & troubleshooting

Because brightness is explicitly not protected here, this is the one node in the color-migration family most likely to blow out highlights or crush shadows if your source and target start at very different exposures - that's the intended behavior, not a bug, but it means you should check the result for clipping before you build further steps on top of it. If you wanted the color match without the exposure risk, that's exactly the gap the pack's other migration nodes (Regular, Saturation, Hue) are built to fill - any of them will leave brightness alone in a way this one deliberately doesn't.

If the shift feels too aggressive and there's no strength input to soften it, the practical workaround is compositing the result back over the original at partial opacity with a standard image-blend node, rather than expecting this node itself to meet you halfway.