ComfyUI Node

Veo Video Saver

The node that actually shows you your expensive clip

By ShmuelRonen·Created about a year ago·Updated about a year ago· 33
Veo Video Saver
  • video_paths
  • output_paths
save_to_outputtrue
filename_prefixveo_video

The terminal node with the built-in player

Veo Video Saver is the output node for this pack - the one with the native video preview. After Veo Text to Video spends minutes (and a couple of dollars) rendering an mp4 on Google's servers, this is where you actually see the result and give it a filename you'll recognize later. The name is doing honest work: it saves, and it previews, and because it's marked as an output node, ComfyUI treats it as the end of the line.

How it works

It takes the pack's VEO_VIDEO type - a path to the generated mp4 - and does two things. First, if save_to_output is on (it is by default), it copies the video into your ComfyUI output folder under filename_prefix_001.mp4. The counter increments automatically, so you can run a batch of generations without ever overwriting a previous clip. Second, it pushes the file to the frontend, and the pack's own JavaScript renders an inline <video> player right inside the node - loop on, controls on, ready to scrub.

One thing worth understanding: the generation node already writes the raw file to your output directory as veo_<timestamp>.mp4. So the "saving" here is really "copying to a tidy name" - if you only care about having the file, you could technically skip this node. Its real value is the preview and the readable filename, and given how much Veo generations cost, "actually seeing the thing you paid for" is worth a node all by itself.

Inputs and outputs

Three inputs, all straightforward:

  • video_paths (VEO_VIDEO) - wire from Veo Text to Video.
  • save_to_output - keep it true unless you just want the preview and no copy.
  • filename_prefix - change the default veo_video to something like client_shot_03 before you batch. You'll thank yourself when you're hunting files later.

The output, output_paths (VEO_VIDEO), is a passthrough of whatever it saved - wire it onward to Veo to VHS if you want the frames in Video Helper Suite.

Install

It's part of the same one-repo pack:

cd ComfyUI/custom_nodes
git clone https://github.com/ShmuelRonen/ComfyUI-Veo2-Experimental
cd ComfyUI-Veo2-Experimental
pip install --upgrade google-genai

Restart ComfyUI and the node appears as "Veo Video Saver". No models, and no dependencies beyond the SDK - OpenCV, numpy and torch are already inside ComfyUI's Python.

Gotchas

The preview is delivered by the pack's frontend extension (web/js/veo_nodes.js), not by a core ComfyUI widget. That means if you don't see a player but the file does get saved, the extension didn't load - a stale browser tab or a ComfyUI version mismatch is usually the culprit, and a hard refresh fixes it. Also, the filename counter starts at 001 and only counts up per run, so your output folder fills in slightly arbitrary order; set a meaningful prefix early and you'll stay sane.

Categoryvideo/preview

Inputs (3)

NameTypeDefaultDescription
video_pathsVEO_VIDEO
save_to_outputBOOLEANtrue
filename_prefixSTRINGveo_video

Outputs (1)

NameTypeDescription
output_pathsVEO_VIDEO