Load CLIP

The no-frills member of Sage's *FromInfo loader family: hand it a clip_info bundle, get back a loaded CLIP model. No special tokenizer tweaks, no architecture-specific handling - that's what makes it the one to reach for by default.

Where it sits in the pack

Sage Utils builds its loaders around a shared metadata bundle: a checkpoint gets loaded through one of the pack's metadata-aware loaders, hashed, matched against Civitai when possible, and cached locally (the README documents this cache living in sage_cache_hash.json / sage_cache_info.json under comfyui/user/default/SageUtils/). From that bundle, separate small nodes each pull one piece - this one for CLIP, Sage_VAELoaderFromInfo for the VAE. There's also a specialized sibling, Sage_ChromaCLIPLoaderFromInfo, which does the same job but applies Chroma-specific T5 tokenizer settings on top. Use that one only if you're actually running Chroma; use this plain version for everything else.

Inputs and outputs

One input, clip_info (the MODEL_INFO-family bundle), one output, clip - ready to feed into whatever text encoder node your workflow uses next, whether that's a stock CLIP Text Encode, Sage_CombineCLIPTextEncode, or Sage_DualCLIPTextEncodeLumina2. There's nothing to configure here beyond the connection itself, which is the point - it's meant to be an invisible link in the chain, not something you fiddle with.

The reason this is worth using over a stock CLIP loader at all, even when you don't need Chroma's special handling, is consistency: routing every load through the same *_info bundle means your whole graph - model, clip, vae - traces back to one hash-verified source, and any metadata node downstream can report on the exact model/clip/vae combination that actually produced an image instead of you having to remember it.

Installing it

Through ComfyUI Manager: search Sage Utils, install, restart. Manually:

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

Restart ComfyUI afterward. Nothing extra to download for this node - it loads whatever CLIP component your checkpoint already provides.

Common issues

If the load comes back empty or errors, the problem is almost always upstream in clip_info rather than in this node - it needs to be a genuinely populated bundle from a Sage metadata-aware loader, not an unconnected input or something assembled by hand.

The one mix-up worth flagging explicitly: if you're loading a Chroma checkpoint and getting inconsistent results, this isn't the node you want - Chroma needs a specific T5 tokenizer tweak (minimum padding, minimum length) that only Sage_ChromaCLIPLoaderFromInfo applies. This plain loader will happily load Chroma's CLIP component without complaint; it just won't apply that fix, so if you're chasing subtly-off Chroma output, check which of the two loaders you actually used.