Image Blend

The plainest of WAS's blending trio, and often the one you actually want. Per the README, Image Blend "blends two images by opacity" - the straightforward crossfade: dial the mix from fully one image to fully the other, everywhere in the frame at once, no mask involved. That's what separates it from its two siblings: Image Blend by Mask does the same crossfade but lets a mask control where it happens, and Image Blending Mode swaps the simple opacity mix for Photoshop-style blend modes (multiply, screen, overlay, and the rest).

If you just need "these two images, mixed X% toward one of them, uniformly across the whole frame," this is the node - the other two exist for when you need spatial control or a specific compositing math, and reaching for them when you only needed a flat crossfade is more setup than the job requires.

How it works

Two images go in, plus how much weight to give each in the mix, and it produces a single blended output - a straight linear interpolation between the two images' pixel values. Turn the mix all the way to one side and you get that image back untouched; sit it in the middle and you get an even 50/50 fade. It's the same math behind an opacity slider in any image editor, just running per-pixel across the whole image uniformly.

What it takes and gives back

Two IMAGE inputs and an opacity control that sets how much of each contributes to the result, producing one blended IMAGE output. Both source images need matching dimensions to blend correctly - mismatched sizes are the standard failure mode for any two-image node like this, so resize first if your sources came from different generation steps.

Where it's genuinely useful

Fading between a generated result and its source (useful for controlling how strongly an effect or edit shows through), combining two style variations into a middle ground, or building a crossfade animation frame by frame by stepping the opacity value across a sequence. It's simple, and that's the appeal - not every compositing job needs a mask.

How to install it

ComfyUI Manager: search "WAS Node Suite," install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/WASasquatch/was-node-suite-comfyui

then, from inside that folder, install requirements - path/to/ComfyUI/python_embeded/python.exe -s -m pip install -r requirements.txt on portable, pip install -r requirements.txt on system Python. Restart ComfyUI; it's under WAS Suite.

Common issues & troubleshooting

The main practical snag is size mismatch - if your two source images aren't the same width and height, the blend will either error out or produce something you didn't expect, depending on how the node handles the mismatch internally. Run both through a resize node first if they came from different sources or generation settings.

Otherwise this is a lightweight image op with no external dependency, unlikely to break on its own. The pack-wide risk still applies: WAS Node Suite has had no active development since December 2023, and the recurring complaint since then is the whole suite failing to import after a ComfyUI update - a shared-dependency version clash, not this node specifically. If it happens, reinstall requirements with your embedded Python interpreter, not a system one.