How long can I extend a video with this template?

The workflow is tuned for up to 10 seconds per step and about 40 seconds total across iterations. You can run more steps, but visual quality and continuity may degrade as context drifts.

How do I keep characters and style consistent across steps?

Keep prompts consistent, describe key subjects and camera behavior clearly, and reuse the last 10 seconds as context via the Video Slice node. For stronger identity anchoring, attach one or more reference images to the GeminiVideoOmniV2 node.

Does the output include audio?

This template focuses on visual continuation. LoadVideo/SaveVideo in many ComfyUI setups export silent MP4s. If you need audio, keep your original track and re-sync or design new audio in post after export.

Can I branch the story and try alternative continuations?

Yes. Duplicate the GeminiVideoOmniV2 + SaveVideo segment, keep the same Video Slice tail input, and vary the prompt (and optional image refs). You’ll get multiple alternate continuations from the same context.

Gemini Omni 1.1 Flash: Video Extend

This ComfyUI tutorial workflow shows how to extend an existing video in coherent, story-aware chunks using the GeminiVideoOmniV2 node (Gemini Omni 1.1 Flash). It loads your clip with LoadVideo, extracts the final moments as context via Video Slice, and asks Gemini to continue the scene for up to 10 seconds per run. The model reads the last 10 seconds of visual context so characters, motion, camera framing, and scene layout carry forward naturally instead of restarting from scratch. SaveVideo then exports the extended result as a new clip.

Technically, the pipeline is a loop-friendly chain: LoadVideo → Video Slice (tail window) → GeminiVideoOmniV2 (prompted continuation) → SaveVideo. You can iterate this up to four times to build a 40-second story, or branch at any step by changing the prompt. The GeminiVideoOmniV2 node also supports optional image references, which you can attach mid-story to introduce new characters or props while maintaining continuity with the previous scene. The included MarkdownNote explains the required input asset path and tips for best results.

API

Use this workflow from code

Every Comfy workflow is a JSON graph. The payload below is this workflow, exactly as ComfyUI runs it — fetch it from the URL, keep it in version control, or load it in ComfyUI and run it node by node.

e2ceec4fc610.json

Fetching workflow JSON…

Run it from TypeScript or Python with the Comfy SDK. The same code targets Comfy Cloud or a ComfyUI you host yourself — only the base URL changes.

// Install (beta)
npm i @comfyorg/sdk

// Run this workflow (TypeScript)
import { Comfy } from "@comfyorg/sdk";

const client = new Comfy({ apiKey: "comfyui-..." });
const wf = await client.workflows.fromFile("workflow_api.json");
const job = await client.run(wf);
await job.getOutputs("<output-node-id>")[0].toFile("output.png");

The SDK takes a workflow in API format: open this workflow in ComfyUI and use File → Export Workflow (API).

Comfy Cloud API access requires a plan with an API key.

SDK docs Get an API key

FAQ

Frequently Asked Questions