LORA Select (Uni)

LORA Select (Uni) is the Unified Loader-flavored version of the pack's LoRA selector: a dropdown over your loras folder with a none option prepended, outputting the chosen filename as a string. It exists so the Unified Loader's LoRA choices can live outside the loader, visible and swappable.

The "Uni" difference matters more here than on some other selectors because of the off-switch. A plain LORA Select only offers real files - fine when a LoRA must always be present. The Uni variant lets you set none to explicitly run without a LoRA, which is exactly the semantic a combined loader wants when it's branching between "with LoRA" and "plain" runs.

How it works

Standard PG selector skeleton: at import it scans folder_paths for the LoRA list (loras, with lora and lora_models fallbacks) and freezes the dropdown. process() returns your pick on the lora_name output. No loading, no patching, no strength - a LoRA can be hundreds of megabytes, and this node touches none of them. The filename travels; the Unified Loader (or any name-based loader) does the work.

If you're pairing it with the pack's LoRA bridge toolkit instead - the LoRA Bridge Loader and its hook/merge family - note the bridge has its own dropdowns and a single LORA_BRIDGE output, so it doesn't consume this node's string. This selector's natural home is the Unified Loader's LoRA-aware workflows.

The input and output

• lora_name - dropdown over LoRA files, default none.
• Output: lora_name - the filename string.

Install

Part of 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. Under PG/Select/UniLoader. No dependencies.

Common issues

• New LoRA not listed. Dropdowns build at import - restart ComfyUI after adding a .safetensors to models/loras.
• Won't plug into a MODEL or CLIP input. It's a string. It feeds name-based inputs, not model inputs. If the wire is red, that's the reason.
• none breaks a plain loader. Some non-Uni loaders can't handle a none string. That's why the plain LORA Select exists - pick the variant that matches your loader.

Selector nodes are the unglamorous filler of the PG pack, and this one is no exception - but the Uni variant's explicit off-switch genuinely earns its keep in combined workflows. If you route LoRAs through the Unified Loader, it's the tidy way to keep the choice in one place.