FL Save And Display Image

The stock Save Image node has one annoying property: it's a dead end. The image goes to disk and shows a preview, but nothing comes out the other side, so if you want to also keep processing that image you need a second branch off an earlier node. FL_SaveAndDisplayImage fixes that small papercut - it saves to disk, shows the preview inline on the node, and passes the image batch through so you can wire it into whatever comes next.

That passthrough is the whole reason to use it. It turns "save the final result" into "save a checkpoint mid-graph." Want to see and archive the raw generation and then upscale it, and then save that too? Drop one of these after the sampler and another after the upscale. Each one gives you a saved file, an on-node preview to eyeball, and the image still on the wire heading downstream. No branching, no re-routing from three nodes back.

The inputs and outputs

It's deliberately minimal. Two inputs:

• images (IMAGE) - the batch to save and show.
• filename_prefix (default ComfyUI) - the name stub for the files on disk. It writes into your ComfyUI output directory using the standard save path, so numbering and .png extension are handled for you. Set this to something meaningful per branch ("raw", "upscaled") and your output folder stays readable.

One output:

• images (IMAGE) - the same batch, untouched, ready to feed the next node.

Because it uses ComfyUI's normal SaveImage machinery under the hood, the files land where all your other saves do and behave like any other output - nothing exotic to learn.

Installing it

FL_SaveAndDisplayImage comes with ComfyUI_Fill-Nodes. Easiest is ComfyUI Manager: search Fill-Nodes, install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/filliptm/ComfyUI_Fill-Nodes

then restart ComfyUI. No model download - it's a plain save/preview node.

When to reach for it

Any time you'd otherwise be squinting at a Preview node next to a Save node next to a reroute. This collapses all three jobs into one and keeps the graph linear. It's genuinely nice for iterative work where you want an archived snapshot at each stage rather than just the final frame. The only thing to keep in mind: it saves every time the graph runs, so if you scatter a dozen of these through an experimental workflow you'll accumulate a lot of files fast. Prune the prefixes to the stages you actually care about, or clear your output folder now and then. That's the extent of the "gotcha" - it does exactly what the name says and gets out of your way.