Nodes/Comfyroll Studio/CR Image List (Legacy)
ComfyUI Node Runs on cloud

CR Image List (Legacy)

Comfyroll's Manual Way to Bundle Images Into a List

By Suzie1Β·Created 3 years agoΒ·Updated 2 years agoΒ· 1,296
CR Image List (Legacy)
  • image_1
  • image_2
  • image_3
  • image_4
  • image_5
  • image_list
  • IMAGE_LIST
  • show_help
β—„alias1β–Ί
β—„alias2β–Ί
β—„alias3β–Ί
β—„alias4β–Ί
β—„alias5β–Ί

CR Image List does one job: it takes up to five images you've wired in by hand and bundles them into a single IMAGE_LIST - Comfyroll's own list type, separate from ComfyUI's native batched IMAGE tensor - for feeding into whatever Comfyroll node downstream expects a list rather than a single image or a batch.

How it works. Five optional image slots (image_1 through image_5), each with a matching alias text field so you can label what each one is - handy if a downstream node renders those labels, say as captions in a grid layout. There's also an image_list input that accepts the output of another CR Image List node, which is how you chain past five images: wire one list into the next one's image_list slot and it keeps growing. Output is the combined IMAGE_LIST, plus the standard show_help string.

Worth knowing before you reach for it. This node is tagged Legacy in its own category path inside Comfyroll's node menu - it's not called out by name in the pack's top-level README the way CR Image Size explicitly is, but the tag is there in the node's own metadata. Comfyroll's more actively-used list nodes today tend to load images straight from a folder - CR Load Image List and CR Load Image List Plus - rather than requiring you to wire up to five image sockets by hand. If you're picking a list node fresh rather than maintaining an existing workflow, it's worth checking those first; this one is really for the case where you already have five specific, individually-produced images in the graph and want to gather exactly those.

Why it's IMAGE_LIST and not IMAGE. This matters in practice: IMAGE_LIST is a Comfyroll-specific socket type, so it only plugs into other Comfyroll nodes built to consume it - it won't connect to ComfyUI's native batch-processing nodes expecting a plain IMAGE. If you're trying to wire this into something outside the Comfyroll pack and the socket won't connect, that's why.

Install. ComfyUI Manager: search "Comfyroll Studio", install, restart. Manually: cd ComfyUI/custom_nodes && git clone https://github.com/Suzie1/ComfyUI_Comfyroll_CustomNodes.git, restart. No models to download.

Troubleshooting. Same pack-wide caveat as every other Comfyroll node: it registers its entire node set from one shared file, and real install reports on r/comfyui show a single broken import (Failed to load Graphics nodes / Failed to load Utility nodes, a NameError underneath) wiping every Comfyroll node from the menu at once, not just the one that failed. If Comfyroll nodes are missing after install, redo it with a clean git clone - a corrupted or partial download (the CivitAI zip is a common culprit) causes this more often than an actual dependency conflict. One separate report from someone trying to build an XY-grid comparison workflow with Comfyroll noted the list/grid tooling here isn't the most transparent to configure compared to dedicated XY-grid packs - if you're specifically after image comparison grids rather than just bundling a handful of images, it's worth comparing against alternatives before committing a whole workflow to it.

Category🧩 Comfyroll Studio/πŸŽ₯ Animation/πŸ’€ Legacy

Inputs (11)

NameTypeDefaultDescription
image_1optIMAGEβ€”
alias1optSTRINGβ€”
image_2optIMAGEβ€”
alias2optSTRINGβ€”
image_3optIMAGEβ€”
alias3optSTRINGβ€”
image_4optIMAGEβ€”
alias4optSTRINGβ€”
image_5optIMAGEβ€”
alias5optSTRINGβ€”
image_listoptimage_LISTβ€”

Outputs (2)

NameTypeDescription
IMAGE_LISTIMAGE_LISTβ€”
show_helpSTRINGβ€”