Checkpoint Select (Uni)
A filename dropdown made for the Unified Loader
- chkpt_name
Checkpoint Select (Uni) is a dropdown over every file in your checkpoints folder that outputs the chosen filename as a string - with a none option prepended. That none and the (Uni) suffix are the whole story: this is the variant tuned for the pack's Unified Loader, which expects its model slots to be able to say "no model here."
If that sounds trivial, that's because it is. The entire PG selector family exists to pull model-choice widgets out of loader nodes so the choices live in one visible place. The "Uni" flavor adds the explicit off switch.
How it works
At import, it asks folder_paths for the checkpoint list and builds the dropdown. process() returns the selection unchanged on the chkpt_name output. Nothing loads - a checkpoint can be multiple gigabytes, and this node never touches any of them. It's a string handoff, full stop.
The practical pattern is "select-then-load": this node picks the name, the Unified Loader consumes it and does the actual work. Because the Uni variant includes none, you can also use the dropdown as a master switch - flip to none and the loader skips loading a checkpoint entirely, which is handy in combined workflows where the model comes from a diffusion UNet slot instead.
The input and output
chkpt_name- dropdown overcheckpointsfiles, defaulting tonone.- Output:
chkpt_name- the selected filename as a string.
Install
Ships with PG Nodes:
ComfyUI Manager → search "PG Nodes" → Install → restart
Manual: git clone https://github.com/GizmoR13/PG-Nodes into custom_nodes (folder named PG-nodes), restart. It lives under PG/Select/UniLoader. No dependencies.
Common issues
- Checkpoint not listed. The list snapshots at import. Restart ComfyUI after dropping a new
.safetensorsintomodels/checkpoints. - Output won't plug into a MODEL input. Correct - it's a string filename. Route it to a loader's name input, not a model input.
- Forget which variant you're on. The plain
Checkpoint Select(no Uni) omitsnoneand is meant for loaders that require a real selection. Use the Uni one when the loader has its own off-switch.
It's a convenience layer over a convenience. If you already set your checkpoint directly in the loader, you don't need it. If you're building a workflow where one visible dropdown should control what gets loaded, this is the knob.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| chkpt_name | COMBO | none | 1 options: none |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| chkpt_name | none | — |