CLIP Passthrough

If your first reaction to "CLIP Passthrough" is "why does that exist," you're not wrong. It takes a CLIP, hands it back to you completely untouched, and does nothing else. That's the entire job. But "does nothing" is the point, because CLIP Passthrough solves a wiring problem, not a generation problem.

In ComfyUI, CLIP is the text-encoder object. You load it once via a Checkpoint Loader or a separate CLIP Loader, and everything downstream - every CLIP Text Encode - wants to borrow it. The clean pattern is one source, many consumers: load CLIP once, feed it to every encoder, and never encode through a second loader. The trouble is that a busy graph buries the loader under forty wires, and the first time you duplicate a big branch you end up with a second CLIP Loader running the same model twice. CLIP Passthrough exists so you can take that single CLIP wire, run it through a tidy little node where you can see it, and fan it out from there.

The mechanism is about as honest as nodes get. Look at the source and you'll see the input is clip (optional, marked forceInput), the output is clip, and the function literally returns whatever came in. No copy, no re-encoding, no cost. If you leave the input unconnected, the node outputs nothing - same as every optional passthrough in this pack - so it won't error a workflow that's still mid-build.

Inputs and outputs that matter

There's one input and one output, both named clip and both CLIP type. That's the whole schema:

• clip (in) - the CLIP object, usually straight from your Checkpoint or CLIP Loader.
• clip (out) - the same object, ready to wire into CLIP Text Encode nodes.

Installing it

This is a node from the wenchengxiang/ComfyUI-Practical-Tools pack, and the whole pack installs the same way. ComfyUI Manager is easiest: open Manager → Custom Nodes Manager → search "ComfyUI-Practical-Tools" → Install → restart ComfyUI. Or skip Manager and clone it by hand:

cd ComfyUI/custom_nodes
git clone https://github.com/wenchengxiang/ComfyUI-Practical-Tools

then restart ComfyUI. No pip install, no requirements.txt, no model downloads, no CUDA dependencies - these are pure-Python nodes running on the torch/PIL/numpy ComfyUI already ships. If the node doesn't show up, the pack auto-discovers its own files and prints [WCX Nodes Error] lines to the console, which will name the file that failed.

Issues and gotchas

Honestly? There aren't many. A passthrough can't really break. Two things worth knowing: first, it only does anything when it's connected - an unconnected CLIP Passthrough is inert and won't block a run. Second, it's a typed node, so unlike the core Reroute it will only accept CLIP; if what you actually need is "bend this one wire so my graph isn't a noodle plate," the built-in Reroute is the lighter tool and ComfyUI's own docs treat it as the legibility fix. Reach for CLIP Passthrough when you want one visible, typed spot to split a CLIP to several encoders - or when a shared workflow you downloaded already uses it and you don't want to re-plumb a graph that works.