SaveImageLazy (🚫Deprecated)

Lead with the important part: easy saveImageLazy is deprecated. The pack itself files it under its "🚫 Deprecated" category and marks the node name accordingly. It still exists so old workflows that reference it don't break, but you shouldn't reach for it in anything new - the pack's maintainer has moved image saving elsewhere. If you found this because a downloaded workflow uses it, it'll still run; if you're building fresh, use one of the alternatives below.

What it did

The "lazy" in the name is the interesting bit. A normal ComfyUI SaveImage node is a terminal output - it's the end of a wire, it writes the file, and nothing continues past it. saveImageLazy was built to save the images and pass them through, so you could write a file partway down a graph and keep processing the same images afterward. That's genuinely useful when you want an intermediate checkpoint saved - say, the base render before an upscale - without breaking the chain or duplicating the branch.

The inputs and output

• images - the images to write.
• filename_prefix - the prefix for the saved filename (default ComfyUI).
• save_metadata - whether to embed the workflow metadata into the PNG. Default true, which is the ComfyUI convention: the graph that made the image is stored inside the image, so anyone can drag it back into ComfyUI and reconstruct the workflow. Turn it off only if you deliberately don't want to ship your workflow with the file.
• Output: images - the same images, passed through so you can keep working with them downstream.

How to install it

The node comes with the pack, though again - deprecated, so this is really for keeping an old workflow alive. Install Easy-Use via ComfyUI Manager ("ComfyUI Easy Use") or:

cd ComfyUI/custom_nodes
git clone https://github.com/yolain/ComfyUI-Easy-Use

Then install.bat / pip install -r requirements.txt, restart. Preinstalled on comfy.icu.

What to use instead

For the common case - save the final image - Easy-Use's samplers already handle it. Every easy kSampler, easy kSamplerTiled and friend has an image_output widget with Save and Hide&Save options, so the save happens right in the sampler with no extra node. That's the intended path now.

If you specifically want the pass-through behavior (save an intermediate, keep processing), the pack's easy imageSave node covers that ground with date formatting and other options, and plain ComfyUI SaveImage covers the terminal case. Between the sampler's built-in save and imageSave, there's no gap saveImageLazy fills that isn't handled better elsewhere - which is presumably why it got deprecated.

Common issues

The only real "issue" is using it at all in a new workflow. Deprecated nodes get no further fixes and can be removed in a future release, so anything you build on it is on borrowed time. Migrate to the sampler's image_output=Save or to easy imageSave.

If you're keeping an old workflow running and it works, it works - no need to panic. Just know that if it one day stops loading after a pack update, the node going away is the likely reason, and the fix is swapping in a current save node rather than trying to resurrect this one. And whichever save node you land on, leave save_metadata on if you value the embedded-workflow convention - it's how the community shares reproducible setups by sharing the PNG itself.