Save Bytes Bridge (Non Output) (Yogurt Nodes)

YogurtSaveBytesBridgeNonOutput is the mid-pipeline version of the pack's YogurtSaveBytesBridge. Same job - take raw BYTES, write it to disk, hand you the path - but it's explicitly not flagged as an output node, which is the pack's way of saying "this is a save checkpoint, not the end of the story."

The inputs are identical to its sibling: bytes_data, output_dir (blank = ComfyUI's output folder), filename_prefix (supports %date:yyyy-MM-dd% formatting), overwrite, suffix (.pkl, .dat, .bin, or "Custom"), and custom_suffix. Outputs: bytes_data passes through, plus path for the file's location.

When the NonOutput version wins

Use it when you want to snapshot state without interrupting a branch. A couple of real cases:

• Checkpointing serialized data at the halfway point of a long pipeline - if the run dies later, the pickle is already on disk.
• Saving a debug copy of the bytes a node produced, then letting the same bytes continue to the real consumer.
• Writing intermediate files in a loop where you don't want a terminal node gumming up the batch.

The distinction between the two save nodes is mostly bookkeeping - the "Output" twin is flagged as a terminal, this one isn't - but if you're placing saves inside a larger graph, the NonOutput version reads truer to what it does: a side-effect along the way, not a destination.

Install

Part of ComfyUI-YogurtNodes. ComfyUI Manager → search ComfyUI-YogurtNodes → install, or:

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

Restart ComfyUI, look under "Yogurt Nodes". No model downloads, no keys.

Gotchas match its sibling: watch overwrite (off means later writes won't clobber earlier files, so the path output shifts as filenames get uniqued), and remember that a bytes node can only save things that arrive as BYTES - if your data is an IMAGE or a dict, route it through the right serializer first.