Latent Loader Filtered (CCN)
Reload a saved .latent without the folder maze
- latent
Saving a latent is easy; finding it again is the problem. ComfyUI's built-in Load Latent only looks at the top of your input directory, so anything you stashed in a subfolder - or dumped into output/latents/ by a save node - is invisible to it. Latent Loader Filtered fixes that: it recurses into subfolders, finds every .latent file in your input directory, and gives you a picker you can sort by date_modified, name, or size, ascending or descending.
The author's own summary is the whole pitch: "Unlike the built-in Load Latent, it recurses into subfolders, so latents organized under input/latents/ (or any subfolder) are found." If you keep a tidy latent archive, this is the node that lets you actually use it.
The inputs that matter
- latent - the picker dropdown of found
.latentfiles. It lists relative paths from the input directory (solatents/good_one.safetensorsshows as such), and the combo's native type-to-filter gives you text search for free. - sort_by - date_modified, name, or size. When your latent collection grows past a dozen files, sorting by recent date is how you find "the one I just made."
- sort_order - descending or ascending. Descending date is the usual "newest first" default.
One output: latent, ready for the sampler or further tinkering. If there are no .latent files in input, the picker shows a clear "(no .latent files in input)" message instead of an empty broken dropdown - a small thing, but it tells you the fix immediately.
Getting latents into reach
The node only sees your input directory. Anything saved by a "Save Latent" node typically lands in output/latents/, which this node won't find. The author's documented workaround is simple: move the files you want from output/latents/ into input/ (or a subfolder of it), and they become selectable. That's not a bug - it's the standard ComfyUI input-dir convention, applied consistently.
Where it lives and the caveat
This is a wip (work-in-progress) node, same as Gated Increment: it ships in the git clone but is excluded from the registry-published package. In practice that doesn't matter - both install paths below are git clones - but if you ever install the pack as a bare registry package, this node may not appear. Clone from git to be safe.
It also has a small server component: the frontend fetches a metadata route (/ccn/latent_filter/list) from a local HTTP endpoint to get mtime/size for sorting, which is how the sort dropdown works at all. If the sort seems dead, it's usually because the frontend endpoint isn't reachable - a full restart (and a hard browser refresh) resolves it.
Install
cd ComfyUI/custom_nodes
git clone https://github.com/valkymaera/ComfyCollectorNodes
restart ComfyUI, or grab ComfyCollectorNodes from ComfyUI Manager. No model downloads, no Python deps beyond what ComfyUI already has. If you've ever lost a latent to a folder you forgot you had, this is a small, permanent fix.
Inputs (3)
| Name | Type | Default | Description |
|---|---|---|---|
| latent | COMBO | 1 options: (no .latent files in input) | |
| sort_by | COMBO | date_modified | 3 options: date_modified, name, size |
| sort_order | COMBO | descending | 2 options: descending, ascending |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| latent | LATENT | — |