Send Image (Texturaizer)

Every ComfyUI graph ends somewhere, and in the Texturaizer pipeline that "somewhere" is usually Send Image. It's a SaveImage in disguise: it takes your generated IMAGE, writes it to disk, and passes it along so your graph can keep going. In a Blender workflow that pass-through is the whole point - Texturaizer's viewer and history panel read these saved files, so this node is how finished renders get back out of ComfyUI and into Blender's monitoring UI.

Context: Texturaizer is a paid Blender addon by Luke Kratsios (LatentSpaceDirective); these nodes are the free open-source ComfyUI half.

Inputs and outputs

• images (IMAGE) - required; the images to save.
• filename_prefix (STRING, optional) - the filename prefix. It supports ComfyUI's formatting tokens (%date:yyyy-MM-dd%, or %Empty Latent Image.width% to embed values from other nodes) per the author's tooltip.
• images (IMAGE) out - the same images, passed through so downstream nodes still get them.

So it's a "send" node with a passthrough, not a terminal one. In a multi-pass scene you'll often place it mid-graph, after a decode, so the pass is captured and the data keeps flowing to the compositing stage.

How it works - the temp-folder detail

Where a stock SaveImage writes to your output folder, this one is wired to ComfyUI's temp directory with a random _temp_ prefix (the compress_level is also set low, for speed over size). That's a deliberate choice for a batch pipeline: temp files are meant to be transient, cleaned up by ComfyUI, and grabbed by the Blender side rather than piling up in your permanent output folder. If you were expecting your renders to land neatly in ComfyUI/output, check the temp location instead - or set filename_prefix to something recognizable so you can find them.

Install

Pack-level, once:

cd ComfyUI/custom_nodes
git clone https://github.com/LatentSpaceDirective/ComfyUI-Texturaizer

or search "Texturaizer" in ComfyUI Manager and restart. No extra dependencies beyond stock ComfyUI packages, no model downloads.

When to use it

Reach for it when the render needs to be both saved and continued - a Texturaizer pass that also feeds a mask or an upscale, for instance. If you just want the image saved and the graph to stop, the stock SaveImage does the same job with friendlier output locations. And if you want the image to persist in your output folder rather than the temp area, this node's filename_prefix plus ComfyUI's format tokens is the closest you'll get without swapping in a plain SaveImage. One thing to note: because it inherits SaveImage's save logic while overriding the inputs, treat the images output as pass-through of what you put in - that's what the schema promises, and it's what the rest of your chain should assume.