☁️BizyAir Load Eva Clip (PuLID Flux)
BizyAir Load Eva Clip (PuLID Flux) — ComfyUI Node Guide
- eva_clip
This one's about as simple as a node gets - no inputs, one output - but it's worth understanding because it's a required part of the PuLID-Flux pipeline, and if you skip it your face-consistency workflow won't run at all.
PuLID is ByteDance's identity-adapter technique for putting a real face into a generation without training a LoRA, and its Flux port is the reason PuLID beat out InstantID as the go-to face tool once the ecosystem moved off SDXL - InstantID never got a Flux version, PuLID shipped one in September 2024, and that was basically the whole contest. Under the hood, PuLID-Flux's identity pipeline leans on two components to actually understand a reference face: an InsightFace-style recognition model for the biometric identity vector, and an EVA-CLIP vision encoder for richer visual features around the face. This node loads that second piece.
What it does and why it's separate
EVA-CLIP is a scaled-up CLIP vision transformer variant. In the PuLID-Flux pipeline it's used alongside the face-analysis model to extract features that get fed into the identity-injection step (BizyAir Apply PuLID Flux, the node that actually patches your model). Splitting it out into its own loader node - rather than baking it into the apply node - is a pretty standard ComfyUI pattern: it lets the cloud-side loader cache the EVA-CLIP weights once and reuse them across runs instead of reloading on every execution, and it keeps the apply node's already-busy input list from growing further.
Inputs and outputs
There's nothing to configure here. Zero required inputs, zero optional inputs. Drop the node into your graph and it's ready.
The one output is eva_clip, typed BIZYAIR_EVA_CLIP. That custom type only means one thing practically: this output is meant to plug straight into the eva_clip input on BizyAir Apply PuLID Flux. It won't connect to anything expecting a standard CLIP or CLIP Vision type - BizyAir's cloud nodes talk to each other over their own typed handles, not ComfyUI's native ones.
How to install it
Same pack, same install as every other BizyAir node - you don't install pieces of BizyAir individually.
ComfyUI Manager: search "BizyAir," click Install, restart.
git clone:
cd ComfyUI/custom_nodes
git clone https://github.com/siliconflow/BizyAir.git
Restart afterward.
You'll also need a BizyAir account and an API key set before anything actually executes - the README's install page walks through the "click to login" flow. That's true for every node in the pack, this one included, even though it looks like a no-config loader.
Building the rest of the PuLID pipeline
This node is one piece of a chain, so it's worth knowing what surrounds it even though this article isn't about those nodes directly. A working BizyAir PuLID-Flux setup needs: a BizyAir_UNETLoader for your Flux checkpoint, this EVA-CLIP loader, a face-analysis loader (not covered here, but it's the InsightFace-equivalent piece), a PuLID model loader, and finally BizyAir Apply PuLID Flux, which takes all of the above plus your reference image and patches the model before sampling. Miss one link and the apply node will just report a missing input rather than anything more descriptive.
Common issues
Because this node has no parameters, there's not much to misconfigure - the failure modes are all upstream or downstream of it. The two things actually worth watching:
Wrong type into eva_clip. If you're mixing BizyAir's PuLID pipeline with a local, non-BizyAir PuLID node pack in the same graph (there's more than one PuLID-Flux implementation floating around the ComfyUI ecosystem), don't expect this loader's output to satisfy that other pack's eva_clip input - the types won't match even if the name does.
No API key / no credits. Since this node's whole job is fetching weights server-side, an unset or expired BizyAir API key will surface as an execution failure here even though the node itself has nothing to configure - it's the simplest node in the chain to blame incorrectly when the real problem is your account, not your graph.
Inputs (0)
No inputs
Outputs (1)
| Name | Type | Description |
|---|---|---|
| eva_clip | BIZYAIR_EVA_CLIP | — |