Composite Basic

Heads up before anything else: this isn't a compositor. It doesn't take two images and blend them. What it does is build a settings object - blend mode, mask handling, opacity - that you eventually feed into WJNodes' actual image-blend node (named ImageCompositeMask_adv in this node's own description, and not itself part of this batch of articles). Composite_Basic is the simplest and most commonly-needed of ten sibling "options" nodes in this pack, each of which configures one slice of that compositor's behavior - canvas, coordinates, scaling, masking, batching, and so on - and all of which chain together the same way.

That chaining is the thing to understand once, because it applies to every node in this family. Each options node has an optional Options input and an output of the exact same type. Plug one into the next, and you're accumulating settings across several nodes instead of setting everything on one giant node with fifty widgets. It's a builder pattern, expressed as a chain of ComfyUI nodes instead of a fluent API. The one wrinkle worth flagging up front: the wire type connecting all of these nodes is itself called Composite_Basic - the same name as this specific node. So you'll see "Composite_Basic" both as a node you drag into your graph and as the socket color every option node in the family speaks. Confusing for about five minutes, then it clicks.

What this particular node sets

• blend_mode - the standard Photoshop-style list: normal, multiply, screen, overlay, darken, lighten, color_dodge, color_burn, hard_light, soft_light, difference, exclusion. If you've used any layer-based image editor, these behave the way you'd expect.
• mask_mode - normal, multiply, or screen: how the blend mask itself gets applied, separate from how the two images blend.
• opacity (default 1, range -1 to 1) - blend strength. Per the node's own description, going negative doesn't just reduce opacity toward zero and stop - it inverts the surface color and applies opacity, which is a genuinely different effect from just turning the strength down. Worth trying deliberately rather than assuming it's a dead zone below 0.

Where it fits in the chain

• Options (optional) - an existing Composite_Basic-typed chain from an earlier options node, if you're extending one rather than starting fresh.
• Composite_Basic (output) - the updated chain, ready to feed into the next options node or into the compositor's own Options input.

Most graphs start here: Composite_Basic sets the three settings everyone needs, and you only add the other nine option nodes (Composite_Coordinate, Composite_Scale, Composite_Canvas_adv, Composite_Mask, Composite_Batch, Composite_Application_pro, Composite_Global_adv, Composite_Merge_pro, Composite_Other) when you actually need that specific control.

Installing it

Via ComfyUI Manager: search ComfyUI-WJNodes, install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/807502278/ComfyUI-WJNodes.git
cd ComfyUI-WJNodes
pip install -r requirements.txt

No model downloads or unusual dependencies for this family - it's pure settings logic.

Common issues & troubleshooting

The blend doesn't seem to happen at all. Remember this node only produces settings - it never touches an image. If nothing visibly changed, check that the final Composite_Basic chain actually reaches the compositor node's Options input, and that the compositor itself has your two images wired in.

Settings from an earlier node in the chain seem to vanish. Every option node in this family can override what came before it on the fields it controls - that's by design, since later nodes are meant to refine earlier ones. If something you set upstream isn't showing up, check whether a downstream node in the same chain also touches that field.

README doesn't mention any of this. Correctly noticed - WJNodes' README documents the image, mask, batch, color, video, and path tooling in detail but says nothing about the ImageBlend/Composite family. Everything here comes from each node's own in-graph description rather than the project docs, so if behavior doesn't match what you expect, trust what the node shows you at runtime over any assumption carried in from a different compositor.