ComfyUI Node

VAE Decode ColorFix

Why your Flux images look washed out — and the decode node that fixes it

By Ltamann·Created about a year ago·Updated 7 months ago· 20
VAE Decode ColorFix
  • samples
  • vae
  • IMAGE

If you've generated Flux images in ComfyUI and thought "huh, everything looks a bit brighter and flatter than it should," you weren't imagining it. The standard VAEDecode node has a known habit of producing washed-out, brightened colors with Flux models, and the pack author published a whole r/comfyui post (as TBG______) explaining exactly why: decoding a full large image at once makes the VAE's normalization statistics drift from what the model was trained on, so the colors shift. Decode in smaller tiles and each tile gets fresh, training-close statistics - which is why VAE Decode (Tiled) looks more correct but costs three passes and a lot of time.

This node is the middle path. It's a drop-in VAE decoder that tiles the latent into 256px tiles with a 25% overlap for smooth blending - but runs a single pass instead of the stock tiled node's three passes. The author claims roughly 3x faster than stock tiled decode while keeping the color accuracy. That claim checks out against the source: it calls ComfyUI's tiled_scale once instead of the decode_tiled three-pass orientation averaging.

What it takes and gives

Only two required inputs, both obvious:

  • samples - the LATENT to decode (wire it from your sampler/VAE Encode).
  • vae - the VAE model. Load the same one you encoded with.

One output, IMAGE. It's a straight swap for VAEDecode in any Flux workflow; the fix is invisible unless your colors were wrong, which is the whole point.

Install

ComfyUI Manager → search TBG Takeaways → install, restart. Or by hand:

cd ComfyUI/custom_nodes
git clone https://github.com/Ltamann/ComfyUI-TBG-Takeaways

Restart, and you'll find it under TBG/Takeaways. No extra dependencies, no model downloads - it uses your loaded VAE.

The honest trade-offs

This is a real problem with a real fix, but keep perspective. One commenter on the author's post noted that stock VAE Decode (Tiled) isn't actually slow until you're decoding very large images - so if you're doing 1024×1024 or smaller, the standard tiled node is a fine, more battle-tested option. Where ColorFix shines is big tiled upscaling, where you decode huge canvases tile-by-tile and the 3x speedup actually matters. It's also worth knowing the author built this for his TBG ETUR upscaler, so it's tuned for that use case rather than general-purpose decoding.

One practical note: if your Flux images look fine, you don't need this node - don't go hunting for a problem you don't have. But if darker images come out bright, washed, or slightly off, swap this in for VAEDecode and A/B them. It's a two-minute change that either fixes your color or tells you your issue is upstream in sampling, not decoding.

CategoryTBG/Takeaways

Inputs (2)

NameTypeDefaultDescription
samplesLATENTThe latent to be decoded.
vaeVAEThe VAE model used for decoding the latent.

Outputs (1)

NameTypeDescription
IMAGEIMAGEThe decoded image with accurate colors.