Anymatix CLIP Loader 2

Let's get the honest part out of the way: AnymatixCLIPLoader2 is not a different node. In the source it's literally an alias - the file that defines it reads AnymatixCLIPLoader2 = AnymatixCLIPLoader, and the pack registers both names in the node menu. Same inputs, same type dropdown with the full recipe list, same CLIP output, same path-based behavior. If you've read the AnymatixCLIPLoader article, you've read this node.

So why two menu entries for one loader? Almost certainly legacy. Node names in ComfyUI are permanent contracts - workflows save the class name, so once a name ships, you can't repurpose it without breaking every saved graph that references it. Renaming is a new node, not an edit. AnymatixCLIPLoader2 reads like a second menu slot added for a specific workflow card inside the Anymatix app, kept around so old graphs and new graphs both resolve. ComfyUI is littered with this pattern; a pack that serves an app with versioned card templates hits it more than most.

Which one should you use?

Functionally it does not matter - pick whichever is in the workflow you're editing and leave it alone. When you're building fresh, the plain AnymatixCLIPLoader is the one to reach for, if only because that's the canonical name and the one you'll see in the pack's own documentation. Don't waste time wondering whether the "2" is an upgrade; it isn't.

What it actually does (in brief)

A path-taking twin of ComfyUI's stock CLIPLoader. You give it:

• clip_name (STRING) - path or filename of the text encoder.
• type (enum) - the clip architecture: stable_diffusion, stable_cascade, sd3, mochi, ltxv, pixart, cosmos, lumina2, wan, hidream, and more, with the model-specific recipes (e.g. clip-l for SD, clip-g + t5 for sd3, umt5 for wan) listed in the node description.
• device (optional) - default or cpu.

It outputs a single CLIP that feeds your CLIPTextEncode. Because it resolves by basename against ComfyUI's model folders, a file already in models/clip or models/text_encoders loads from just a filename - or you can wire in AnymatixFetcher's path output for the URL-addressed workflows this pack is built around.

Install

Standard for the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/Anymatix/anymatix-comfy-nodes

then restart ComfyUI (or install via Manager, searching "anymatix-comfy-nodes"). No extra model downloads from the node itself.

Issues to expect

Since it's the same code as its sibling, the same two mistakes apply: mismatching the type to the actual weights, and expecting it to download a file that was never fetched. And one purely cosmetic gotcha - if you see both "Anymatix CLIP Loader" and "Anymatix CLIP Loader 2" in your node menu and wonder if you've got a corrupt install, you haven't. That's just how the pack ships.