Diffusers Pipeline Loader

This is the entry door into a completely different loading path than the one ComfyUI ships with. Instead of reading a .safetensors checkpoint through ComfyUI's own comfy.sd machinery, Diffusers Pipeline Loader hands the file off to HuggingFace's diffusers Python library and gets back a live diffusers pipeline object - the same object type you'd get calling StableDiffusionPipeline.from_pretrained() in a plain Python script. That's the whole point of the pack: it's not trying to out-load ComfyUI's native checkpoint loader, it's building the on-ramp that everything downstream in ComfyUI-Diffusers needs, most importantly the StreamDiffusion real-time nodes, which are built directly on top of diffusers pipelines and don't know how to talk to a native ComfyUI model.

Why you'd reach for it

If all you want is a normal txt2img workflow, use ComfyUI's built-in Load Checkpoint - it's faster, better supported, and every other pack in the ecosystem expects a native MODEL/CLIP/VAE trio. You reach for this node specifically because you're building a graph that ends in a StreamDiffusion node, or because you're deliberately working with a diffusers-format pipeline for some other reason (custom scheduler behavior, matching a Python reference implementation exactly). It's a means to an end, not a general-purpose replacement.

The inputs and outputs that matter

There's exactly one input: ckpt_name, a dropdown of available checkpoints. It outputs three separate objects that the rest of the pack pulls apart and reassembles:

• PIPELINE - the loaded diffusers pipeline, feeds into Diffusers Scheduler Loader and Diffusers Model Makeup.
• AUTOENCODER - the pipeline's VAE, pulled out so it can be swapped or fed into Model Makeup separately.
• SCHEDULER - the pipeline's default sampling scheduler, same idea - pulled out so you can override it.

Nothing gets sampled here. This node's whole job is unpacking a checkpoint into its three moving parts so the next nodes in the chain - Diffusers VAE Loader, Diffusers Scheduler Loader, Diffusers Model Makeup - can swap any of them out before reassembly.

How to install it

Easiest path: ComfyUI Manager → Install Custom Nodes → search ComfyUI-Diffusers → install → restart. Manual path, same result:

cd ComfyUI/custom_nodes
git clone https://github.com/Limitex/ComfyUI-Diffusers.git
cd ComfyUI-Diffusers
pip install -r requirements.txt

That's enough to get this node and the rest of the plain Diffusers family working. If you're headed toward the StreamDiffusion nodes too, the README has you go further - clone cumulo-autumn/StreamDiffusion inside the node folder and run its TensorRT installer - but Pipeline Loader itself doesn't need any of that. Restart ComfyUI either way.

Common issues & troubleshooting

"Missing node type: DiffusersPipelineLoader" on a shared workflow. This is the most common failure mode for this whole pack - someone shares a workflow, you don't have the pack installed, and ComfyUI just reports the class name with no hint of which repo it came from. One user hit this exact wall with a sibling node in the pack (DiffusersVaeLoader) and had to search the web to figure out it came from Limitex's repo at all. If you see any node prefixed Diffusers* reported missing, this is almost always the pack.

Empty dropdown / no checkpoints show up. The loader reads from ComfyUI's checkpoints folder like the native loader does - if it's empty, double check your model actually landed in models/checkpoints and that you restarted ComfyUI after adding it (a refresh in the UI isn't always enough to pick up a brand-new file).

It loads but the rest of your graph won't connect. The PIPELINE/AUTOENCODER/SCHEDULER outputs are diffusers-specific types - they will not plug into a native KSampler, VAE Decode, or any non-Diffusers-pack node. If you're mixing this loader into an otherwise-native graph expecting it to slot in like Load Checkpoint, that's the mismatch. Stay inside the Diffusers/StreamDiffusion node family once you start here, or go back to the native loader if you don't actually need diffusers or StreamDiffusion specifically.