Wiring & Fixing VAE Decode & VAE Encode (Tiled)
Practical pin-by-pin connection order and common error fixes for VAE Decode & VAE Encode (Tiled) in ComfyUI workflows.
Updated Oct 17, 2026 · 1 min read
- Target Node
- VAE Decode & VAE Encode (Tiled)
- Required Inputs
- samples (LATENT) or pixels (IMAGE), vae
- Output Pins
- IMAGE or LATENT
- Package
- Built-in Core
Step-by-step pin wiring for VAE Decode & VAE Encode (Tiled)
- Drop VAE Decode & VAE Encode (Tiled) onto the canvas by double-clicking and searching its title.
- Connect all required upstream wires (`samples (LATENT) or pixels (IMAGE), vae`) from your checkpoint loader, prompt conditioning, or image preprocessor.
- Route the output (`IMAGE or LATENT`) into your downstream KSampler or VAE Decode node, then click **Queue Prompt**.
Fixing dependency conflicts and type mismatches
If the console prints a Python import error or tensor shape mismatch on this node, verify that your checkpoint family (SD 1.5, SDXL, or Flux) matches any attached LoRA, ControlNet, or IPAdapter weight.
For custom node packs on Windows, run **Update All** inside ComfyUI-Manager or grab a fresh desktop environment from /download.
FAQs
Why won't a wire snap onto VAE Decode & VAE Encode (Tiled)?
ComfyUI enforces strict pin types. Check that the upstream output matches `samples (LATENT) or pixels (IMAGE), vae` and insert a VAE Encode/Decode or preprocessor node if converting between pixels and latents.
How do I bypass this node temporarily without deleting my wires?
Select the node on the canvas and press **Ctrl+B** (Bypass) or **Ctrl+M** (Mute) to test your graph without disconnecting cables.
Run on your hardware. Free forever.
The full ComfyUI engine: open source, fast, extensible, and yours to run however you want. Download the desktop app and open this workflow on your own machine.
