Nodes/comfyui-bus-plugin/Latent Image Bus
ComfyUI Node

Latent Image Bus

The pair you need to decode, in one place

By rhdunn·Created 2 years ago·Updated 2 years ago· 2
Latent Image Bus
  • latent
  • vae
  • latent
  • vae

End of workflow, every time: your KSampler hands you a latent, and to see the picture you have to run it through VAEDecode - which also needs the VAE. Two values, one destination, and if you've been building a big graph the latent and the VAE may have come from entirely different corners of the canvas. The Latent Image Bus bundles them so they travel together and arrive at the decode in one tidy spot.

It's the decode-side sibling of the Image Bus, and like everything in this pack it's a straight pass-through: latent in, latent out; VAE in, VAE out. No decoding happens here. What it buys you is organization - the latent and its VAE pass through one labeled junction, so the decode end of your workflow reads like a single "here's what we're turning into pixels" step instead of two mystery wires crossing the graph.

The inputs and outputs

  • latent (LATENT) - required. The sampler's output, still in latent space.
  • vae (VAE) - required. The VAE needed to turn it back into an image.

Both come out the far side under the same names, latent and vae, and both go straight into a VAEDecode node. That's the canonical wiring, and it's essentially the whole use case. If you're also carrying a mask for the decode, note that this bus doesn't include one - the Image Bus handles the image/mask/VAE combination, and this one sticks to latent+VAE.

Installing it

Same pack as the other ten bus nodes. ComfyUI Manager: search "comfyui-bus-plugin", Install, restart. Or by hand:

cd ComfyUI/custom_nodes
git clone https://github.com/rhdunn/comfyui-bus-plugin

then restart. Pure Python, no dependencies, no model files to fetch - the entire pack is a few small source files.

Common issues

Honestly, this node is hard to get wrong. The one way people do: they feed it a decoded image instead of a latent, or they assume the bus will pick the "right" VAE automatically. It won't - the VAE input is required and you have to connect one, and it has to be the VAE that matches your checkpoint. Wire in a mismatched VAE (say, an SDXL VAE into an SD1.5 latent) and the decode comes out mangled, and the bus will happily pass that mismatch through because it doesn't validate anything. Same as the rest of the pack: it organizes, it doesn't decide.

CategoryComfyBus

Inputs (2)

NameTypeDefaultDescription
latentLATENT
vaeVAE

Outputs (2)

NameTypeDescription
latentLATENT
vaeVAE