Nodes/ComfyUI-JNK-Tiny-Nodes/Load Checkpoint Model with Name JNK
ComfyUI Node

Load Checkpoint Model with Name JNK

The 'with Name' node that actually loads

By AljnkΒ·Created about a year agoΒ·Updated 12 months agoΒ· 3
Load Checkpoint Model with Name JNK
    • model
    • clip
    • vae
    • name
    β—„modelβ–Ύβ–Ί

    Here's a plot twist: of the pack's three "with Name" nodes, this is the only one that genuinely loads a model. Load LoRA with Name and Load UNet Model with Name are name-only nodes wearing loader costumes - this one does the real work. It loads a full checkpoint (the model, its CLIP, and its VAE - the standard triplet) and hands you the checkpoint's clean basename as a string, so you can record which model produced your output without any extra bookkeeping.

    The mechanism is exactly the core loader under the hood: comfy.sd.load_checkpoint_guess_config, the same function ComfyUI's own Load Checkpoint node uses. Nothing exotic, no special handling - it loads the checkpoint, guesses the architecture config, and returns (model, clip, vae, name) where name is the filename with folder and extension stripped. Because it's a real loader, the load cost and VRAM footprint match the core node. The only difference is the extra string output.

    Inputs and outputs

    • model - dropdown of checkpoints in ComfyUI/models/checkpoints/, subfolders included.

    Outputs:

    • model - the loaded MODEL, ready for a sampler.
    • clip - the CLIP for text encoding.
    • vae - the VAE for decoding.
    • name - basename without extension (e.g. dreamshaper_8_sdxl), for filenames and metadata.

    Installing it

    Pack install: search JNK in ComfyUI Manager, or

    cd ComfyUI/custom_nodes/
    git clone https://github.com/Aljnk/ComfyUI-JNK-Tiny-Nodes.git
    

    No extra dependencies - it's core loading machinery plus a string slice.

    Where people get burned

    The main trap is assuming the other "with Name" nodes work like this one. They don't. If you wire Load LoRA with Name expecting a loaded LoRA, or Load UNet Model with Name expecting a loaded UNet, you'll get strings and a confusing error. This checkpoint variant is the one where the name isn't a lie. The other thing to keep in mind: it's a full checkpoint loader, so it's just as slow and heavy as the core one. If you only need the name for bookkeeping and you're loading the checkpoint elsewhere, you don't want this node too - it'd load the whole thing twice. Use it as your loader, and the name output is a freebie that makes your save pipeline self-documenting.

    CategoryπŸ”§ JNK

    Inputs (1)

    NameTypeDefaultDescription
    modelCOMBO0 options:

    Outputs (4)

    NameTypeDescription
    modelMODELβ€”
    clipCLIPβ€”
    vaeVAEβ€”
    nameSTRINGβ€”