Create Morph Image from Path

This one does exactly what it says, and it's worth being upfront about what it isn't: it's not an AI interpolation node like RIFE, FILM, or AMT-VFI that computes motion between frames and generates the in-betweens. Create Morph Image from Path is a straight crossfade - it takes a folder of images and fades between them in sequence, writing the result out as a GIF or APNG. Simple, cheap, and it looks like exactly what it is: a dissolve transition, not true motion interpolation.

Why you'd reach for it

It's the folder-based sibling of Create Morph Image, which does the same fade but between two image inputs you wire in directly. This version points at a directory instead - useful if you've got a batch of generations you want strung together into a slideshow-with-crossfades, say a LoRA training checkpoint comparison, a style progression, or a set of seed variations you want to flip through smoothly rather than as a hard cut. The README also lists a related Write to Morph GIF node for appending frames to an existing animation incrementally, if you're building the sequence up over time rather than pointing at a folder that's already complete.

What it needs

A path to a directory of images is the core input - per the README it also takes an optional glob pattern, the same style used elsewhere in the suite (things like *.jpg to grab just JPEGs, or **/* to pull in subdirectories too). Point it at a folder, optionally narrow down which files it picks up, and it hands back the finished animation.

Installing it

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

cd ComfyUI/custom_nodes
git clone https://github.com/WASasquatch/was-node-suite-comfyui
cd was-node-suite-comfyui
pip install -r requirements.txt

No extra download for this one specifically - it's pure image processing, no model weights involved. The suite's requirements.txt covers its needs.

Troubleshooting

Ordering matters and it isn't obvious: file globbing typically returns names in whatever order the filesystem or glob library hands them back, which isn't always the order you generated them in. If your morph looks like it's fading between the wrong pairs, check that your source filenames sort correctly (zero-padded frame numbers - 001.png, 002.png - rather than 1.png, 2.png, which sorts 1, 10, 11, 2...) before assuming the node is broken.

Beyond that, the general WAS Node Suite caveat applies here as everywhere in this pack: it's been unmaintained since the author stepped back in December 2023, so if you hit an import failure after updating ComfyUI's core, that's almost always a dependency version conflict in the suite itself rather than anything to do with this specific node - check your console output for the actual import error and, if it points at BLIP or another legacy dependency you don't use, that's the known culprit.