Veo Get 1080p (Ace Data Cloud)

If you've ever run Veo through an API and gotten a soft 1280×720 file back wondering why the model that advertises 4K handed you a tube-era frame - you're not alone, that's a recurring complaint in the ComfyUI crowd. The answer is usually that the default output tier is genuinely lower resolution, and the high-res version is a separate, separately-priced operation.

That operation is what this node wraps.

What it does

"Veo Get 1080p" is one action on the main video endpoint, not its own service. It POSTs action: get1080p to /veo/videos with an existing video ID plus the model that produced it, and returns a task ID. Ace then re-encodes your clip at full HD and hands back a new CDN URL.

Why does it need to know the model? Because different Veo generations have different upstream pipelines and price points, and the request has to be routed and billed against the right one. That single extra widget is the whole difference between this node and Veo Upsample.

Which of the two should you use? They overlap, so here's the honest split. Get 1080p is the narrow, original-model-aware route to exactly one target: 1080p. Upsample covers 1080p, 4k and gif and doesn't ask which model made the original. If you know the source model and 1080p is all you need, this one is fine. If you want 4K, or a GIF, or you genuinely don't remember what generated the clip, use Upsample.

Inputs and outputs

• video_id - the ID of an existing, completed Veo video. Not the CDN URL. The client errors with An existing Veo video ID is required; do not enter a URL rather than silently failing, which is the version of this mistake you want.
• model - veo3, veo3-fast, veo31 or veo31-fast, default veo31-fast. Matching the model that made the original is the point of the field.

Outputs are status, task_id, video_url, trace_id. Submission returns pending and an empty video_url - that's normal. Take task_id to Veo Retrieve Task for the upgraded file, then into Veo Load Video if you want it saved.

Install and key

ComfyUI Manager → Custom Nodes → search Veo → publisher acedatacloud, package Veo by Ace Data Cloud → install, restart. Or:

cd /path/to/ComfyUI/custom_nodes
git clone https://github.com/AceDataCloud/VeoComfyUI.git
cd VeoComfyUI && python -m pip install -r requirements.txt

One dependency, requests. Nothing to download, no GPU. It does require ComfyUI 0.39.0 or newer for the native VIDEO type. Credentials live in the process environment:

export ACEDATACLOUD_API_KEY='paste-your-key-here'
python main.py

Where people get burned

This is not video upscaling the way you're used to it. There's no SeedVR2-style restoration pass happening here, no detail invented, no faces rewritten - you're paying the provider for a higher-resolution re-encode of what Veo already produced. That's the difference between "more pixels" and "more detail," and it's worth being clear which one you actually want. If the source clip is soft and the composition is wrong, 1080p won't rescue it. Better move: request 1080p (or 4k) at generation time on a veo31 model and skip this step entirely.

Second: the ingredients model. If your clip came from Veo Ingredients to Video, this node refuses it - the client's own error says the ingredients model can't upscale a prior video. Route those through Upsample instead.

Third, the usual. It wants a video ID, so keep the task record around rather than only the download link. It's a paid, one-shot submission, and it's an output node - it fires on Queue Prompt whether or not anything downstream reads its outputs, so mute it while you're wiring the graph. If you're waiting on a render, rerun Retrieve against the same task ID; nothing here resubmits for you.