Rebel Load VAE 🗜️

Rebel Load VAE 🗜️ is the pack's version of ComfyUI's VAELoader node. It does one thing: load a VAE - the encoder/decoder that shuttles pixels back and forth between image space and the latent space your sampler actually works in - and hand you a VAE object. In a standard workflow it feeds your encode and decode stages, and swapping in a better VAE is one of the cheapest quality upgrades you can make (a sharper VAE file can visibly clean up faces and details in your decoded output). The Rebel version wraps all of that in the pack's animated styling, nothing more.

How it works

Same wrapper playbook as every node in the pack: pull the native VAELoader's inputs, add theme and color_scheme, delegate the actual load straight to core ComfyUI. The VAE object that comes out is byte-identical to the stock loader's. The animation is a frontend overlay drawn behind the widgets - zero effect on the load, zero VRAM cost beyond the model itself.

The inputs that matter

• vae_name - the VAE file, listed from ComfyUI's VAE folder (typically models/vae, though ComfyUI also finds built-ins in a couple of other spots). This is the only field that does anything besides decorate the node.
• theme / color_scheme - the 12 animations and 14 palettes. Purely cosmetic.

The output is a single VAE socket, which splits to both your VAE Encode (pixels → latent) and VAE Decode (latent → pixels) stages.

Installing it

The pack installs as one unit, no dependencies:

cd ComfyUI/custom_nodes
git clone https://github.com/RealRebelAI/Rebels_Animated_Nodes.git

Restart ComfyUI, then hard refresh the browser (Ctrl + F5 / Cmd + Shift + R) - without the forced reload, ComfyUI's cached frontend JavaScript means the animation won't draw even though the node works. No models to download; bring your own VAE file. It's under Rebel AI → Animated Core.

Where people get burned

• "My VAE file isn't listed." The dropdown reads the VAE folders. Drop the .safetensors there and restart ComfyUI so it rescans; a stale folder listing is the usual cause.
• "Blurry images / weird artifacts." That's rarely the loader and usually the VAE choice itself. Try a better VAE file - this node will happily load any of them; the loader isn't the quality bottleneck, the file is.
• Animation missing on Nodes 2.0. The pack renders on the legacy LiteGraph canvas; under the newer frontend the load works but the backdrop can go flat.

There's no deep mystery here: it's a one-field loader with a pretty box. If you're committing to the Rebel aesthetic across your graph, you'll want it so the VAE row matches the rest. If you're not, the stock VAELoader does the identical job in a gray box.