❌ Load TinyBreaker Checkpoint (custom) [Deprecated]

The "custom" in ❌ Load TinyBreaker Checkpoint (custom) [Deprecated] was a promise the pack outgrew: it was the loader that let you override how each sub-component of TinyBreaker loaded - which VAE, which transcoder, which refiner, what resolution the model assumes. It's now deprecated, and the reason is a familiar one in fast-moving packs: the feature set it offered got folded into the mainstream loaders, and the old node kept a naming scheme (and a "custom" dropdown list) that no longer matches how checkpoints ship.

What it did

Inputs were ckpt_name plus four overrides: vae (fast/high quality), transcoder (automatic), refiner (automatic/none), and resolution (automatic/512/1024/2K/4K). Outputs were MODEL, VAE, TRANSCODER, REFINER_MODEL, REFINER_CLIP, and GENPARAMS. So it was the "advanced" loader of its era - the one you'd reach for when the default assumptions didn't fit your hardware or your experiment.

Why it's gone

Look at the current lineup and you'll see the whole thing was inherited. The advanced loader 💪TB | Load TinyBreaker Checkpoint (advanced) now offers exactly those levers - vae, transcoder, refiner, resolution (as 512/1024/2048/4096) - plus an upscaler_vae, and it's not deprecated. The old node's resolution choices also aged badly ("2K"/"4K" are vague next to the explicit pixel counts the modern loader uses), and its six outputs missed the CLIP and UPSCALER_VAE that current workflows expect. Deprecating it wasn't a quality judgment against the idea; it was the idea being absorbed into something better.

If a workflow forces you to look at it

Same playbook as every deprecated node: replace it with the advanced loader and rewire. The output names mostly line up (MODEL, VAE, TRANSCODER, REFINER_MODEL, REFINER_CLIP, GENPARAMS → METADATA), so the swap is mostly about the CLIP output that now exists and the renamed metadata output. If you were using resolution: 2K, note the modern equivalent is 2048. And don't go looking for it in the node menu - deprecated nodes are hidden from default searches; they only surface when a saved workflow references them.

Install

It's part of the pack, so any install brings it: ComfyUI Manager search "tinybreaker", or git clone https://github.com/martin-rizzo/ComfyUI-TinyBreaker into custom_nodes, restart. But your endgame here is to get off it - the advanced loader does everything it did, does it with saner options, and is actually maintained. Port the workflow, delete the node from your canvas, and move on.