Nodes/ComfyUI-N-Nodes/Load Image From Folder [πŸ…-πŸ…’πŸ…€πŸ…˜πŸ…£πŸ…”]
ComfyUI Node Runs on cloud

Load Image From Folder [πŸ…-πŸ…’πŸ…€πŸ…˜πŸ…£πŸ…”]

The folder loader that reports back what it found

By Nuked88Β·Created 3 years agoΒ·Updated 2 years agoΒ· 237
Load Image From Folder [πŸ…-πŸ…’πŸ…€πŸ…˜πŸ…£πŸ…”]
    • IMAGES
    • MAX WIDTH
    • MAX HEIGHT
    • IMAGE COUNT
    • PATH
    • IMAGE LIST
    β—„folderβ–Ί
    β—„fps30β–Ί

    Same basic job as this pack's LoadFramesFromFolder - point it at a directory, get a batch of images back - but this version is built for a different downstream need. Instead of carrying a frame rate forward for a video pipeline, it reports back on the folder itself: dimensions, a count, the resolved path, and a list of what it found. If your goal is dataset review, captioning batches, or anything where you care more about what's in the folder than reassembling a video, this is the one to reach for.

    How it works

    Feed it folder and it scans for images the same way LoadFramesFromFolder does, stacking them into an IMAGES batch. fps is still a required input here even though nothing in the outputs carries it forward - worth knowing up front so you're not hunting for where it went; this node just doesn't use it for anything the schema exposes.

    The outputs that matter

    IMAGES is the batch, same as always. Beyond that, this node hands back folder bookkeeping instead of video metadata: MAX WIDTH and MAX HEIGHT report the largest dimensions found across the set, which matters if your source images aren't perfectly uniform in size. IMAGE COUNT is exactly what it sounds like, and PATH echoes the resolved folder path back to you - useful if you built it from a relative path or a variable node upstream and want to confirm what actually got read. IMAGE LIST is a string of every filename found, joined by newlines - and it's worth reading that literally: it's a plain string, not a real ComfyUI list type, so don't wire it into something expecting a list output. Split it yourself downstream if you need the individual names.

    Installing the pack

    • ComfyUI Manager - search "ComfyUI-N-Nodes," install, restart.
    • Manual - cd ComfyUI/custom_nodes && git clone https://github.com/Nuked88/ComfyUI-N-Nodes.git, then restart ComfyUI.

    Pure file I/O again, no models or extra dependencies to worry about here.

    Common issues & troubleshooting

    You need the fps/metadata object for FrameInterpolator or a video writer instead. This node doesn't produce one. That's LoadFramesFromFolder - same pack, same "point at a folder of images" idea, but it tags its output with the frame-rate metadata the video nodes expect instead of the folder stats this one returns. Pick based on what's next in your graph, not which one you happened to find first.

    IMAGE LIST doesn't behave like a list anywhere downstream. That's expected, not a bug - it's a single newline-delimited string. If you need to iterate the filenames individually, split on \n in whatever node consumes it (a variable/string node with some custom logic, or an external script if you're driving this through the API).

    Mixed image sizes cause a batching error. ComfyUI's IMAGE batch type generally wants uniform dimensions across the batch. MAX WIDTH/MAX HEIGHT will tell you the largest values it saw, but this node doesn't resize anything to match - if your folder has inconsistent image sizes, resize them to a common resolution before pointing this node at the folder.

    CategoryN-Suite/Experimental

    Inputs (2)

    NameTypeDefaultDescription
    folderSTRINGβ€”
    fpsINT30β€”

    Outputs (6)

    NameTypeDescription
    IMAGESIMAGEβ€”
    MAX WIDTHINTβ€”
    MAX HEIGHTINTβ€”
    IMAGE COUNTINTβ€”
    PATHSTRINGβ€”
    IMAGE LISTSTRINGβ€”