Image Save

The built-in Save Image node is deliberately bare: it drops PNGs into ComfyUI/output/ with a numbered prefix and that's it. Image Save from WAS is the upgrade you install once you start caring where files go and what they're called. Custom output path, choice of format, quality control, and - the real reason people switch - filename tokens.

If you generate at volume, the tokens alone justify it. You can bake the date, time, hostname, or CUDA device straight into the filename, so a folder of outputs is self-documenting instead of ComfyUI_00042_.png.

How it works

You feed it images and it writes them to disk in the format and location you specify. The README spells out the useful bits:

• Format support - PNG, JPEG, and WebP among them. WebP needs your system to actually have WebP support (a package install on Linux, a precompiled library on Windows), which is the one format that isn't guaranteed to just work.
• Path support - point it at any output directory, not just the default output/ folder. (Note the flip side: the node's show_history preview only displays images saved inside ComfyUI/output/ - files written elsewhere save fine but won't show in the history strip.)
• Text tokens - this is the killer feature. In the filename you can use tokens like [time], [time(%Y-%m-%d__%I-%M%p)], [hostname], [cuda_device], and [cuda_name]. So a prefix of [hostname]_[time(%Y-%m-%d)] writes files already stamped with machine and date. You can even register your own tokens with the pack's Text Add Tokens node.

Inputs and outputs that matter

The images input is obvious. The three settings you'll actually touch: the output path (where), the filename prefix (what it's called, tokens allowed), and the format/extension (PNG for lossless and workflow embedding, JPEG/WebP when you want smaller files). There's a quality control for the lossy formats and a show_history toggle that displays previously-saved WAS images in the node.

This is a terminal node - it saves to disk and doesn't pass an image onward to chain further. It's the end of the line.

How to install it

ComfyUI Manager: search was-node-suite-comfyui, install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/WASasquatch/was-node-suite-comfyui

then run the pack's requirements.txt in your ComfyUI venv and restart. For WebP output specifically you'll also want WebP available to your OS - apt-get install webp on Linux, or the precompiled libwebp on Windows.

Common issues & troubleshooting

WebP saves fail or the option does nothing. WebP isn't bundled - your system needs it. Install libwebp (Linux: apt-get install webp; Windows: grab the precompiled binary from the WebP project). Until then, stick to PNG or JPEG.

Files saved to a custom path don't show in the node's history. By design - show_history only previews images written under ComfyUI/output/. The files are on disk where you told them to go; they just don't appear in the strip. And ComfyUI resizes history thumbnails to a uniform size, so a mixed-resolution history looks squished.

PNG vs JPEG for sharing workflows. ComfyUI embeds the workflow graph into PNG metadata, and that's how the "drag the image back in to rebuild the graph" culture works. Save JPEG or WebP and you usually lose that embedded workflow. If you want the image and the reproducible graph, keep it PNG.

"Import Failed" for the whole suite after a ComfyUI update. Classic WAS Node Suite: it downgrades some packages for older modules, so a ComfyUI upgrade can break the import at startup. Re-install the pack's requirements against the activated venv (or run install.bat). The suite's been maintenance-only since late 2023, so this reinstall is a known, recurring step.