Nourivex Image Route Toggle

Some workflows are built around a habit: iterate cheap, render expensive. You bang out a dozen versions with upscaling turned off because it's fast and you're only checking composition and prompt, then - once you actually like one - you flip a single thing and wait for the full-res model upscale to finish. Nourivex Image Route Toggle is that single thing, turned into a node.

What it does

It's a pure A/B switch for images, and it does nothing else. Two image inputs in, one image out, and a boolean decides which one passes through:

• image_base - your fast path, straight off the VAE decode (or a quick scale).
• image_upscaled - your slow, pretty path, after an upscale model.
• use_upscale - the switch. false (the default) passes image_base; true passes image_upscaled.

That's the entire mechanism. No type tricks, no fallback logic, no hidden rescaling - the node literally returns one of the two tensors it was handed. In the pack's own workflows the base path comes straight from VAEDecode, the upscaled path goes through the model upscaler, and this node is the last stop before the final preview, so you never rewire the graph to switch between preview and render. The README frames it exactly that way: use_upscale = false for quick preview, true for a sharper final.

The trap, and it's a real one

Both inputs are required. There's no "leave it unwired and it skips" behavior. If you're in fast-preview mode and you never built an upscale path at all, you still have to connect something to image_upscaled - even a node you've bypassed - or the graph refuses to run. It's the opposite of an rgthree Any Switch, which passes the first non-empty input and lets you leave branches hanging. This one is a strict manual A/B, so it only earns its keep if you actually maintain both paths. Beginners have a tendency to wire both inputs to the same image just to make it validate, at which point the toggle is theatre - flip it all you like, nothing changes.

Do you need it?

If you're the sort of person who runs every intermediate image through a full model upscale before looking at it, no - you'd just run the upscale always and never look back. If you iterate a lot before committing, it's a nice ergonomic win that keeps one boolean as your "render quality" knob instead of a pile of bypassed nodes. It's a preference node, honestly. What it is not is a quality tool - it adds no pixels and no detail, it only routes them.

Install

Part of the Nour_Comfy pack. Via ComfyUI Manager (search Nour_Comfy), or:

cd ComfyUI/custom_nodes
git clone https://github.com/Nourivex/Nour_Comfy

Then restart ComfyUI and hard-refresh the browser if the nodes don't show up. This is a dependency-free pack - no pip installs, no model downloads - so there's not much to get wrong.