Anymatix Triple CLIP Loader

Some diffusion models don't take a single prompt encoder - they want two, or three, and the text prompt gets split across them. ComfyUI ships a dual loader for the two-encoder architectures, but when a workflow needs three text encoders merged into one CLIP object, you're past what stock ComfyUI hands you. AnymatixTripleCLIPLoader loads three separate text-encoder checkpoints and stacks them into a single CLIP that one text-encode node reads from. It's the three-seat version of the loader family, and the one you'll meet most often in exported workflows that ComfyUI's own loader doesn't cover.

Mechanically it's short and honest: three string inputs resolve against your text_encoders folder, and a single call to comfy.sd.load_clip() gets all three paths (plus the embeddings directory). ComfyUI's dual loader is the same call with two files; this is just the arithmetic extended. The node hands you one CLIP output, which plugs into a standard CLIP Text Encode node - downstream, nothing knows or cares that the CLIP was assembled from three parts.

The string-input thing again

Like every loader in this pack, the three inputs (clip_name1, clip_name2, clip_name3) are plain STRING paths rather than dropdowns. That's the Anymatix design, and it's worth internalising because it's the answer to "why does this loader exist at all": the pack serves a desktop app that addresses models by URL. A workflow says "these three encoders," fetcher nodes download them on demand - possibly after the graph was written - and each loader strips its path to a basename and loads. A dropdown of existing files can't express a file that hasn't been downloaded yet; a string can. You can still drive it by hand - type three filenames, or wire in paths from anywhere.

One difference from the Anymatix dual loader worth noting: this one has no type or device selector. It resolves everything under text_encoders and just loads, so the model files need to live there (or in whatever your extra_model_paths.yaml maps to it).

Install

Under the "Anymatix" category in anymatix-comfy-nodes. ComfyUI Manager: search "anymatix-comfy-nodes", install, restart. Or:

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

Restart after. No Anymatix app needed - the pack's whole reason for being published is that exported workflows open in a stock ComfyUI.

Practical notes

Order matters: the encoders merge in the order you wire them, so don't reorder the names from a workflow you're reproducing. And because everything resolves by basename, keep the three files uniquely named or the wrong encoder can win. If you see a CLIP error on load, it's usually one of the three paths being wrong or missing - check the fetchers ahead of it before you suspect the merge.