Enviral Checkpoint Name

Load Checkpoint's ckpt_name dropdown is one of the most useful menus in ComfyUI and one of the most annoying when you want automation. It's a fixed combo - a string from another node can't be wired into it. So every workflow that needs "swap checkpoint based on some earlier decision" ends up duplicating loader nodes or using hacky workarounds.

Enviral Checkpoint Name is the adapter that closes that gap. It gives you a dropdown of your current checkpoints, but it also accepts a linked string - from ComfyUI's built-in Custom Combo node, from a text splitter, wherever - and converts it into the exact native combo type Load Checkpoint expects on its ckpt_name input.

How it works

The dropdown enumerates folder_paths.get_filename_list("checkpoints"), so it reflects every checkpoint ComfyUI currently knows about, including paths from extra_model_paths.yaml. If you feed it a string instead of picking from the list, it resolves it leniently:

• exact name match first
• then case/path-normalized comparison
• then a unique path-suffix match, so a bare filename can resolve even if your full path has folders

If nothing matches cleanly, validation fails before the downstream loader runs and you get a "closest matches" suggestion in the error. That fail-fast behavior is the nice part - a wrong checkpoint name surfaces as a clear message, not as a silently-broken graph.

Input and output

• ckpt_name - the dropdown or linked string; empty default until you set it.
• Output ckpt_name - native combo, straight into Load Checkpoint.

That's the entire node. One in, one out.

Install

It's in the Enviral Design Node Pack. ComfyUI Manager: search "Enviral Design Node Pack". Or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/EnviralDesign/comfyUI-enviral-design-node-pack

then restart ComfyUI. No models, no extra dependencies.

When it earns its place

If you hardcode one checkpoint per workflow, you don't need this. It pays off the moment you build graphs that branch - a "pick your style" Custom Combo node feeding both this and Enviral Diffusion Model Name, so the whole loader chain follows one choice. It's also handy for batch workflows that iterate over a list of checkpoints via a text splitter: split the names, feed each part through, and let the node normalize them into valid combos. Saved workflows stay readable because the socket layout never changes.