🌻 Zip Save

Takes a directory and compresses it into a single .zip. That's it - and it's exactly the thing you want at the end of a batch job when you've just generated two hundred images and would rather grab one file than click download two hundred times.

When this earns its place

Batch workflows produce piles of files: image sets, caption text, a dataset you're prepping for training. Moving those around one at a time is miserable. Zip Save sits at the tail of a pipeline and rolls a whole output folder into one archive you can download, upload, or hand to someone. It pairs naturally with the pack's other batch nodes - save a run's worth of images with the Image Saver, drop the captions next to them, then zip the folder and you've got a tidy deliverable. The README frames it exactly that way: good for backups or sharing several files at once.

How it works

There's no magic here - it walks the input directory and writes a standard ZIP to the output directory under the filename you give it. Everything is a path on the machine running ComfyUI, which matters: on a serverless or cloud host, these are server-side paths, not folders on your laptop.

The inputs

Three, all strings, all straightforward:

• Input_Directory - the folder you want zipped. This needs to actually exist and contain files.
• Output_Directory - where the finished .zip gets written.
• Zip_Filename - the archive name, defaulting to archive.zip.

It's an output node, so it fires as an endpoint. Two outputs come back: Zip_Path, the full path to the archive it just wrote (wire this into a downloader, an uploader, or a cleanup node), and Status, a message telling you how it went.

Common issues

The usual snag is the input directory: point it at an empty or wrong folder and you get an empty or missing archive with nothing useful inside. Check the path before you rely on it, and make sure whatever writes those files (your saver node) runs before Zip Save in the graph order - zipping a folder before it's been populated gives you nothing. Because everything is server-side paths, remember on a hosted ComfyUI you're zipping files on the host and then retrieving via Zip_Path, not reaching into your own filesystem. And ordinary write-permission rules apply to Output_Directory - pick a folder the process can write to, like ComfyUI's output.

Installing ComfyUI-Addoor

ComfyUI-Addoor (葵花宝典) is a utility and batch-plumbing pack from developer Eagle-CN. ComfyUI Manager: Install Custom Nodes → search "ComfyUI-Addoor" → install → restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/Eagle-CN/ComfyUI-Addoor.git
cd ComfyUI-Addoor
pip install -r requirements.txt

Restart and find it under 🌻 Addoor / Utilities.