Save image to an absolute path and provide text optional to control execution order v5.1.0

ComfyUI's built-in Save Image is fine until you need a file in a specific place - a path a script watches, a folder your automation polls, a directory outside ComfyUI/output. That's the whole reason SaveImage_absolute exists: you type an absolute path, it writes a PNG there, done. No timestamped subfolders, no renaming conventions, no fighting the output directory.

The sneaky extra is in the name after the colon: "and provide text optional to control execution order." The node returns the filename it saved as a STRING output, and you can wire that string into another node as a dependency to force ordering in the graph. In a pipeline where a downstream step needs the file to exist on disk before it runs - a script that reads the file, a shell node, another tool watching the folder - that string wire is the guarantee.

How it works

Under the hood it's the smallest possible implementation: take the first image in the batch, convert to a numpy array, and Image.fromarray(...).save(absolute_filename). PIL handles PNG encoding. Nothing fancy, no metadata embedding - which is worth knowing if you rely on ComfyUI's "workflow embedded in the PNG" behavior. This node strips that.

The inputs that matter

• images (IMAGE) - the image(s) to save. Only the first frame of the batch is written, so for multi-image output you'll want a loop or per-image save.
• absolute_filename (STRING, default image.png) - the full path, e.g. /home/me/pipeline/out.png. It must be absolute - the node does not resolve relative paths against anything.

Output: a STRING (the filename) labeled text to control order - wire it onward to enforce execution order.

Installing it

Part of TRI3D-LC/tri3d-comfyui-nodes:

cd ComfyUI/custom_nodes
git clone https://github.com/TRI3D-LC/tri3d-comfyui-nodes
cd tri3d-comfyui-nodes
pip install -r requirements.txt

or ComfyUI Manager → "tri3d-comfyui-nodes", restart. This one lives in the image category.

Common issues

• Only the first frame saves - batch input quietly becomes a single file. If you expected a full batch, check the shape first.
• Relative paths do nothing useful - it writes relative to ComfyUI's CWD, which is almost never what you meant. Always use an absolute path.
• No metadata - because it bypasses ComfyUI's save pipeline, your PNG won't carry the workflow JSON. Fine for automation, annoying if you wanted provenance.
• The filename string is stale for batches - it returns what you passed in, not a per-frame name. For batch jobs, generate filenames upstream.

For scripts and automation this is a genuinely useful escape hatch; for everyday saving, the built-in node is friendlier. Pair it with SaveText_absolute and the ordering trick becomes a habit: save the PNG, save its prompt text, and the text-save waits on the image-save through the string wire.