Load Image From Url

If you've ever tried to drive ComfyUI purely through its API, you've hit this wall: the built-in LoadImage node only shows you files that are already sitting in ComfyUI's own input/ folder. It's a whole recurring question on the ComfyUI subreddits - "how do I send an image to the API?" - and the answers people land on are either upload the file first, or base64-encode it into the request body. Load Image From URL skips both. Give it a link and it fetches the image directly over HTTP, no upload step, no base64 blob bloating your request payload.

How it works

One multiline text field, one URL per line - the pack's own convention is literally "one line, one image." ComfyUI fetches each line, decodes it, and if the source image carries an alpha channel, splits that out into a mask automatically, exactly the way the built-in loader handles a local PNG with transparency.

The inputs and outputs that matter

• urls (STRING, multiline) - the only input. Paste one URL per line; a three-line field loads three images.
• images (IMAGE) and masks (MASK) - both outputs are marked as list outputs, so each line in urls becomes its own list entry rather than getting batched into one tensor. Wire the result into this pack's ListUnWrapper if you want the rest of the graph to run once per image instead of trying to process them all at once.

How to install it

Via ComfyUI Manager: search comfyui-easyapi-nodes, install, restart. Or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/lldacing/comfyui-easyapi-nodes.git
cd comfyui-easyapi-nodes
pip install -r requirements.txt

Restart ComfyUI. No models, no heavy dependencies - this node just needs outbound network access from wherever ComfyUI is actually running.

Common issues & troubleshooting

Reachability is the whole game. Whatever machine your ComfyUI process runs on needs to be able to reach the URL you paste in - easy to forget when you're testing against a link that only resolves inside a private network, behind auth, or on your own laptop's localhost.

Hotlinking gets blocked. A handful of image hosts refuse requests without a browser-like referer header, so a link that opens fine in your browser can still fail here. Grab a direct CDN or object-storage link rather than a page URL when you can.

One bad line can take down the whole batch. With several URLs stacked in one multiline field, a single 404, redirect loop, or timeout tends to fail the whole fetch rather than skipping past it quietly. If you're loading a batch from user-supplied links, validate them (or split risky ones into their own run) before firing off a big multiline load.