ImageSaveToPath(ImageIOHelpers)

ComfyUI's built-in Save Image decides where your files go, and it only knows one neighborhood: its own output/ folder. Fine for everyday generation. Useless when another tool is supposed to pick up the file from its directory - a game/texture pipeline, a watch folder, a folder an app polls. ImageSaveToPath(ImageIOHelpers) is the save node that lets you say where. You type a path, it writes the PNG there.

It's an output node with no graph outputs: images in, file out. If LoadByPath is the pack's "read from anywhere," this is its "write to anywhere," and it's the one I'd reach for out of the whole set. Core Save Image's folder lock is one of the small frictions that keeps tripping people up when ComfyUI meets the rest of their stack.

The inputs that matter

• images - the IMAGE tensor to save.
• folder_path - STRING, the target directory. Absolute paths only, really; relative resolves from the server's working directory and you'll just confuse yourself.
• filename_prefix - STRING, default ComfyUI. Files get named with this prefix plus a counter, exactly like core Save Image. Set it to something descriptive and files become findable: export, render, tile-04.
• save_prompt (bool, true) - embed the workflow into the PNG's metadata so you can drag it back in later. Leave it on.
• save_extra_pnginfo (bool, true) - same idea for extra run metadata.
• compress_level (int, 0–9, default 4) - PNG compression. 4 is the standard ComfyUI default, a sane balance. 9 shrinks files noticeably but slows the save; 0 is near-instant and produces giant files. You'll rarely need to touch it, but it's there when you're writing thousands of tiles.

How to install it

cd ComfyUI/custom_nodes
git clone https://github.com/Ryuukeisyou/comfyui_image_io_helpers

Restart ComfyUI, or install via ComfyUI Manager (search "comfyui_image_io_helpers"). No models to download, no heavy dependencies - this is plain image encoding. The pack is a tiny five-node set and the GitHub repo has been 404ing when fetched directly, so if the clone fails, that's the known cause, not you.

Troubleshooting

The usual suspect is the folder: create the target directory before the run, and make sure the ComfyUI process can write there. If the server runs as a service or a different user, a folder that looks fine in your file manager can be unwritable from ComfyUI's perspective - permission errors are the #1 "where did my image go" report for path-based save nodes. Double-check that folder_path is the folder, not a filename-with-trailing-slash hybrid, and remember the filename is auto-built from the prefix. If nothing appears, your first move is verifying the absolute path and write access, not reinstalling anything.

One more habit worth forming: leave save_prompt on. When you later find a random render in a shared folder, the embedded workflow is how you figure out what made it - that's the whole "workflow included" culture of this ecosystem, applied to files that left ComfyUI's walls.