Multi CLIP Switch (Creepybits)

If you've ever built a workflow where you swap between an SDXL checkpoint and a Flux one, you know the pain: different models want different CLIPs, and re-plugging those wires every time is the chore switch nodes exist to kill. Multi CLIP Switch is the Creepybits take on the classic three-way CLIP selector. You wire up to three CLIPs into its slots and flip an integer to choose which one flows out. Same idea as the ComfyUI core CLIPLoader plus a switcher, but compact and manual.

The one input that matters

The whole node is driven by a single widget:

• Input - an integer, 1 to 3, that picks which of the three CLIPs gets passed through.

The clip1, clip2, and clip3 inputs are optional wires. Outputs are CLIP (what you feed into your text encoder) and a show_help string - which, in the best Creepybits tradition, is a rotating "proverb of the day" gag rather than actual help. One light laugh per graph, then ignore it.

Why you'd reach for it

Two genuinely useful patterns:

• Multi-model workflows with "modes." Build one graph with an SD1.5, an SDXL, and a Flux CLIP wired into the three slots. Set Input to 1, 2, or 3 and the whole pipeline switches flavor without touching a wire. Pair it with the pack's model and VAE switches and you have a one-knob "which model family am I running" control.
• A/B testing encoders. If you're curious whether the same prompt behaves differently through CLIP-L versus a larger text encoder, this lets you toggle between them on the same graph and compare outputs back to back.

What'll trip you up

The switch is dumb by design: it passes through whatever is in the selected slot, including nothing. If Input is 2 but clip2 isn't wired, you get a None out the other end, and whatever node is downstream will probably throw. ComfyUI lets you leave slots empty, so the failure mode is "works on setting 1, explodes on setting 2" - check your wiring before you blame the node.

Also note the naming. This is the Multi switch: it has a manual selector. The pack's Dynamic CLIP switch has no selector at all - it just passes the first connected non-empty input. If you want active control, this is the one you want.

Installing it

It's part of the Creepybits pack, installed all at once:

cd ComfyUI/custom_nodes
git clone https://github.com/Creepybits/ComfyUI-Creepy_nodes.git

Restart ComfyUI, or find "Creepy" in ComfyUI Manager. The pack's requirements (google-genai, Pillow, OpenCV, numpy) install on first launch. There are no model files to fetch - the CLIPs you wire in are the ones you already have.

Honest verdict: if you only ever run one model, you don't need this. But the moment you're juggling two model families in one graph, a three-way CLIP switch stops being a nicety and starts being the thing that keeps the workflow on one canvas.