Download Workflow
Download JSON or search “Causal Forcing” in Template Library
How it works
Unlike standard video generation which processes all frames in parallel, Causal Forcing treats video generation as a sequential process:- The model takes an input image as the first frame
- It generates the next frame conditioned on the previous one
- Each new frame becomes the input for the next prediction
- This repeats for the desired number of frames
Learn about Subgraph
This workflow uses a Subgraph node for modular processing. Check out the Subgraph documentation to learn how to customize and extend the workflow.
Causal Forcing vs Causal Forcing++
Using the workflow
Inputs
The workflow accepts a single input image (the first frame) and a text prompt describing the desired video content (optional).WAN I2V subgraph parameters
These are exposed as controls on the blueprint subgraph node:Steps to run
- Load an image — use the LoadImage node to load your starting frame
- Write a prompt (optional) — describe the desired video content
- Set duration — how many frames to generate
- Select models — choose Wan2.1 I2V checkpoint, CLIP, and VAE
- Choose mode — Causal Forcing or Causal Forcing++ (set via the subgraph’s internal configuration or a Causal Forcing-specific input if available)
- Run — frames will be generated sequentially and saved to
ComfyUI/output/
Model downloads
Download the Wan2.1 I2V model and required files. Place them in the correspondingmodels/ subdirectories.
Wan2.1 I2V
Wan2.1 I2V 14B
wan2.1_i2v_480p_14B_fp16.safetensors — Wan2.1 I2V 14B checkpoint
Wan2.1 I2V 1.3B
wan2.1_t2v_1.3B_fp16.safetensors — Wan2.1 1.3B checkpoint (8GB VRAM minimum)
CLIP and VAE
CLIP (google-bert)
google-bert/bert-base-uncased — CLIP text encoder
VAE (Wan2.1)
Wan2.1_VAE_bf16.safetensors — Wan2.1 VAE