Qwen3-VL Batch Info

Qwen3-VL Batch Info is the pack's smallest node and it does exactly one thing: count the images in a folder. You feed it a folder_path and it returns a single integer, total_count, with the number of png, jpg, jpeg, webp, or bmp files inside. That's it. No model involved, no captioning, no VRAM - it's pure filesystem math, which makes it the one node in this pack you can't really break.

Why would you want a node whose entire job is a number? Because the batch and loop workflows in this pack need to know how many iterations to run, and the count is rarely something you want to hardcode. Batch Info is the "read the folder once, tell the rest of the workflow what it's up against" helper. The pattern: wire total_count into a loop controller or use it to size a batch, so that when you add or remove images from your input folder, the workflow adapts without you editing a constant.

It's worth being honest about the scope here - this is a genuinely thin utility node, and it knows it. If you've already got a total_count from Qwen3-VL Folder Loader (Loop) (which also reports the count) you may not need Batch Info at all. It exists to be a cheap, standalone count you can read at workflow build time, or to feed loop parameters in a setup where the Folder Loader's index-driven outputs aren't convenient.

How it works

The mechanism is trivial and worth knowing because it defines the node's behavior: it globs *.png, *.jpg, *.jpeg, *.webp, *.bmp in the folder and returns the length of that list. Two behaviors fall out of that:

• If the folder doesn't exist, it returns 0. Not an error, just zero. If you're feeding the count into a loop and you get zero, check your path before debugging anything else.
• Only top-level files in that folder count. It does not recurse into subfolders. Nested images are invisible to it.

The single input

• folder_path (STRING) - the absolute path to the folder. That's the whole input list.

Where it fits in the wider workflow

The pack's batch story has two halves: Qwen3-VL Batch Run (Folder) processes every image in a folder and returns one big formatted string, and the loop flavor (Folder Loader + Loop Run) walks images one at a time so you can inject each result into an image-generation chain. Batch Info feeds both - it gives you the total so a loop knows when to stop, or so you can sanity-check the scope before kicking off a long batch. The README's warning applies here louder than anywhere: the batch nodes process every single image in the folder, so point them at a dedicated folder, never your whole Downloads or Pictures directory. Batch Info is the cheapest way to see just how many images that "dedicated folder" actually contains before you press Queue.

Install the pack once (ComfyUI Manager → search "qwen3-vl-comfy-ui", or clone https://github.com/Granddyser/qwen3-vl-comfy-ui into ComfyUI/custom_nodes and pip install -r requirements.txt), restart ComfyUI, and you'll find Batch Info under Qwen3-VL along with the rest of the family. It's the node you'll use for five seconds every time you set up a batch job - and those five seconds are exactly why it exists.