SP_WebsocketSendImage

If you're running ComfyUI through the browser UI, you already have a way to see your images - you don't need this node. SP_WebsocketSendImage is for the other case: something driving ComfyUI programmatically, over the API, that wants the output pushed straight to it rather than written to a file it then has to go find and read back.

What it does

One required input, images, typed IMAGE. No outputs - it's an output node, a terminal step that fires as a side effect of running. When it executes, it sends the image data out over ComfyUI's websocket connection to whatever client is listening on that run.

This is the same idea behind ComfyUI's own built-in SaveImageWebsocket node, which a lot of API-driven tooling already relies on for exactly this reason: writing to disk and then reading the file back adds a round trip and a cleanup step you don't need if the client just wants the bytes. SP_WebsocketSendImage gives SP-Nodes users the same capability without pulling in ComfyUI core's version, and it fits the pack's broader theme - the same author also builds Comfizen, a desktop app that turns ComfyUI API workflows into a simplified point-and-click UI, and tools like that live and die on having a clean way to get results back out of a running workflow in real time.

How you'd use it

Wire your final image output into this node instead of (or alongside) a regular Save Image node, and have your API client listening on that run's websocket connection ready to receive binary image data as it comes through. If you're writing your own client against ComfyUI's API, this is the piece that lets you skip polling a history endpoint or watching an output folder - the image arrives the moment the workflow produces it.

Installing it

Part of the SP-Nodes pack:

• ComfyUI Manager: search "SP-Nodes", install, restart.
• Manual: cd ComfyUI/custom_nodes && git clone https://github.com/bananasss00/ComfyUI-SP-Nodes, restart ComfyUI.

No models, no heavy dependencies - it's a thin wrapper over ComfyUI's own websocket layer, same as SP_SendStringWebsocket in this pack.

Troubleshooting

The most common gotcha with any websocket-based image node is client-side, not node-side: you have to be subscribed to the correct client/session ID - the one your API call used when it queued the prompt - or the image goes out on a channel nobody's listening to. If you're testing this and getting nothing, verify your client's websocket subscription matches the run before assuming the node isn't firing. And since ComfyUI's API has no authentication by default, if your instance is reachable beyond localhost, image data sent this way is visible to anyone who can open a connection to it - the same caution that applies to running an unauthenticated ComfyUI instance in general, not something specific to this node.