SaveImageWithCustomExif

This node exists to solve one specific problem: core ComfyUI's Save Image node has no idea what to do with metadata attached by CustomExif, so if you chain CustomExif into a regular save, your carefully-written EXIF string just gets dropped. SaveImageWithCustomExif is the pack's own save node - a drop-in replacement that writes whatever metadata reached it along with the image file. The README says it outright: "It is recommended to use the SaveImageWithCustomExif node to save images."

If you're not using CustomExif anywhere in your graph, you don't need this node - the core Save Image works fine on its own. This one earns its place specifically as the pairing partner for that node.

The inputs and outputs that matter

• images - the images to save, per its own tooltip.
• filename_prefix (default "ComfyUI") - the same templating you'd expect from core ComfyUI's save node: the tooltip explicitly notes it "may include formatting information such as %date:yyyy-MM-dd% or %Empty Latent Image.width% to include values from nodes," so you can build dynamic filenames pulling in the date or a value from anywhere else in your graph.

This is a terminal node - is_output_node is true, and there's no image output to wire onward. It's the end of the line.

How to install it

Search ComfyUI-HakuImg in ComfyUI Manager, or:

cd ComfyUI/custom_nodes
git clone --recurse-submodules https://github.com/licyk/ComfyUI-HakuImg

Restart ComfyUI, find it under Image → HakuImg, next to CustomExif.

Common issues & troubleshooting

Used this node but there's no custom metadata in the file. Check that a CustomExif node actually sits upstream in the chain feeding images. Without it, this node behaves exactly like a normal save - no metadata is invented for you, it just passes through whatever (if anything) is already attached.

filename_prefix template isn't substituting. Same behavior as core ComfyUI's Save Image, since the templating syntax is identical: a typo in a %date:...% or %NodeTitle.field% pattern won't error, it'll just print the literal text instead of substituting a value. Double-check the exact syntax against a working example if a filename comes out looking wrong.

Wondering whether you even need this over the core Save Image node. You only do if CustomExif is in the picture. If you're just doing standard pixel post-processing with the rest of this pack (blend, curve, chromatic aberration, and so on) and don't care about faking camera metadata, the regular Save Image node is simpler and does the same job for everything else.