Batch Load Latent & Image

This is the other half of the pair. Batch Save Latent & Image writes latents and their decoded images to disk; this node reads them back. You give it a list of filenames and a directory, and out come the latent and the image, ready to plug into a fresh sampler or the rest of your graph.

Why you'd reach for it

It only makes sense next to its sibling, so the use case is the same one: splitting a heavy workflow into stages that don't have to run in one shot. The pattern people actually use - straight off r/StableDiffusion - is to run a pile of cheap stage-one renders, save the latents, throw away the ones that don't fit, and then load only the keepers into the expensive second pass. No re-sampling the starts you already liked, no keeping two big models resident at once, and a nice side effect for low-VRAM setups: the first model can leave memory entirely before the second one loads.

Same honest caveat as on the save side, though. ComfyUI ships built-in Load Latent, and it manages memory well enough on its own now that a lot of people never reach for this at all. Where this node earns its slot is when you saved the latent and its image together and want both back in one pull - you get the picture for free instead of re-decoding a latent just to see what it is.

How it works

A latent is the compressed form the diffusion model works in - cheap to store, and you can resume from it without re-running the steps that produced it. Loading one drops you back into the middle of a pipeline. This node reads your filename list line by line from the load directory, pulls each saved latent and its paired image off disk, and emits them as a batch. Feed the latent output into a KSampler's latent input to continue generation from that point; the image output is there when you need the pixels too.

The inputs that matter

• filenames - the multiline list, one name per line (default latent_1 / latent_2 / latent_3). These have to match what you wrote on the save side. A typo here isn't a soft failure; the file simply isn't there.
• load_directory - defaults to latents, i.e. output/latents. It must point at the same place the save node wrote to, or you'll load nothing.

Outputs are latent (LATENT) and image (IMAGE) - the same pair you saved, back in the graph.

Installing it

Through ComfyUI Manager, search "ComfyUI Unusual Tools" and install, then restart. Or by hand:

cd ComfyUI/custom_nodes
git clone https://github.com/Diohim/ComfyUI-Unusual-Tools

No model files, no dependency wrangling. It appears under latent.

Where people get tripped up

Loading is where the save/load contract gets tested, so almost every problem is a mismatch. The filenames you ask for have to actually exist in the directory you point at - the README's first troubleshooting step is literally "verify that the filenames you're trying to load actually exist," which tells you how common the typo-and-wrong-folder combo is. Keep the directory identical to the save node's. If a relative path acts up, use an absolute one. And when something silently comes back empty, check the ComfyUI console before theorizing - the error is usually sitting right there, and it's usually a name or a folder, not the node.