OvertliAddtlLoadImage

You installed Overtli Studio Suite, added this node, clicked the dropdown and got nothing. Not a bug, and not an install failure. OvertliAddtlLoadImage is ComfyUI's stock Load Image with the file list nailed to one directory and one directory only: ComfyUI/input/OvertliDS/addtl. If your pictures are anywhere else, this node cannot see them, and it never will.

Why a loader that refuses to see your images

The whole suite is built on a Normal/Addtl split. You get two prompt libraries, two sets of saved references, separate output folders, even separate latent-continuation storage for the video side - input/OvertliDS/addtl for "Addtl" media and input/OvertliDS/references for the Normal side. The point is scope discipline: your regular reference set stays clean and small and your second, separate pile of references doesn't leak into the standard pickers. In the pack's documentation that split is explicit - managed standard selectors exclude Addtl entries, and vice versa.

In practice Addtl is also the side the pack sets up for material you might not want sitting in the same list as your family photos. So no, this isn't a general-purpose loader you should swap in everywhere. If you want to load any image from input/, use core Load Image and leave this one alone.

How it actually works

Under the hood it subclasses nodes.LoadImage, so the pixels you get are decoded exactly like core's loader: PIL, EXIF orientation applied, RGB float tensor, alpha channel turned into an inverted mask. What changed is the file list.

INPUT_TYPES walks input/OvertliDS/addtl recursively, keeps only .png .jpg .jpeg .webp .bmp .gif .tif .tiff, and hands you the paths relative to input/. Then it validates twice - once in VALIDATE_INPUTS and again inside load_image - resolving your selection through ComfyUI's annotated-filepath helper and refusing anything that isn't a real file inside the island. Break that rule and you get the pack's own message: "Choose an existing reference inside input/OvertliDS/addtl." It fails loudly rather than quietly loading a stale path, which is the right call.

One input, two outputs. The required image combo is your picker, and it carries an upload control. Outputs are the standard pair, IMAGE and MASK - wire IMAGE into a ControlNet preprocessor, a VAE Encode, an img2img chain, or a vision model's image context, and MASK only if something downstream wants the alpha. Multi-frame GIFs and TIFFs still load as a batch the way core does.

Install

ComfyUI Manager: search Overtli and install the suite. Or by hand:

cd ComfyUI/custom_nodes
git clone https://github.com/OvertliDS/overtli-studio-suite
cd overtli-studio-suite
pip install -r requirements.txt

Then restart ComfyUI. The Python requirements are light - requests, Pillow, numpy, with torch coming from your ComfyUI runtime. No model downloads. The README leans Windows-first, which matters more for the CLI-based provider features elsewhere in the pack than for this node.

You'll also need the folder to exist, since the code returns an empty list when it doesn't:

mkdir -p ComfyUI/input/OvertliDS/addtl
cp ~/my_references/*.png ComfyUI/input/OvertliDS/addtl/

New-Item -ItemType Directory -Force -Path ComfyUI\input\OvertliDS\addtl
Copy-Item $HOME\my_references\*.png ComfyUI\input\OvertliDS\addtl\

The pack's own upload controls write into that island for you - the Director posts uploads with subfolder=OvertliDS/addtl. Dropping files in by hand is the guaranteed route, though, and subfolders inside addtl are fine because the listing is recursive.

Where people get burned

• Empty dropdown. Either the folder doesn't exist, or your files are sitting at the root of input/. Nothing at the top level shows up here.
• Suddenly-invalid selection. The workflow stores the relative path. Move, rename or delete the file and the node throws the island error on the next run instead of silently loading something else. Re-select, don't debug it.
• Wrong node for the job. Most people who end up here wanted core Load Image. The giveaway is that the dropdown shows paths like OvertliDS/addtl/foo.png rather than bare filenames.
• It is not a saver. No previews, no writes, no sidecars - it only hands pixels to the graph. Your original stays untouched on disk, which also means its embedded workflow metadata survives if nothing rewrites the file.