☁️BizyAir DualCLIPLoader

Since SDXL, every serious base model dropped SD 1.5's single CLIP-L text encoder in favor of pairing two encoders together for more prompt-following headroom - CLIP-L plus CLIP-G for SDXL, CLIP-L plus a T5 variant for Flux, and SD3 can go either way. This node is the loader that gets both files into your graph at once, matched to whichever architecture you're actually running.

How it works

You pick two encoder files and a type telling BizyAir which architecture's pairing logic to apply to them. Get the pairing wrong - say, loading two CLIP-only files but selecting flux - and text conditioning downstream will be malformed, since Flux's dual-encoder setup assumes one classic CLIP and one T5-family encoder, not two of the same kind. The output is a BIZYAIR_CLIP handle rather than a plain CLIP, which means the actual encoding happens on BizyAir's cloud workers rather than your own GPU - so this dropdown is about matching the checkpoint you're loading downstream, not managing your local VRAM budget the way the equivalent choice would on a purely local setup.

The inputs and outputs that matter

• clip_name1 / clip_name2 - both pull from the same five-option list: clip_l.safetensors, clip_g.safetensors, t5xxl_fp16.safetensors, t5xxl_fp8_e4m3fn.safetensors, umt5_xxl_fp8_e4m3fn_scaled.safetensors. For SDXL: clip_l + clip_g. For Flux: clip_l + one of the t5xxl variants. umt5_xxl is the encoder some non-Flux architectures use in place of a standard T5 - only relevant if that's what your checkpoint actually calls for.
• type - sdxl, sd3, or flux. This tells BizyAir how to interpret the two files you picked; it doesn't infer the architecture from the filenames.
• Output: BIZYAIR_CLIP - feed it into your BizyAir text-encoding node.

On the fp8 vs fp16 T5 choice specifically: fp8_e4m3fn is roughly half the size for a barely-perceptible quality cost, which is why it's the default most people reach for on local Flux setups. Whether that same tradeoff matters here depends on how BizyAir bills/loads it server-side - but if you're not chasing the last percent of fidelity, fp8 is the safe first pick.

How to install it

ComfyUI Manager: search BizyAir, install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/siliconflow/BizyAir

then restart. BizyAir wants an account and API key set up on first use per the README.

Worth knowing before you start troubleshooting a "missing node" prompt: this node shares its name with ComfyUI core's own DualCLIPLoader. Several users have reported BizyAir getting auto-installed by ComfyUI Manager's missing-node resolver on older workflows (pre-February 2025) where Manager guessed the wrong pack for a generically-named node - a bug the Manager maintainer acknowledged and has since fixed. If BizyAir shows up in custom_nodes and you didn't put it there on purpose, that's the likely reason; uninstall it through Manager rather than deleting the folder by hand, since people who did the latter reported leftover files causing follow-on issues.

Common issues & troubleshooting

Garbled or ignored prompts. Almost always a type mismatch against the two files you picked - double-check you selected the pairing that matches your actual checkpoint's architecture.

You only meant to load one encoder. This node is specifically for the dual-encoder architectures; if you're running something that only needs a single CLIP file, use a single-CLIP loader node instead.

It showed up and you didn't install it. See the install note above - check whether Manager auto-resolved it against an older workflow rather than assuming something malicious happened.