Save to Shade

Save to Shade is the companion to Shade Mount: Mount brings a Shade.inc project drive onto the machine, this node writes your render output to it. Give it a mount path and an image or a list of video clips, and it saves them to <mount_path>/output/ with auto-incrementing filenames - so consecutive runs don't clobber each other and everything lands in a predictable spot that other machines on the workspace can see.

It's squarely aimed at the same narrow audience as Shade Mount: render VMs pushing deliverables to a Shade filespace. If you're not running that stack, there are a dozen generic savers that are a better fit. If you are, this is the two-minute node that closes the loop between "generated" and "on the shared drive."

The inputs

• mount_path - the mounted drive path, normally wired from Shade Mount's mount_path output. It's a required string input, so you could type it too, but wiring it keeps the workflow honest.
• filename_prefix - the base name, output by default; the node appends an incrementing number so each save gets a unique file.
• format - png or jpg (images only; videos save as MP4 regardless).
• quality - JPEG quality, 95 default.
• image - an IMAGE tensor to save as a file.
• video_paths - a list of video file paths (the video_paths output from a DIGIT video generator) to copy into the drive.

Output: saved_paths - the paths of everything it wrote.

How it works

There's not a lot of machinery to it, and that's a feature. It takes the media you connected, writes it into <mount_path>/output/, and hands back where each file went. The auto-incrementing filename means you can re-queue the same workflow and get output_0001.png, output_0002.png, and so on, rather than fighting overwrite dialogs. Because it works off a plain path string, it doesn't care whether that path came from Shade Mount, a typed-in mount, or an NFS share - it just needs a writable directory.

Gotchas

Install via the pack: ComfyUI Manager, search comfyui-digit, restart. The main failure mode is the mount itself - if mount_path isn't mounted (or the drive dropped), the save fails, and the fix is upstream in Shade Mount, not here. Make sure the environment ComfyUI runs in has the Shade credentials, because if the drive was mounted by a different process or a shell without SHADE_API_KEY, the path may be stale. And note there's no save_workflow metadata option here - this is a lean copy-out, not the PROJEKTS pipeline saver. For pushing finished clips to a shared drive, though, that leanness is the whole appeal.