Diffusion Forcing, Self Forcing, Context Forcing, Wave Forcing. Behide these terms are methods that improve video generation making it faster, longer or more accurate. But “forcing” is not one shared algorithm or one recipe. These methods change different parts of the process: how a model learns, what it remembers, and how the work of generating a video is scheduled.
Some teach a model to keep going after its own imperfect frames. Others decide which parts of the past deserve space in memory, or spread denoising across several GPUs. They can all help with faster or longer video, but they don't solve the same problem.
Here is a way to keep them apart, with a short explanation of each method and links to the papers, demos and code.
TL;DR: “Forcing” covers several approaches to video generation, not one algorithm. The methods below tackle noisy context, accumulated errors, limited memory, long sequences and inference speed. Use the comparison table to see what each one changes; reported speed gains only make sense alongside hardware, resolution and generation settings.
Forcing methods at a Glance
“Training” below means the method introduces a training or distillation recipe. Training-free methods modify an existing generator at inference time.
Method | Main change | Main aim | Training? |
|---|---|---|---|
Diffusion Forcing | Different noise levels across tokens | Flexible lengths and guided trajectories | Yes |
DFoT | Flexible history + History Guidance | Long-video consistency and motion | Yes |
Self Forcing | Training on self-generated history | Reduce train–test mismatch; fast streaming | Yes |
Rolling Forcing | Joint denoising of neighboring frames | Long streams with less drift | Yes |
Self-Forcing++ | Short teacher supervises long student rollouts | Minute-scale generation | Yes |
Deep Forcing | Persistent context + selective KV-cache pruning | Longer generation with bounded cache | No additional training |
Causal Forcing | Causal teacher for few-step initialization | Better fast autoregressive generation | Yes |
Context Forcing | Long-context teacher + compressed memory | Consistency over longer histories | Yes |
Hybrid Forcing | Compact long-term state + sparse recent attention | Long video with bounded memory | Yes |
Any Forcing | Flexible step counts + selected history | One-step and few-step output | Yes; memory selection is training-free |
Wave Forcing | Overlapping denoising across model replicas | Higher multi-GPU streaming throughput | Yes |
Trajectory Forcing | Reuse intermediate denoising predictions | Better context for later chunks | Yes |
Relax Forcing | Initial, recent and selected history frames | Long-video motion and consistency | No additional training |
One-Forcing | Adversarial objective + framewise distillation | Stable one-step generation | Yes |
Disen-Forcing | Separate anchoring and motion attention heads | Preserve identity without freezing motion | Yes |
Causal Forcing++ | Causal consistency distillation | Lower first-frame latency; cheaper initialization | Yes |
Forcing methods
1. Diffusion Forcing
It is an earlier foundation that makes it easy to trace where some of these ideas came from. Diffusion Forcing blends sequential generation with diffusion to train the model to deal with uneven noise across tokens, letting it predict future steps while earlier ones are still a little noisy. That unlocks variable-length generation ‒ like long, smooth videos that don't fall apart past their training limit ‒ and makes it much easier to guide outputs toward a target for planning tasks.
Diffusion Forcing Paper
Diffusion Forcing Project Website
Diffusion Forcing GitHub
Diffusion Forcing Transformer (DFoT)
The follow-up, Diffusion Forcing Transformer (DFoT), brings this idea to transformer-based video diffusion. It can condition on more than a fixed story ‒ on different numbers or subsets of past frames. Its History Guidance combines those different views of the past to improve consistency and motion, and help the model continue much longer videos.
DFoT Paper
DFoT Project Website
DFoT GitHub
2. Self Forcing
An autoregressive video model trained with clean, real context frames has a slightly unfair advantage: when it starts generating, it has to continue from its own imperfect work instead. Self Forcing brings that situation into training. The model generates a sequence using its own earlier outputs, while a video-level objective evaluates the result as a whole. A few-step diffusion model, gradient truncation, and KV caching keep the process practical. This makes fast streaming generation possible, although quality can still drift when the video runs much longer than the clips used in training.
Self Forcing Paper
Self Forcing Project Website
Self Forcing GitHub
3. Rolling Forcing
This method doesn’t finish one frame and then completely move on. It denoises several neighboring frames together, with earlier ones closer to completion and later ones still noisier. Letting those frames influence each other helps stop a small mistake from simply being passed down the line. It also keeps cached information from the first frames as a reference for the rest of the video. Training on self-generated histories prepares it for that rolling process, supporting multi-minute streams with less accumulated drift.
Rolling Forcing Paper
Rolling Forcing Project Website
Rolling Forcing GitHub
4. Self-Forcing++
A teacher that only understands short clips can still help a student make a long video. Self-Forcing++ has the student generate a longer sequence, then samples short sections for the teacher to supervise. This gives the student feedback on the problems that appear later in its own generation, without needing a long-video teacher or a new long-video dataset. It extends Self Forcing toward minute-scale generation, using historical KV-cache information.
Self-Forcing++ Paper
Self-Forcing++ Project Website
Self-Forcing++ GitHub
5. Deep Forcing
Deep Forcing changes what the model remembers, without retraining it. Its Deep Sink keeps a substantial portion of cached history as a persistent reference and adjusts the timing information attached to it. Participative Compression then checks which cached tokens recent frames actually use and removes less useful ones. The aim is to preserve enough context for a scene to stay recognizable without letting redundant or degraded history keep steering the next frames. The authors demonstrate extending a model trained on five-second clips to videos longer than a minute.
Deep Forcing Paper
Deep Forcing Project Website
Deep Forcing GitHub
6. Causal Forcing
A teacher that can look at the whole video has information a streaming student will never have. Causal Forcing addresses this mismatch when initializing the fast, few-step student: it uses an autoregressive teacher that follows the same past-to-future order. After that initialization, it applies the distribution-matching stage used in Self Forcing. The change improves the starting point for fast video generation. It can therefore be combined with methods such as Rolling Forcing to extend the video length.
Causal Forcing Paper
Causal Forcing Project Website
Causal Forcing GitHub
7. Context Forcing
This method gives both the student and teacher a longer view, so supervision can account for earlier subjects and scenes. Its Slow-Fast Memory system compresses redundant visual history to keep that longer context manageable, which works better than just letting the cache grow with every new frame.
Context Forcing Paper
Context Forcing Project Website
Context Forcing GitHub
8. Hybrid Forcing
Keeps a compact running state of the older history through linear temporal attention, while block-sparse attention handles recent frames without checking every possible connection. It distills the model in stages, first with dense attention and then with the hybrid design. The result is a generator that can keep drawing on the past without keeping all of it in a growing cache.
Hybrid Forcing Paper
Hybrid Forcing Project Website
Hybrid Forcing GitHub
9. Any Forcing
The idea is to train one model to work at different step counts, using adversarial objectives to improve realism, keep predictions consistent across step counts, and strengthen the first frame. For longer videos, Any Forcing also chooses which historical states are still useful. That memory selection needs no additional training, though the generator itself does.
Any Forcing Paper
Any Forcing Project Website
10. Wave Forcing
A video chunk does not have to be completely finished before it can help generate the next one. Wave Forcing lets newer chunks use earlier, cleaner chunks while those are still being denoised. It then spreads the staggered stages across several full copies of the model on different GPUs. Once the pipeline fills, it can output one chunk per concurrent forward round, without reducing the whole process to one-step denoising.
Wave Forcing Paper
Wave Forcing Project Website
Wave Forcing GitHub
11. Trajectory Forcing
Usually, the next video chunk sees the finished result of earlier chunks. Trajectory Forcing keeps the intermediate predictions that produced them around and uses selected ones as context for what comes next. It first learns from pseudo-trajectories built from real videos, then from its own generated trajectories. To avoid attending to every intermediate state, each denoising update selects one prediction from each retained earlier chunk.
Trajectory Forcing Paper
Trajectory Forcing Project Website
12. Relax Forcing
Relax Forcing gives different parts of memory different jobs: initial frames anchor the scene, recent frames keep movement continuous, and selected frames in between provide useful motion history. It chooses that middle group to stay relevant without repeating what the recent context already contains. This is an inference-time memory change, so it can improve an existing model without retraining it.
Relax Forcing Paper
Relax Forcing Project Website
Relax Forcing GitHub
13. One-Forcing
One-Forcing adds an adversarial training objective to distribution-matching distillation, giving the student model another signal for producing realistic video in that single step. It also generates autoregressively at the latent-frame level rather than in larger chunks, which makes the adversarial training more stable.
One-Forcing Paper
One-Forcing Project Website
One-Forcing GitHub
14. Disen-Forcing
Keeping the first frames in memory can help preserve a scene, but making every attention head look at them can also hold back movement. Disen-Forcing separates those jobs during distillation: a small set of heads handles long-range semantic anchoring, while the others focus on local motion. It changes how context reaches those heads and adds a training constraint to keep the two roles distinct, aiming for consistency without turning the video into a nearly still image.
Disen-Forcing Paper
Disen-Forcing Project Website
15. Causal Forcing++
Causal Forcing++ pushes the same idea toward generating one frame at a time in just one or two sampling steps. It replaces the original initialization procedure with causal consistency distillation, which learns from a single teacher step at a time instead of requiring a large precomputed collection of complete denoising trajectories. That reduces the work needed to prepare the student and makes the more aggressive few-step setup practical. In the authors’ comparison, the two-step frame-wise model halves first-frame latency relative to their four-step chunk-wise baseline.
FAQ
What does forcing mean in video generation?
It is a label used by several research methods, not one standard algorithm. Some change the training setup, others manage past context or schedule denoising. The shared name does not mean they are interchangeable.
What is the difference between Diffusion Forcing and Self Forcing?
Diffusion Forcing trains a sequence model with different noise levels across tokens. Self Forcing trains an autoregressive video model on its own generated history, so it learns to continue from the imperfect context it will encounter at inference.
Do all forcing methods need extra training?
No. Many introduce a training or distillation recipe, but some change inference instead. Deep Forcing, for example, manages the KV cache without additional training.
Does faster video generation mean lower latency?
Not necessarily. Throughput measures how much video a system produces over time; latency measures how long you wait for a result. A pipeline can raise throughput after it fills while still taking time to produce its first chunk. Always check GPU count, resolution, denoising steps and what timing the paper reports.
Can these methods generate unlimited video without losing consistency?
Being able to keep generating is not the same as keeping a scene coherent indefinitely. Errors can accumulate, and a fixed memory budget may discard useful details. Check how long the authors actually evaluate, rather than treating long-video or infinite-video generation as a guarantee.





