Upscale Model Switch

This is plumbing, not a filter - and that's exactly why it's useful. Upscale Model Switch takes two upscale models and a boolean, and hands back whichever one the boolean points at. No processing happens here; it just lets you build a graph where the upscale model itself is a decision rather than something hardcoded at build time.

Why you'd want that

An "upscale model" in ComfyUI is a loaded ESRGAN-family checkpoint - something like 4x-UltraSharp or Remacri - plugged into an Upscale Image (using Model) node. These are pure pixel interpolators: they add no new content, they just make the image bigger cleanly, and different models trade off sharpness against artifacting differently depending on the source. It's common to keep two around - a fast, general-purpose one for previews and a heavier or more specialized one (a face-tuned model, say, or one better suited to painterly output) for final passes. Rather than manually rewiring which model feeds the upscale node every time you want to compare or switch, this node lets a single boolean toggle - driven by a checkpoint name check, a UI switch, or a batch parameter - pick between them automatically.

It's part of a whole family of "X Input Switch" nodes this suite ships - Model, CLIP, VAE (also covered in this pack, see VAE Input Switch), Conditioning, Image, Latent, LoRA, ControlNet Model, and more - all doing the identical boolean-pick trick for a different socket type. If you've used one, you've used them all.

How it compares to newer switch nodes

If you're coming from a workflow built around rgthree-comfy, you've probably seen its context and switch nodes, which do similar plumbing with a nicer UI and more visual feedback about which branch is active. WAS's version predates that and is plainer - just a boolean in, a value out - but it still does the job, and if you're already pulling in WAS for other utilities there's no real downside to using its switches too rather than adding another pack.

Installing it

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

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

Nothing extra to download for this node - it's pure graph logic.

Troubleshooting

The most common mistake with any of these switch nodes: forgetting that both inputs need to actually be connected for the switch to have something to hand back, even the branch you're not currently using. If a run fails complaining about a missing input on the "off" side, that's why.

Otherwise this node is about as low-risk as WAS Node Suite gets - it's not the kind of node likely to break from an unmaintained dependency, since it touches no external library. If your whole WAS install fails to import after a ComfyUI update, that's a suite-wide dependency conflict (the pack's been unmaintained since December 2023), not anything specific to this switch.