SP_Name_Checkpoint

A checkpoint is the full model file - the complete set of weights that turns a prompt into an image, usually a few gigabytes on disk. Every workflow needs to load one, and ComfyUI's stock Checkpoint Loader does exactly that: pick a file, get back a model/CLIP/VAE bundle. SP_Name_Checkpoint does the opposite job - it lets you pick a checkpoint file and get back nothing but its name, as plain text, without loading anything into VRAM.

Why you'd want just the name

The obvious use is labeling: feed the filename into a Save Image node's filename prefix, or into a text overlay, so a batch of outputs from different checkpoints is self-documenting instead of a folder of identically-named files you have to cross-reference against a workflow screenshot later. It's also handy for driving logic that depends on which checkpoint is active - a switch node keyed on the name string, or a log/debug output recording exactly which model produced a given run - without paying the VRAM and load-time cost of actually loading the checkpoint through this node. If you're already loading the model elsewhere in the graph, this is a cheap parallel path to get its identity as data.

Inputs and outputs that matter

• name - a dropdown populated from your checkpoints folder. It's an enum, not free text: you're picking from whatever's actually on disk, not typing a filename by hand.
• Output: STRING - the selected filename, ready to feed into anything that wants text rather than a loaded model.

How to install it

Through ComfyUI Manager: search "SP-Nodes," install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/bananasss00/ComfyUI-SP-Nodes

Restart ComfyUI once it's cloned. No extra dependency for this node - it just reads your existing checkpoints folder.

Common issues & troubleshooting

The dropdown is empty. That means ComfyUI can't find any files in your checkpoints folder - check models/checkpoints actually has something in it, and restart ComfyUI if you added files while it was already running, since the folder is scanned at startup.

The name doesn't match what another node expects. If you're feeding this string into something that wants a specific format (with or without a file extension, with or without a subfolder prefix), check what this node actually outputs versus what the receiving node wants - a mismatch here is a string-formatting issue, not a sign either node is broken.

Confusing this for a model loader. Worth saying plainly since the category (ModelName) and the sibling nodes around it can blur together at a glance: this node never loads the checkpoint into memory. If your workflow needs the actual MODEL/CLIP/VAE outputs, you still need a real Checkpoint Loader somewhere in the graph - this node only ever gives you the filename as text.