ComfyUI Client Set Image (Yogurt Nodes)

The other Set nodes patch numbers and strings. This one ships pixels. ComfyUI Client Set Image takes an image from your local graph, uploads it to the remote ComfyUI server, and rewires the target node's input so the remote workflow uses your image. For img2img, inpaint-with-local-mask, ControlNet reference, or any remote workflow that needs an image it didn't generate, this is the node that connects the two machines at the pixel level.

How it works

The flow is: upload the image to the remote server's input folder via its upload API, then patch the target node's input to reference the uploaded file. That's why Load's auto_connect matters - the tooltip on it says the HTTP session (needed for image upload) should be live, so make sure it's on true for Set Image to work. The node takes the first frame of the input batch - the tooltip is explicit about that - so a multi-image batch gets collapsed to its first image. If you want to send several distinct images into a remote workflow with multiple image inputs, you chain multiple Set Image nodes, one per slot.

The upload-then-reference pattern is the standard way external tools feed ComfyUI: the image lands in the server's input directory, the workflow's Load Image picks up that filename, and the remote graph treats it like any other input file. Nothing about the remote workflow needs to change to accept your image - you're just supplying the file it would otherwise expect to be sitting in its folder.

Inputs

• client - the handle from Load (with auto_connect on) or a previous Set node.
• node - the remote node's id or title - typically the Load Image node.
• key - the input field name in the workflow JSON.
• image - the image to upload; the first frame of the batch is used.

Outputs

• client - the patched handle, passed on toward Run.

Install

Standard Yogurt Nodes install. ComfyUI Manager → search "ComfyUI-YogurtNodes", or:

cd ComfyUI/custom_nodes
git clone https://github.com/yogurt7771/ComfyUI-YogurtNodes.git
cd ComfyUI-YogurtNodes && pip install -r requirements.txt

Then restart ComfyUI.

Where people get burned

Most common failure: auto_connect is off, and the upload silently fails. The session isn't live, the image never lands, and the remote runs against whatever stale file it had. Turn it on first, and if an upload "works" but the remote uses an old image, check that the target node actually reads from the uploaded filename rather than a hardcoded one. Second, only the first frame uploads - if you need a specific frame of a batch, index it locally before this node, or you'll get frame 0 every time. Third, remember the remote's input folder accumulates your uploads: run the same workflow a hundred times with different images and the server fills with orphaned files. Not a failure, but a housekeeping bill you're running up. And as ever with this family: the node/key references go stale when the remote workflow changes - a renamed Load Image node means your image goes to a slot nobody reads.