Upload Media

Upload Media (class VideoUpload) is the pack's little file-picker, and it does exactly one thing: you drop a video into ComfyUI's input folder, pick it from a dropdown, and it hands you the file's path. That's the whole job, and it's a job somebody has to do.

Why does this node exist? Because the pack's main node, Overlay Media Node, takes media as STRING file paths wired in from other nodes - you can't just type a path into it. So you need something with a GUI dropdown that outputs a path, and this is that something. It's also handy anywhere else a node wants a video path on a wire, like a VHS_LoadVideoPath.

What it actually does

On creation, the node looks at ComfyUI's input directory, collects every file ending in webm, mp4, mkv, gif, or mov, and puts them in the video dropdown. Pick one and it resolves the annotated path (so it still works after you've moved the file into a subfolder) and returns it as the filepath output - a plain STRING.

That's it. No frames, no audio, no loading into the graph. If your workflow needs actual pixels, this is the wrong node - VHS_LoadVideo from VideoHelperSuite is the one that decodes frames and audio into the graph. VideoUpload just produces a path you can wire into something that wants one.

Using it

Drop your clip into ComfyUI/input (the same folder where you drop images for LoadImage), then add the node. One honest gotcha: the file list is built when the node is instantiated, so a file you drop in after adding the node won't show until you delete and re-add it, or restart ComfyUI. New videos, new node.

Wire the filepath output into Overlay Media Node's main_media or overlay_media input, or into any other path-based video node, and you're set.

Installing it

Same pack as its sibling - install via ComfyUI Manager (search ComfyUI Overlay Media Node) or clone it:

cd ComfyUI/custom_nodes
git clone https://github.com/Elaine-chennn/comfyui-overlay-media
pip install -r requirements.txt

then restart ComfyUI. No models to download, no GPU needed. The only real dependency is the Python ffmpeg wrapper, and that still wants the actual ffmpeg binary on your PATH - worth checking if you're on a clean Windows portable install.

If something looks off

File not in the dropdown? Wrong extension (only those five are listed), it's in a subfolder you didn't check, or you need to re-add the node. Downstream "file not found" error? The file was moved after the node grabbed it. It's a three-line node, so the failure modes are three-line failures. For what it is - a dropdown that hands a path to path-hungry nodes - it does the job without fuss.