Save_It

ComfyUI's default SaveImage writes every generation straight to output/ the moment it finishes. Fine for batch runs, miserable when you're iterating and your folder is a graveyard of rejects. Save_It flips the flow: it shows you the image first, and you decide whether it ever touches disk. Manual save, autosave, folder favorites, A/B compare against the original - it's the save node for people who care where their images go.

It's an output node (no outputs; it terminates the branch), so it slots in exactly where you'd put SaveImage. Feed it images from a VAE Decode and it previews the result with a real UI baked into the node.

What it does that SaveImage doesn't

• Manual save - with AutoSave off (the default), nothing is written until you click the Save button. You review, you keep, you skip. The save_trigger widget is the internal wiring behind that button.
• AutoSave - flip it on and every generated image is saved immediately. The README's guidance is worth following: manual for curation, AutoSave for long unattended runs.
• Where to save - filename_prefix is a mini-template: ComfyUI → output/ComfyUI_00001.png, Portraits/face → a Portraits subfolder, or a full absolute path like D:\MyImages to save anywhere on the system. Absolute paths are the killer feature most save nodes lack.
• Format and quality - PNG, JPEG, or WebP; quality only matters for JPEG/WebP (PNG ignores it).
• Timestamp naming - use_timestamp swaps the counter for date/time filenames when you want time-sorted files.
• Favorites & history - bookmark save locations and switch with a click; the Save History panel shows your last 50 saves with full paths. Favorites persist across workflows and sessions.
• Compare mode - connect original_image and toggle enable_compare for an interactive A/B: horizontal or vertical wipe, overlay with opacity, or a difference view that highlights changed pixels. Handy for before/after LoRA or upscale tests.

Metadata is preserved too - the prompt and workflow chunks ride into the saved PNG, so your outputs stay reproducible.

How the naming works

The sequential counter isn't a global number; it's stored per-folder in a hidden .save_it_counter file inside the save directory. Each destination gets its own counter, and it survives restarts. Do not delete that file if you want numbering to keep going.

Installation

Ships in the ComfyUI-ialhabbal suite. ComfyUI Manager search ComfyUI-ialhabbal, or:

cd ComfyUI/custom_nodes
git clone https://github.com/ialhabbal/ComfyUI-ialhabbal.git

Restart and find Save_It under the interactive category. It uses standard libraries - no extra deps, no model downloads.

Common issues

• The full UI isn't showing - the author's own release thread has a user on ComfyUI portable (0.18.1) hitting exactly this after installing via Manager. A restart with a fresh browser tab usually fixes it; otherwise check your ComfyUI version is recent - the frontend features are served from the pack's web folder and need a compatible client.
• My numbering jumped - the counter lives in the folder, so saving to two different folders starts each at 1. That's by design.
• AutoSave on, but nothing saves - check filename_prefix. An empty or weird prefix can make the save path unresolvable; give it at least a folder/name.
• JPEG looks mushy - quality defaults to 95, but if you cranked it down for size, remember that's a one-way door for that file.

Is it worth switching from SaveImage? If you batch-generate and curate, yes - the manual-save-then-review loop is the whole point, and it's the node the author pairs with their own workflow tools. If you never look at output again after a run, the default is fine and you're not the audience.