Image Comparer

Side-by-side images are how you think you're comparing two generations. A hover slider that wipes from one to the other is how you actually see the difference - especially when the change is subtle sharpening or a denoise tweak that two thumbsnails side by side will never reveal. Image Comparer is Eclipse's take on the classic compare-with-slider node, and it's explicitly modeled on rgthree's Image Comparer, which the KB's panel calls the tool you want for "Image Comparer slides between two results" when you're debugging.

The workflow is: connect image_a (left) and image_b (right), hit run, and slide across the seam. Hover or click mode, whichever you prefer. It's an output node, so it runs every time - no cache weirdness to fight.

The auto-split trick

Here's the genuinely nice bit: you can skip wiring two inputs entirely. Connect a single batch to image_a and leave image_b alone, and the node compares the first two images in the batch automatically. That makes it a zero-effort A/B for the common case where you generated two variants into one batch - pass the batch, compare variants, done. (If only image_a is connected and it's a single image, it falls back to showing that one.)

The output that's easy to miss

The node has an image output that returns the side you picked as the default - set via right-click → "Default output: A/B" - and it defaults to image_b, on the reasoning that B is usually the new/result image you want flowing onward. Fall back to A if B is empty. So this isn't just a viewer; it's a visual selector. Compare two candidate results, wire the output onward, and whatever side you set as default is what the rest of the workflow consumes. That's the part people discover three weeks in and then rebuild around.

Installing

ComfyUI_Eclipse, r-vage's utility pack. Manager → search ComfyUI_Eclipse, or:

cd ComfyUI/custom_nodes
git clone https://github.com/r-vage/ComfyUI_Eclipse

Restart; it's under Eclipse → Image → Save & Preview. Standard deps; the pack targets current ComfyUI (frontend 1.51.2+ for the modern widget layer - which matters here, since this node was rewritten for the V3/Nodes 2.0 API), and its v4.0 cleanup dropped legacy RvTools_v2 nodes.

If you've already got rgthree installed, you may not need this - same job, same lineage. Where Eclipse's version earns its keep is the batch auto-split and the pipe-friendly default-output behavior, and if you're running Eclipse's ecosystem anyway, one less pack is a real argument.