Save H3 RefMods

Extract and the loaders can save files on their own, but there's an awkward ComfyUI reality: output only happens when something downstream actually executes. Save H3 RefMods exists so you can persist a RefMod bundle without connecting a Preview, sampler, or any other consumer to make the graph run. You hook up Extract / Master / Loader → Save H3 RefMods, queue the workflow, and the bundle lands on disk - the Save node is itself an execution output, so its own sockets can stay unconnected and the run still completes.

It's a genuinely useful little thing when you're building a reference library: you can save mods as a side effect of a workflow whose real output you don't care about, without pretending you want an image preview.

How it works

The node walks the bundle and writes each distinct mod once - repeated copies of the same mod (say, from a loader's copies setting) don't duplicate files. Distinct mods that collide on the same name get numbered suffixes (name, name_2, ...) within the bundle so nothing silently overwrites. Existing destination files are replaced, using atomic file replacement so a crash mid-write doesn't corrupt the file. Loader strengths stay in the returned bundle; they are not baked into the saved latents, which the node's own description calls out - the file stores the latent and its config, and strength remains a runtime concern for Apply.

Inputs are short:

• mods - the bundle to save (from a loader, extractor, or Master).
• filename_prefix - prepended to each mod name.
• subfolder - relative to the configured RefMod storage root (models/refmods by default or your extra_model_paths.yaml root).

Outputs are mods (the bundle, now carrying resolved paths) and saved_paths (a string listing every file written - handy to wire into a text display or log). The node reports the written paths to the console too.

Install

ComfyUI Manager (search "ComfyUI-MiniMaxH3Mod") or:

cd ComfyUI/custom_nodes
git clone https://github.com/Luisacaotica/ComfyUI-MiniMaxH3Mod

Restart; deps are light (safetensors, numpy, Pillow). No model downloads from the pack - you need H3 weights + its VAE in a current ComfyUI to have anything meaningful to save (and H3's licence excludes the US, EU, UK and Korea from local weights).

Common issues

The classic mistake is double-saving: if your extractor still has save on and you also route it into Save H3 RefMods, the file gets written twice. Set the extractor's save=False and let the Save node handle persistence. Also remember ComfyUI's output-node cache: it may reuse cached results when inputs haven't changed, so don't be confused when an identical re-queue doesn't visibly rewrite files. And if you saved with a subfolder, loaders list it as folder/name - refresh the node definitions before hunting for it in the dropdown.