FL Google Drive Image Downloader

Paste a Google Drive share link, get an image tensor back - no manual download-then-load-image round trip. Useful for workflows pulling reference images from a shared Drive folder someone else controls, like a client's asset drop or a team's shared moodboard, where re-uploading everything into ComfyUI by hand doesn't scale.

The mechanism

Downloads from a Google Drive share link and converts the result straight to an RGB tensor normalized to 0-1, caching by an MD5 hash of the link so re-running the same link doesn't re-download on every queue - it just serves the cached file. It's the specialized counterpart to FL_GoogleDriveDownloader (a sibling node in this same pack for arbitrary files and ZIPs), built for the common case of "I just want the image."

Inputs and outputs that matter

There are only three fields. google_drive_link is the share URL - it needs sharing permissions that actually make the file fetchable, not one locked to your personal account view. use_cache (default true) should stay on for anything you're iterating on repeatedly, since that's the whole point of the MD5-hashed cache; turn it off only when the file behind the link changes and you need a fresh pull every time. show_preview (default false) toggles an on-node preview so you can eyeball what got downloaded without wiring a separate Preview Image node downstream.

Output: a single IMAGE.

Installing it

ComfyUI Manager: search Fill-Nodes, install, restart. Manually: cd ComfyUI/custom_nodes && git clone https://github.com/filliptm/ComfyUI_Fill-Nodes, then restart. Same family as FL_GoogleCloudStorage, and worth the same heads-up: this pack's Google integration nodes reference Google's client libraries at startup, and a real (if slightly panicked) r/StableDiffusion thread exists of someone seeing Google-Cloud-related log text scroll by after installing this pack and wondering if it was malware. It wasn't - it's these nodes checking their own dependencies, and it's documented in the pack's own README. Worth knowing before you install so a wall of unfamiliar startup text doesn't spook you into uninstalling something that's working exactly as intended.

Where people get burned

This only works on links that don't require signing into a specific Google account to view - a file shared as "restricted, specific people only" won't download through a link the way "anyone with the link" sharing will. If a download fails or comes back empty, check the share permissions first, well before touching use_cache or anything else.

And because use_cache keys off the link itself rather than the file's content, if someone replaces the file behind an existing share link, you'll keep getting the cached old version until you toggle use_cache off for one run to force a refresh.