Veo 3.1 videos are stored 2 days: download them, and what Sume does

Download a Veo 3.1 video within 2 days of generating it. The Gemini API docs say generated videos are stored on the server for 2 days, and that referencing a video for extension resets its 2-day storage timer. After that window the file is not there to fetch.

Sume works differently: a finished job returns a Sume-hosted artifact. Facts below are from Google's Veo page and Sume's Video 1.0 docs, read 2026-10-01.

What exactly does Google say about the 2 days?

Two statements on the Veo page matter. Generated videos are stored for 2 days. If a video is referenced for extension, its 2-day storage timer resets, and the extended video is treated as newly generated. The page applies extension to videos that Veo itself generated.

What does a finished Sume job return?

Completed Video 1.0 jobs return Sume-hosted video artifacts, each with an id, a type, a url on media.sume.com and a content_type. The docs add one rule: treat artifact URLs as opaque, and do not parse paths for workspace, job or provider identifiers.

The docs I read do not state a retention window for those artifacts, so this post makes no claim about one. For what the docs do say about lifetime, see do Sume video URLs expire.

Does Sume offer Veo 3.1?

Not in the catalog I read. Sume resolves model ids from GET /v1/video-router/models, and ids not listed there are rejected on generate. If you want Sume to choose a family for you, send model: "sume/auto". The Veo-versus-Omni comparison is in Gemini Omni Flash vs Veo 3.1.

What should I do with a short-lived vendor file?

Copy it into storage you control the moment the job completes, and record the date. If you plan to extend a clip, do that before the 2 days end, because the timer only resets when the video is referenced.