⭐ Star LTXV Load Last Image From Folder
Auto-load the newest image in a folder so your next clip starts where the last ended
- image
Continuation workflows have a recurring need: "take whatever the last step produced and build on it." In video that means loading the most recently saved frame, and doing it by hand every run is the kind of chore that makes you resent the tool. Star LTXV Load Last Image From Folder (class StarLTXVLoadLastImage) is the automation for it - point it at a folder and it returns the newest image in it, so your next generation can chain onto the last one without you re-picking a file.
How it works
You give it a folder_path string and it scans for image files (png, jpg, jpeg, webp, bmp, tiff and friends), then returns the one with the most recent modification time as an IMAGE output. The node's IS_CHANGED hook is the detail that makes it behave: when the folder is invalid or empty it returns a "always changed" marker so ComfyUI doesn't cache a stale result, and when the folder is fine it re-checks on every run. That means the output genuinely tracks "the newest file in the folder right now" rather than going stale - which is the entire point of using it in a loop.
The intended pattern in an LTX-Video pipeline: your save node writes each clip's final frame (or a reference image) into a folder, this node reads back the newest one, and that becomes the conditioning image for the next image-to-video pass. Combined with ⭐ Star LTXV Get Last Frame on the decode side, you can build a "watch the story march forward" chain where every iteration automatically picks up where the last left off.
Inputs and outputs
folder_path- a plain string path to the folder to watch. This is the only input.image(IMAGE) - the newest image found, ready for a VAE encode or a conditioning input.
That's it. Simple on purpose - the cleverness is all in the freshness behavior, not in options.
Where it fits
Any workflow where a downstream run should automatically consume the newest artifact: multi-pass LTX continuation, folder-based img2img chaining, or a "watch this directory" generation loop. It's the load-side twin of the pack's save nodes - save to a known folder, load "the last one" next run.
Installing
Part of the StarNodes pack - install Starnodes via ComfyUI Manager, or:
cd ComfyUI/custom_nodes
git clone https://github.com/Starnodes2024/ComfyUI_StarNodes
cd ComfyUI_StarNodes
pip install -r requirements.txt
Restart, then search star on the canvas. No models.
Common issues
"Last" means most recently modified, so if something else writes into that folder (a preview thumbnail, a sidecar), you might load the wrong file - keep the folder exclusive to the outputs you intend to chain. If nothing loads, the path doesn't exist or holds no image files; the node tolerates that gracefully (returns no image rather than crashing). And because it reads by modification time, a save node that re-writes an old file with a new timestamp will legitimately surface it as "last" - that's your file ordering, not a bug.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| folder_path | STRING | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| image | IMAGE | — |