☁️BizyAir VAE Decode

This is the node at the very end of almost every generation workflow - the one that turns whatever your sampler produced back into an actual picture. Samplers work entirely in latent space, a compressed representation that isn't directly viewable; VAE Decode is the translation step back to real pixels, and skip it and you've got nothing to save or look at.

Conceptually it's identical to ComfyUI's core VAE Decode node. The difference, consistent with the rest of this pack, is that the decode itself happens on BizyAir's cloud rather than locally, and its VAE input has to come from a matching BizyAir loader.

Inputs and outputs

Two required inputs:

• samples - the latent to decode, type LATENT. This is a standard type, so it'll accept latents from any sampler in your workflow, BizyAir or not.
• vae - the VAE to decode with, type BIZYAIR_VAE, which must come from BizyAir Load VAE. This is the input that only connects within the BizyAir family - a stock ComfyUI VAE Loader's output won't plug in here.

Output is a single IMAGE - the final decoded picture, ready for a Save Image node or any further postprocessing.

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 through the README's "click to login" step - since this decode runs server-side, a missing key means the very last step of your workflow simply won't complete, which can be a confusing place to hit a wall after everything upstream ran fine.

Common issues

If everything upstream in your workflow ran without errors but this node fails, check the API key first - it's easy to assume a problem this late in the pipeline is about the image or the sampler, when it's actually the same auth requirement every BizyAir node has.

Match your vae to your checkpoint's actual model family. Decoding a latent that came from a Flux-based sampling pass with an SDXL VAE (or vice versa) produces a technically-valid image that's visibly wrong - washed colors, static-like artifacts, or structure that doesn't match what you expected. If your final image looks broken but the workflow ran without errors, the VAE mismatch is the first thing to check, not the sampler settings.

And remember the type boundary: vae here needs BIZYAIR_VAE specifically, so it has to trace back to BizyAir Load VAE somewhere upstream in your graph, not a stock ComfyUI loader.