Rebel Save Image 💾

Every workflow ends the same way: a Save Image node writes your result to disk with the workflow embedded in the PNG metadata. Rebel Save Image 💾 is the pack's animated version of that terminal node - take an IMAGE, give it a filename prefix, and ComfyUI writes it to the output folder. Same file writing, same metadata embedding, same output directory; the only difference is the Matrix rain behind the controls. It's the natural final node in a Rebel-styled graph: decode, look, save, all matching.

How it works

The standard wrapper: pull the native SaveImage inputs, add the two cosmetic enums, and delegate the actual write to core ComfyUI. The file lands in your output folder, named prefix_00001_.png and counting up, with the workflow JSON baked into the metadata - the whole "drag the image back into ComfyUI to reconstruct the workflow" trick works because of that metadata, and it works identically here. The animation is frontend-only.

The inputs that matter

• images - the IMAGE to save, from your VAE Decode or anywhere pixels end up.
• filename_prefix - the file name prefix, default ComfyUI. The author's own tooltip calls out the fun part: it supports format strings like %date:yyyy-MM-dd% or %Empty Latent Image.width%, so you can bake dates and other node values into filenames.
• theme / color_scheme - the 12 animations and 14 palettes. Decoration.

There are no outputs - like the core Save Image, it's an output node that ends the branch.

Installing it

One clone, 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) so the cached frontend JavaScript reloads and the animation draws. It's under Rebel AI → Animated Core.

Where people get burned

• "Where did my image go?" Same place the stock node puts it: your ComfyUI output directory. If you changed filename_prefix with formatting tokens, double-check the token syntax - a mistyped %date% token can produce an odd-looking filename (or fail to expand) even though the image saves fine.
• No animation after install. Browser cache - hard refresh. The pack's README calls this step critical for a reason.
• Flat backdrop on Nodes 2.0. The pack renders on the legacy LiteGraph canvas; saving works fine but the animation can vanish under the newer frontend.
• File overwrites / duplicate names. Same behavior as stock: the counter suffix (_00001_) keeps collisions from clobbering each other.

It's the last node in the pipeline and one of the easiest swaps in the pack - the exact tool you already use, in a jacket that matches the rest of your graph. Nothing clever, nothing missing.