Superside Preview Image

The unglamorous node that keeps your workflow viewable: Superside Preview Image shows an image in the graph, and it's the in-house equivalent of core ComfyUI's PreviewImage. Same input, same preview-on-canvas behavior, one deliberate difference - it saves its previews to ComfyUI's temp folder with a random prefix instead of accumulating permanent output files. Preview to your heart's content without the output folder turning into a museum of every intermediate frame you ever looked at.

That temp-folder detail is the entire reason to care about this clone existing. Core's PreviewImage is fine, but in long production workflows - the kind this pack is built for - the output directory fills with throwaway previews. This node's whole personality is "look, then disappear."

The input and output

One input: images - connect any IMAGE tensor (or a batch; it previews the frames). The node is an output node, meaning it terminates the graph branch visually.

The output is also images, an IMAGE passthrough. It's a real tensor, not just a view, so you can wire it onward even though its job is to show the image - handy if you want a preview node in the middle of a chain rather than at the end.

How it works

It saves the input to the temp directory with a randomized filename prefix and registers it as a UI preview, exactly like core's PreviewImage does - just pointed at temp storage with a unique name so reruns don't collide. Pure local, no API, no key, instant.

Installing it

cd ComfyUI/custom_nodes
git clone https://github.com/Superside/comfyui-superside-nodes
pip install -r requirements.txt

Restart ComfyUI, find it under Superside. No configuration.

When it's worth swapping in

If your workflow's final step is a preview that you also want to save for real, use a Save node - previews in temp get cleaned up. If you're just checking your work, this node keeps your output folder clean where core's PreviewImage accumulates files. In the Superside pack, it's also the preview plumbing underneath Mask Preview, so every gray-mask preview you see in those workflows runs through this same temp-save path. Small node, small difference, and the kind of detail that keeps a thousand-run production session from drowning in files.