Save 4 hours! We auto-setup your workflow! Free!

Drop your workflow.json — we handle every dependency, custom node, and model. Just open the link and run.

Auto-Setup Workflow Json (Free) Now!
ComfyUI > Nodes > FunUI > FunUI CLIP Loader

ComfyUI Node: FunUI CLIP Loader

Class Name

FunUICLIPLoader

Category
FunUI/Loaders
Author
digital-garbage (Account age: 1276days)
Extension
FunUI
Latest Updated
2026-11-03
Github Stars
0.02K

How to Install FunUI

Install this extension via the ComfyUI Manager by searching for FunUI
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter FunUI in the search bar
After installation, click the Restart button to restart ComfyUI. Then, manually refresh your browser to clear the cache and access the updated list of nodes.

Visit ComfyUI Online for ready-to-use ComfyUI environment

  • Free trial available
  • 16GB VRAM to 80GB VRAM GPU machines
  • 400+ preloaded models/nodes
  • Freedom to upload custom models/nodes
  • 200+ ready-to-run workflows
  • 100% private workspace with up to 200GB storage
  • Dedicated Support

Run ComfyUI Online

FunUI CLIP Loader Description

Loads single or multiple text encoders, including mixed GGUF files, with CPU offloading.

FunUI CLIP Loader:

FunUICLIPLoader loads the text encoders that allow your generation workflow to understand written prompts. A text encoder turns words into numerical information that an image or video model can use to guide generation; this node prepares that encoder rather than encoding your prompt or generating images itself. It can load one encoder file or combine several files in a defined order, supporting model families that require multiple text-encoding components. It also supports GGUF encoders, including combinations of GGUF and ordinary encoder files, and detects GGUF containers even when their filenames do not identify them correctly. You can keep the encoder on the CPU to leave more GPU memory available for generation, with a trade-off in prompt-processing speed. The node checks for unavailable encoder families, missing files, and unsuccessful loading so that configuration problems can be identified before prompt encoding begins.

FunUI CLIP Loader Input Parameters:

clip_name1

Required COMBO selection for the first text encoder file. Its options come from the encoder-file list available to the node, so the actual filenames depend on your installation rather than a fixed list in the source. This is the primary encoder slot and is loaded before any additional selected files. Choose an encoder intended for the model family you are using; a file being available in the dropdown does not guarantee that it is compatible with your model. Standard encoder files are resolved through ComfyUI’s configured text-encoder locations, while GGUF files use the node’s GGUF-aware file resolution. No explicit default is declared for this parameter, and numerical minimum and maximum values do not apply.

type

Required COMBO selection identifying the model family for which the encoder files should be loaded. The available options are supplied dynamically by the node’s encoder-family helper rather than hard-coded in this class; the source explicitly identifies ltxv for LTX-2 and minimax for MiniMax H3, and the supplied general pipeline uses stable_diffusion. The default is ltxv when that option is available; otherwise, it is the first available family, or stable_diffusion if the family list is empty. This setting controls how ComfyUI interprets the selected encoder files, so it must match the intended model family rather than being treated as a style or quality setting. An unknown family causes an explicit error instead of silently falling back to another family. Numerical minimum and maximum values do not apply.

clip_name2

Optional COMBO selection for a second encoder file. The options are an empty string, meaning no file in this slot, followed by the same available encoder-file choices used for the first slot. The default is the empty string. Use this slot only when your model’s text-encoder setup requires another component; selecting more files does not automatically improve prompt understanding or image quality. When populated, this file is loaded after clip_name1 and before files in later slots. It can contain a standard encoder component or a GGUF encoder, and mixed GGUF and non-GGUF selections are supported. Empty slots are skipped rather than treated as validation failures. Numerical minimum and maximum values do not apply.

clip_name3

Optional COMBO selection for a third encoder file, with an empty string plus the available encoder filenames as its options. Its default is the empty string, and numerical minimum and maximum values do not apply. This slot extends the ordered encoder-file selection for model configurations that need another component. When populated, its file is loaded after the populated earlier slots and before clip_name4. Leaving it empty does not prevent another populated slot from being processed, but you should still follow the file order prescribed for your model. Keep this slot empty when your encoder setup does not require it, because the node passes all selected files to the loader rather than treating additional files as optional enhancements.

clip_name4

Optional COMBO selection for a fourth encoder file. Its options are an empty string and the available encoder filenames, and its default is the empty string. Numerical minimum and maximum values do not apply. This is the final encoder slot exposed by the node and is processed after all populated earlier slots. Use it only when the intended model configuration requires a fourth component, preserving the required component order. Like the other optional slots, it can remain empty without causing a validation failure, and its selected file participates in the same combined text-encoder loading operation rather than creating a separate encoder output.

device

Optional COMBO selection with exactly two options: default and cpu. The default is default, which leaves device placement to ComfyUI’s normal management rather than explicitly forcing the encoder onto a particular device. Selecting cpu sets both the encoder’s load device and offload device to the CPU, keeping it off the GPU and leaving more VRAM available for the diffusion model. This can help when GPU memory is limited, but prompt processing is slower and the encoder still requires system memory. The setting controls where the encoder runs, not which model family is used or how many files are loaded. Numerical minimum and maximum values do not apply.

FunUI CLIP Loader Output Parameters:

clip

