Load Frame Sequence

The simplest node in the frame family, and the front half of the older loading path. You give it a folder path, it recursively globs every file in it, and it outputs a FRAMES list - one entry per image - plus a Total_frames count. That's it. No filtering, no range controls, no resizing. It's the "just give me everything in this directory" node.

Its real job is to feed LoadFrame, which expects a FRAMES list and pulls out the specific frame the loop counter asks for. So the pairing looks like: LoadFrameSequence lists the folder → LoadFrame picks the current frame by number → that image goes to the sampler. In the newer sample workflows, MakeFrameDataset + LoadFrameFromDataset largely replaced this duo, but LoadFrameSequence still shows up in the older ones you'll find in the wild, and it's the least surprising way to eyeball a folder of frames.

Inputs and outputs

Just one input: file_path. The output is a Frames list plus Total_frames. Both are useful - the list for loading, the count for wiring into LoadFrame's total_frames or just knowing how long the clip is.

A couple of honest warnings. The node validates on the fly and will complain ("Found 0 frames in path …") if the path is empty or wrong - that's actually a feature, it catches typos early. But because it grabs every file recursively, a folder with mixed extensions or stray non-image files (like a thumbs.db on Windows) will list them too, and the downstream loader may choke when it tries to open one. Keep the folder clean: only the frames you actually want.

Also note the ordering: files are globbed, and glob order isn't guaranteed alphabetical in a way you can rely on. If your frames are named 0001.png … 0600.png and the sequence loads out of order, that's this node showing you its one real weakness - zero-padded, sequentially named files (%06d style) are the fix, which is exactly what MakeFrameDataset's extraction produces.

Honestly, unless you specifically need a raw frame list to poke at, LoadFrameFromDataset is the smoother ride. But if you've loaded an old ComfyWarp workflow and see a big FRAMES wire, this is what it comes from, and now you know what it does.