Load image from WebDAV

If you keep your image library on a NAS, a Nextcloud, or any WebDAV server, Load Image from WebDAV lets ComfyUI fetch a file from it mid-graph - no syncing folders, no mounting drives, no downloading to input first. Three string inputs (url, username, password) go in, one IMAGE comes out, ready for img2img, ControlNet, or whatever consumes it.

How it works. The node does a requests.get() on the url with HTTP basic auth, opens the response as an image, and runs it through the same pipeline as ComfyUI's own image loader: EXIF transpose (so photos with rotation metadata land upright), conversion to RGB, normalization to a float tensor, and a batch dimension so it reads as a standard IMAGE. Notably it also handles mode='I' (32-bit int) images by scaling them - a courtesy most loaders skip.

The input that matters most is url. Unlike the upload nodes in this pack, which append a filename to whatever you give them, this one fetches the URL as-is. You need the full, exact path to the file - including the WebDAV mount point, which is service-specific. For Nextcloud that's the ugly-but-real form:

https://your-server.example/remote.php/dav/files/username/path/to/image.png

For dufs or a plain nginx dav share it's the direct file path. If you get a 404, 401, or a garbled image, check the full URL against your server's WebDAV path first - that's the #1 failure mode.

Why you'd reach for it. The community's usual answer to "ComfyUI files live on another machine" is rclone syncing your output folder to a cloud target - which works, but syncs everything. This is the on-demand version: pull exactly the image you need, exactly when you need it, in the middle of a workflow. If you run generation on a headless box and keep source material on a NAS, that's a genuinely useful pattern.

Things to be careful about:

• Credentials live in the node, which means they live in the workflow, which means they're embedded in every PNG you save with workflow metadata. Do not share workflows that contain a NAS password - scrub it or expect a leak. This is a real, concrete security consideration, not a hypothetical.
• Basic auth only. If your server does OAuth or token auth, this node can't help you.
• No caching - it re-downloads on every run. Fine for occasional pulls, wasteful inside a loop.
• The URL is a plain text field; there's no file browser, so you'll be typing or pasting paths.

Install is the pack standard (Chaser's Custom Nodes, chaserhkj). ComfyUI Manager - search "Chaser's Custom Nodes" - or:

cd ComfyUI/custom_nodes
git clone https://github.com/chaserhkj/ComfyUI-Chaser-nodes

then restart. No models to download; the relevant dependencies (requests for the HTTP, pillow from ComfyUI itself) install automatically. And keep the author's own warning in mind - this is a personal ad-hoc pack, "use them at your own risk" - especially relevant here since you're handing it server credentials.