Save Image Out

The stock Save Image node is a dead end - you feed it an image, it writes a file, and that's the last you hear from it. Nothing comes back out, which is fine for a workflow that ends there, but useless the moment you want to do something with the file you just saved: log its location, hand it to another tool, or reference it later in the same run. Save Image Out fixes that by passing the image straight back through and adding the saved file's path as a second output.

It's a small node from ComfyUI-WJNodes, a personal utility pack from an author who publishes only under the GitHub handle 807502278 - one of several nodes in this pack that exist purely because the stock equivalent throws information away that's genuinely useful to keep.

What it does

Two inputs, nothing exotic: an image batch and a filename prefix, exactly like the built-in Save Image node. It writes the file(s) to ComfyUI's output directory the normal way. The difference is entirely in what comes back: instead of being a dead-end terminal node, it returns both the original IMAGE (so you can keep chaining it into a preview node, or another save step, without needing a second copy of the same wire) and PATH, a string with the file's location on disk.

Inputs and outputs that matter

• images - the image or batch to save.
• filename_prefix - default ComfyUI, same convention as the built-in node.

Outputs: IMAGE passes the input straight through, and PATH is the saved file's path as a string. This node is marked as an output node in ComfyUI's graph, same as Save Image - it'll run even if nothing downstream consumes its outputs, so you can use it purely for the save, and only wire up PATH when you actually need it.

Why this is worth using over the stock node

The obvious case is chaining: feed PATH into this pack's own Load_Image_From_Path elsewhere in the same graph, or into Split_Path if you want to pull the filename or extension out for use in another string (naming a related output file to match, say). It's also handy for straightforward logging - wire PATH into a text preview so you can see exactly where a given run's output landed without hunting through the output folder afterward, which matters more than it sounds like once you're running batches and losing track of which file corresponds to which run.

Installing it

ComfyUI Manager: search "ComfyUI-WJNodes." Manually:

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

Restart ComfyUI. No models, no extra dependencies - this is a thin wrapper around standard file-saving.

Where to be careful

The PATH output reflects wherever ComfyUI's output directory actually resolves to on the machine running the workflow - typically an absolute path. If you're chaining that path into something running in a different environment, or expecting a relative path for portability, that mismatch is something you'll need to handle yourself; the node doesn't normalize or rewrite it.

This is another node from a pack with no public discussion anywhere to check against, so behavior around edge cases - saving a batch of multiple images and getting a single PATH back, for instance - is best confirmed by testing directly rather than assuming based on the stock node's conventions. If you're saving a batch, check what exactly the path output contains (one path, or something else) before building logic that depends on it.