Nodes/ComfyUI-YogurtNodes/Save Image Bridge Ex (Non Output) (Yogurt Nodes)
ComfyUI Node

Save Image Bridge Ex (Non Output) (Yogurt Nodes)

Save anywhere, in any format, without the spotlight

By yogurt7771·Created 2 years ago·Updated 9 days ago· 1
Save Image Bridge Ex (Non Output) (Yogurt Nodes)
  • images
  • images
  • width
  • height
  • batch
  • saved_paths
output_dir
filename_prefixComfyUI
disable_metadatafalse
overwritefalse
suffix.png
custom_suffix
png_compression4
jpeg_quality100

Save Image Bridge Ex (Non Output) is the combination variant: all the flexibility of the Ex version - the Custom extension option - minus the "this is a workflow output" status. It's the node you reach for when you want files on disk in a format ComfyUI doesn't default to, but you don't want that save treated as a headline result by the API or the frontend.

The mechanism is simple and the naming tells you everything. "Ex" means the suffix dropdown gained a Custom choice backed by a custom_suffix field, so you can write .webp, .bmp, .tiff - anything Pillow supports. "Non Output" means is_output_node is false, so ComfyUI doesn't collect this node's result as one of the workflow's outputs. The disk write happens either way; only the API/frontend treatment changes.

Why that combination exists

Think of a pipeline that dumps .webp previews into a shared folder while the actual deliverable goes through the normal output nodes. With the plain Ex bridge you'd get the preview and watch it pollute your API response and history. With this one, the preview lands in the folder silently and the saved_paths output still tells your downstream automation exactly where it went. The passthrough outputs (images, width, height, batch, saved_paths) work identically to every other Save Image Bridge variant - the image keeps flowing through the graph after the write.

Inputs are the Ex set: images, output_dir (blank → ComfyUI output), filename_prefix with %date:yyyy-MM-dd% tokens, disable_metadata, overwrite, suffix (.png/.jpg/Custom), custom_suffix, png_compression, jpeg_quality. Remember the precedence from the tooltip: a non-empty custom_suffix overrides the dropdown.

Install

One pack, one install, all nodes - this is true for the whole Yogurt set:

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

Or through ComfyUI Manager by searching ComfyUI-YogurtNodes. Restart ComfyUI and you'll find it under Yogurt Nodes → IO. Dependencies are just numpy, pillow and requests - no models, nothing GPU-heavy.

The traps

Same two that bite every member of this family. First, Custom in the dropdown with an empty custom_suffix leaves the node with no extension - keep them paired. Second, because it's non-output, the file won't appear in ComfyUI's frontend gallery; that's expected, check the folder or the saved_paths output rather than assuming it failed. And since overwrite defaults to false, repeated runs append counters to your filenames until you flip it on.

CategoryYogurtNodes/IO

Inputs (9)

NameTypeDefaultDescription
imagesIMAGEThe images to save.
output_dirSTRINGThe directory to save the images to, leave blank to save to the ComfyUI output directory.
filename_prefixSTRINGComfyUIThe prefix for the file to save. This may include formatting information such as %date:yyyy-MM-dd% or %Empty Latent Image.width% to include values from nodes.
disable_metadataCOMBOfalseDisable saving metadata to the PNG file.
overwriteCOMBOfalseOverwrite existing files.
suffixCOMBO.pngThe file extension to save the images as.
custom_suffixSTRINGThe file extension to save the images as. If this is not empty, the suffix option will be ignored. Otherwise, the suffix option will override above suffix option.
png_compressionINT40–9The level of compression to use for PNG images.
jpeg_qualityINT1000–100The quality of the JPEG image.

Outputs (5)

NameTypeDescription
imagesIMAGE
widthINT
heightINT
batchINT
saved_pathsLIST