Meld Save Image

Every ComfyUI output already gets registered in the Meld Image Manager automatically the moment a workflow finishes. So why a dedicated save node? Because Meld Save Image does the parts auto-registration can't: it saves the file and records richer metadata, tags it, and - the headline feature - infers the parent image using a perceptual hash (pHash) so your img2img and upscale chains become a visible lineage tree.

If you've ever stared at a folder of variations and wondered which one came from which, this is the node that answers it.

What it does on save

• Saves the file with a filename_prefix that supports date and dimension tokens - the default is %date:yyyy-MM-dd-HH-mm-ss%, and you can use %width%, %height%, %year%, etc.
• Registers into the Image Manager's SQLite database: file path, timestamps, resolution, file size, pHash and SHA256 hashes, prompts, the checkpoint used, and the full workflow JSON.
• Infers lineage: it computes the input's pHash and links it to the closest-matching image already in the database. That's how "this render is a child of that earlier render" gets recorded even though no one told it.
• Tag inheritance: child images can inherit the parent's tags, so a tagged img2img run keeps its labels without re-tagging every frame.

The inputs that matter

• images - what to save.
• filename_prefix - the formatting template; %date:...% is the useful one.
• extension - png or webp; quality (1–100) matters mostly for webp.
• origin_image (optional) - the source image for img2img. Connect it to make the parent link explicit instead of inferred.
• positive / negative (optional) - saved as metadata; wire them from Meld Image Loader or Meld Prompt Constructor so the record is complete.
• tags (optional) - comma-separated, e.g. girl, masterpiece.

Output is just images, passed through unchanged, so you can chain it ahead of a preview node.

Where it fits

The loop is: Meld Image Loader loads an old render and restores its settings → you tweak → Meld Save Image records the new file as a child of the old one. In the Image Manager's Detail Viewer you can inspect the prompt, model, and tags of any saved image, and the lineage view shows the family tree. That "reuse past work instead of hunting through folders" workflow is the entire point of the pack.

Installing it

Same pack, same install:

• ComfyUI Manager → search "Meld" → install, or
• comfy node install HappyOnigiri/ComfyUI-Meld, or
• cd ComfyUI/custom_nodes && git clone https://github.com/HappyOnigiri/ComfyUI-Meld.git && cd ComfyUI-Meld && pip install -r requirements.txt then restart.

This is the one Meld node whose dependencies actually do something visible: imagehash, scipy, and PyWavelets power the pHash and lineage side. No model downloads, no API keys. Privacy note - the pack deliberately reads only generation metadata, not EXIF like GPS.

Honest take: if you're a "save the PNG, sort it later" person, the automatic registration alone is enough and you can skip this node. The moment you start iterating on top of old outputs and want the history, the pHash lineage is what makes the Manager feel like a real database instead of a fancy file browser.