Preview Image Bridge (Output) (Yogurt Nodes)

YogurtPreviewImageBridgeOutput is the "Output"-suffixed twin of YogurtPreviewImageBridge, and if you compare their schemas you'll find they're identical. Same single input, same four outputs. The difference is intent: this is the one the pack names for the end of the image branch, the "we're done with this image, show me what it looks like" spot.

• images in - the IMAGE tensor.
• images out - passes through unchanged.
• width, height, batch out - dimensions and batch count as integers.

Since it passes the image through instead of consuming it, it behaves like the plain preview bridge mid-graph too. Which one you use is honestly a matter of taste and graph readability - the pack ships both so you can name the end point of a branch without reaching for a generic save node.

What it's actually for

The pass-through preview pattern exists because ComfyUI's own preview node ends the line. If you want a final visual check before a save node, or you want the last decoded image in a chain to be visible in the UI without stopping the flow, this node is the cleaner read. And like its sibling, the width/height/batch outputs are genuinely useful - feed them into a subsequent crop or a captioning step instead of assuming dimensions.

Install

Same pack, same steps as everything in ComfyUI-YogurtNodes:

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

or install ComfyUI-YogurtNodes via ComfyUI Manager and restart. It lives under "Yogurt Nodes", display name "Preview Image Bridge (Output) (Yogurt Nodes)". No model downloads.

If you're staring at both preview bridges wondering which to place: put the plain one anywhere you want eyes mid-pipeline, put this one at the end of the branch where the result is final. If you swap them by accident, nothing breaks - they're the same node under two names.