A CLIP object containing the loaded text-encoder configuration assembled from the selected files in slot order. In ComfyUI, this object supplies the text-encoding capability that downstream nodes use to convert your prompt into conditioning information for generation; it is not an image, a prompt string, or already encoded conditioning. Connect it to a compatible text-encoding node such as CLIPTextEncode. The supplied FunUI pipelines connect this same output to both positive and negative prompt-encoding nodes. The CLIP output represents the combined encoder setup even when several files were selected, and loading also uses ComfyUI’s configured embeddings directories. If the loader cannot produce a recognized encoder, the node raises an error instead of returning an unusable empty CLIP value.

status

A STRING containing a readable summary of a successful load. Its first line follows the pattern FunUI CLIP Loader | type=ltxv device=default, with the selected family and device setting substituted as appropriate. Subsequent lines list the loaded filenames in a numbered sequence, making it useful for checking which files were used and in what order. When GGUF files are involved, the text also includes notes returned by the GGUF loader and any warning that a file named as a safetensors file is actually a GGUF container. The device entry records the selected setting; device=default does not identify the exact hardware chosen by ComfyUI. This output is informational rather than generation conditioning, and it is returned only after loading succeeds.

FunUI CLIP Loader Usage Tips:

  • Match the encoder files and type to your generation model. For example, the supplied LTX pipeline selects ltxv, while the supplied general pipeline selects stable_diffusion. Do not rely on the node’s default family being correct for every workflow.
  • Start with only the encoder files your model requires. Leave clip_name2, clip_name3, and clip_name4 empty unless the model’s setup instructions call for additional components.
  • Preserve the recommended file order in multi-file setups. The node processes populated slots from clip_name1 through clip_name4; it does not automatically rearrange files into a model-specific order.
  • Use device=cpu when you need to reserve GPU memory for the diffusion model. Keep device=default when you want ComfyUI to manage placement normally and avoid deliberately forcing CPU prompt processing.
  • You can combine GGUF encoder files with standard encoder components in the same node. The source specifically accommodates a GGUF encoder paired with a safetensors connector, but the files must still form a compatible setup for the selected family.
  • Connect clip to the clip input of CLIPTextEncode or another compatible prompt-processing node. If your workflow uses both positive and negative prompts, both text-encoding nodes can use the same loaded CLIP object.
  • Inspect status when checking a saved workflow or troubleshooting file selections. It confirms the selected family, device setting, loaded-file order, and any GGUF-specific notes.

FunUI CLIP Loader Common Errors and Solutions:

FunUI CLIP Loader: pick at least one text encoder file.

  • Explanation: No nonempty encoder filename reached the loading stage. Although the first slot is required in the interface, an incomplete or programmatically constructed workflow can still reach this check.
  • Solution: Select a valid file in clip_name1 and run the node again. Leave only the unused additional slots empty.

FunUI CLIP Loader: this ComfyUI has no encoder family '…'. Known families: …

  • Explanation: The selected family name does not correspond to a family supported by the installed ComfyUI runtime. This can happen when a saved workflow refers to a family that was renamed or is unavailable in your current installation.
  • Solution: Select the correct supported family from the current type dropdown. If your model requires a family that is absent, check its ComfyUI version requirements and update the installation as needed rather than substituting an unrelated family.

… is no longer where it was listed from.

  • Explanation: A selected GGUF file appeared in the available-file list, but the node could not resolve its location when execution began. The file may have been moved, renamed, deleted, or stored on a drive that is no longer available.
  • Solution: Restore access to the file or select its current entry from the refreshed encoder list. Check that any external or network drive containing it is connected, then rerun the node.

Could not load a text encoder from … as type '…'.

  • Explanation: The underlying loader returned no recognized encoder for the selected files and family. The filename list and family in the message identify the configuration that failed.
  • Solution: Check that the files are text-encoder components for your intended model, confirm type, and verify the required component count and order. Remove unrelated files and replace any incomplete or incorrect downloads with the recommended encoder files.

Encoder file not found or inaccessible

  • Explanation: Standard encoder files are resolved through ComfyUI’s configured text-encoder paths, and a missing or inaccessible file causes the underlying path resolver to raise an error. The exact message is not specified in this node’s source.
  • Solution: Confirm that the selected file still exists in a configured text-encoder location and is readable by ComfyUI. Refresh the file selection after moving or renaming files, and check folder permissions if the file exists but cannot be opened.

GGUF loading or encoder-file reading error

  • Explanation: GGUF support and ComfyUI’s file readers can raise their own errors when they cannot read or interpret a selected file. This node does not define fixed messages for those failures; possible causes include damaged downloads, incompatible encoder contents, or an unavailable dependency required by the loading path.
  • Solution: Read the full error in the ComfyUI console to identify the affected file or missing requirement. Verify that the file is complete and appropriate for the selected family, and follow any dependency instructions reported by the GGUF support. Changing a filename extension alone does not convert the file’s format.

Out of memory during encoder loading or prompt processing

  • Explanation: The selected encoder setup may require more GPU or system memory than is available. This is an underlying runtime error rather than a custom error message defined by this node, so its exact wording depends on the execution environment.
  • Solution: If GPU memory is the problem, try device=cpu and free memory used by other workloads. Ensure that you have enough system RAM for CPU loading, and avoid selecting unnecessary encoder files. If needed, use a smaller or quantized encoder variant explicitly supported by your model’s setup.

FunUI CLIP Loader Related Nodes

Go back to the extension to check out more related nodes.
FunUI
RunComfy
Copyright 2025 RunComfy. All Rights Reserved.

RunComfy is the premier ComfyUI platform, offering ComfyUI online environment and services, along with ComfyUI workflows featuring stunning visuals. RunComfy also provides AI Models, enabling artists to harness the latest AI tools to create incredible art.