This page records the differences between the two Veo 3.1 channels APIYI used to provide: Official (this series) passed requests through to Google AI Studio, while Reverse accessed Google Flow. Both channels are now offline, so the comparison matrix and decision tree below are kept for historical reference only.
Full Comparison Matrix
Three-Step Decision Tree
1
Q1: Do you need frame-to-video capability?
- Yes → Use VEO 3.1 (Reverse)
-flseries (e.g.,veo-3.1-landscape-fast-fl); Official does not yet expose frame-to-video - No → Go to Q2
2
Q2: Does your frontend need a streaming sync progress bar?
- Yes (user-facing UI can’t go blank) → Use VEO 3.1 (Reverse)
/v1/chat/completionsstreaming endpoint - Backend tasked (queue consumer, batch production) → Go to Q3
3
Q3: Budget vs quality priority?
- Budget first ($0.15 vs $0.3 difference matters) → Use VEO 3.1 (Reverse), 50% lower price
- Quality / stability first (final delivery, 4K, strong instruction following) → Use Official (this series) with
veo-3.1-generate-preview - Iteration / preview → Use Official
veo-3.1-fast-generate-preview($0.3) or Reverse-fast($0.15)
Scenario-by-Scenario Recommendations
Can I use both channels together?
Absolutely. The two channels are independently routed:- Under the same account, a single Token (on the Default group) can call both channels simultaneously; billing is tracked per-call
- Switch the
modelfield as needed in your business code:- To use Official →
veo-3.1-fast-generate-preview/veo-3.1-generate-preview - To use Reverse →
veo-3.1-fast/veo-3.1-landscape/veo-3.1-fletc.
- To use Official →
Related Docs
- VEO 3.1 Official Overview — Official channel complete intro
- VEO 3.1 (Reverse) Overview — Existing Reverse channel complete intro
- VEO 3.1 Official Text-to-Video Playground
- VEO 3.1 Official Image-to-Video Playground
- VEO 3.1 (Reverse) Quick Start — Streaming sync usage
- VEO 3.1 (Reverse) Async API — Includes frame-to-video usage