Nodes/FunUI/FunUI Checkpoint Loader
ComfyUI Node

FunUI Checkpoint Loader

The FunUI Checkpoint Loader, Read Honestly

By digital-garbage·Created about a year ago·Updated about 11 hours ago· 22
FunUI Checkpoint Loader
    • model
    • clip
    • vae
    • status
    ◄ckpt_name▾►

    Most of FunUI assumes 2026 video models: an H3 or LTX diffusion file here, a text encoder there, a VAE somewhere else, three slots you pair up yourself. This node is the opposite assumption. FunUI Checkpoint Loader exists because the SD family still ships everything welded into one file - unet, text encoder, VAE - and a pipeline built around three separate loaders has no way to open one.

    The pack's own source comment says it plainly: neither the split loaders nor this one is the "real" one, which is the point of FunUI's pipeline slots being swappable.

    What it actually does

    It's a thin, honest wrapper. Under the hood it calls ComfyUI's own comfy.sd.load_checkpoint_guess_config - the same architecture guessing core's CheckpointLoaderSimple does - so there's no clever reinterpretation of your file going on. Pick a file, get model, clip, vae.

    What you're paying for is the fourth output: status. The node reports what the file loaded as, and warns when the checkpoint is missing pieces. That matters more than it sounds. A checkpoint with no baked VAE loads happily and then fails three nodes downstream, usually as a grey, washed-out render that sends people hunting for a colour-management fix that doesn't exist. Here you get (no vae) in the status string and a line in the log before you queue anything.

    The inputs and outputs that matter

    Only one input to set:

    • ckpt_name - a dropdown of whatever ComfyUI finds in ComfyUI/models/checkpoints. Single-file checkpoints only. A bare diffusion model (the huge H3/LTX-style transformer you download on its own) is not a checkpoint; it wants one of the pack's split loaders instead.

    Then four outputs:

    • model → your sampler, modifier loader, or LoRA loader.
    • clip → prompt encoding, or FunUI Enhance Prompt if you want an LLM rewriting the text first.
    • vae → decode. On an SD 1.5 checkpoint that came without one, this output is an empty placeholder that raises when used, so wire it knowing that.
    • status → a plain string. Nothing consumes it; it's for you, and it's viewable in the node's output panel after a run. That's the whole point of it.

    Installing it

    The nodes all come from one pack, so this section is the same for every FunUI node. In ComfyUI Manager, search FunUI (registry name FunUI), or:

    cd ComfyUI/custom_nodes
    git clone https://github.com/digital-garbage/FunUI
    cd FunUI && pip install -r requirements.txt
    

    Then restart ComfyUI. Note the naming mess: the pack page you came from says olivv-cs/ComfyUI-FunPack, because the project started life as FunPack and has since been renamed FunUI. If your clone directory is still called ComfyUI-FunPack, the node info panel will say custom_nodes.ComfyUI-FunPack - that's just the folder name, nothing breaks. requirements.txt needs comfy-kitchen>=0.2.32 and gguf; spaCy and NVIDIA VFX are optional add-ons installed on the next restart after you switch those modules on.

    You don't need to open the FunUI studio (/fun/) to use these nodes in a normal graph, but the app is what most of them were built for. After installing, Settings ▸ About FunUI tells you which version you got.

    Where people get burned

    A file in the wrong folder is invisible. .safetensors checkpoints go in models/checkpoints. Dropped into models/diffusion_models, they simply won't appear in this dropdown, and no amount of restarting fixes it.

    Don't let pip upgrade what ComfyUI compiles against. The pack's own docs say this, and it's the single most common way a working install dies: if pip install -r requirements.txt announces it will change torch, numpy, transformers or comfy-kitchen, read that list before saying yes. A torch swap costs you an afternoon.

    A status line is not a solution. If it says the file has no clip, the model will sample fine and your prompt will encode as garbage - because there's no encoder. Either put the matching encoder through FunUI's split CLIP loader, or grab a checkpoint that actually carries one. The node told you; it can't fix the file for you.

    One practical note on VRAM. On 2026 models the text encoder is a second budget, not a rounding error, so a checkpoint load can look fine and then OOM on the first forward pass. If that happens, it's the model that doesn't fit - not this node being slow.

    Finally, expectation setting: FunUI is a one-person hobby project with no QA team, and you won't find a tutorial thread on it anywhere. When something looks wrong, the ComfyUI console is the documentation - the pack logs which parts of a checkpoint loaded and which didn't.

    CategoryFunUI/Loaders

    Inputs (1)

    NameTypeDefaultDescription
    ckpt_nameCOMBO0 options:

    Outputs (4)

    NameTypeDescription
    modelMODEL—
    clipCLIP—
    vaeVAE—
    statusSTRING—