☁️BizyAir Load VAE

The VAE is the part of the pipeline that translates between the compressed latent space your sampler actually works in and real pixels - it's what BizyAir VAE Encode and BizyAir VAE Decode call on. This node is simply where you pick which one. It matters more than it looks: a mismatched VAE (an SDXL VAE loaded against a Flux checkpoint, say) produces washed-out colors or outright broken images even when everything else in the workflow is correct, because different model families genuinely use different VAEs and they aren't interchangeable.

Inputs and outputs

One required input: vae_name, an enum of the VAE files BizyAir hosts. The sample list spans several model families at once, which is a useful map of what this loader is meant to cover: sdxl/sdxl_vae.safetensors for SDXL, flux/ae.sft for standard Flux, three Flux-Tools-specific variants - flux.1-canny-vae.safetensors, flux.1-depth-vae.safetensors, flux.1-fill-vae.safetensors - for the Canny, Depth, and Fill/inpainting tools respectively, and wan_2.1_vae.safetensors for Wan video.

That Flux Tools split is worth calling out specifically: Canny, Depth, and Fill aren't just LoRA-style add-ons to base Flux, they ship with their own matched VAE, and using the plain flux/ae.sft VAE with one of those checkpoints instead of its dedicated variant is a real, easy-to-make mistake.

Output is vae, typed BIZYAIR_VAE - a custom type that only connects to other BizyAir nodes expecting it, specifically BizyAir VAE Encode and BizyAir VAE Decode. It won't plug into ComfyUI's stock VAE-consuming nodes, and a locally-loaded VAE won't plug into BizyAir's Encode/Decode nodes either.

Installing BizyAir

Through ComfyUI Manager: search "BizyAir," install. Or clone it manually:

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

Restart ComfyUI, or run comfy node install bizyair via Comfy-CLI. Set your API key on first use via the README's "click to login" step - like every loader in this pack, the actual VAE runs server-side rather than as a local file you're managing yourself.

Common issues

Washed-out colors, static-like noise, or images that look almost right but subtly off are the classic symptoms of a VAE/checkpoint mismatch - before troubleshooting anything else in the pipeline, confirm you picked the VAE variant that actually matches your loaded model, especially if you're using one of the Flux Tools checkpoints (Canny, Depth, Fill) rather than plain Flux.

Type mismatches are the second common trap: this loader's BIZYAIR_VAE output only connects downstream to BizyAir's own Encode/Decode nodes. If a connection won't make in the graph editor, check you're not accidentally mixing a stock ComfyUI VAE node into an otherwise-BizyAir chain.

And if the dropdown looks thinner than you expected for a given model family, that reflects what BizyAir currently hosts rather than the full universe of VAE files floating around HuggingFace - it won't necessarily have every community VAE variant available.