2🐕Specify image save path

ComfyUI's built-in Save Image node writes everything into one output folder, named with a prefix you set. That's fine for casual use and quickly annoying the moment you're running several different workflow branches and want their results kept apart - test renders in one folder, finals in another, a batch job's output somewhere you can find it without digging through hundreds of same-folder files. Specify image save path is ergouzi's answer: same idea as the stock node, plus an actual directory field.

How it works

Three required inputs, and it's a terminal node - it doesn't pass anything further downstream, it just writes files to disk. images is whatever batch of images you want saved. filename_prefix (default ComfyUI) works exactly like the stock Save Image node's prefix - it's prepended to each saved file's name. custom_output_dir (default empty) is the actual new capability: point it at a directory and your images land there instead of ComfyUI's default output/ folder.

What to actually set

custom_output_dir is the whole reason to use this over the stock node - leave it blank and you've essentially got a slightly different Save Image. Set it to an absolute path, or a path relative to wherever ComfyUI is running from, depending on how the node resolves it. One thing worth being deliberate about: if you type a path that only exists on your own machine - a folder on your desktop, a drive letter from your dev PC - make sure that path actually exists in whatever environment is executing the workflow. A folder that's real on the machine where you built the workflow won't magically exist somewhere else the same graph gets run.

Installing it

ComfyUI Manager: search "Comfyui-ergouzi-Nodes", install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/11dogzi/Comfyui-ergouzi-Nodes.git

No models involved - this just writes files. Standard note for the pack: this English repo is the frozen branch, with the author's active work continuing in a separate Chinese-first sibling repo.

Common issues & troubleshooting

Nothing gets saved, or you get an error about the path. The most likely cause is custom_output_dir pointing at a folder that doesn't exist - most save nodes of this kind expect the directory to already be there rather than creating nested folders on their own. Create the target folder ahead of time if you're not sure it exists.

Files show up in the default output folder instead of your custom one. Double-check custom_output_dir isn't actually blank - it's easy to leave it unset while assuming you configured it, since an empty string is a valid (if unhelpful) value that just falls back to default behavior.

Path works locally but not somewhere else the workflow runs. This is the general trap with any node that takes a literal filesystem path as a text field: it's tied to whatever machine executes it. If you're sharing this workflow or running it somewhere other than where you built it, use a relative path or confirm the target directory exists in that environment too.