Multi-shot narrative progression
Built for story-driven shorts that need to cut between wide, medium, and close shots within one pass. Spelling out shot order in the prompt gets you closer to a storyboard structure on the first try.
Alibaba Tongyi · Wan 2.7
Wan 2.7 — Alibaba Tongyi's video model for multi-shot film narrative and shot continuity
What is Wan 2.7?
Wan 2.7 is the newest generation in Alibaba Tongyi's Wanxiang (Wan) video model series, built for shorts with high demands on multi-shot film narrative and shot continuity. It suits storyboard-style concept films, brand mood shorts, and tests that need to advance shot language within a single pass; new projects should default to 2.7 within the Wan family. Compared with Wan 2.6, 2.7 is stronger on narrative completeness and shot continuity. Exact duration, references, and resolution follow the current tier in the iMini workspace. Select Wan 2.7 in the iMini video workspace to use it.
- Vendor
- Alibaba Tongyi / Tongyi Wanxiang
- Positioning
- Newest Wanxiang generation · multi-shot narrative
- Clip length
- Follows workspace tier
- Resolution
- Follows selectable workspace tier
- References / modality
- Text / image / first-last frame and multi-image reference (follows workspace)
- Best for
- Multi-shot film narrative and shot-driven shorts
Stronger shot continuity
Suited to the ‘this shot flows into the next’ demand in brand mood pieces and concept ads. Mood, subject, and camera logic are driven by a single generation chain.
Latest in the Wanxiang family
Wan 2.7 represents the current leading edge of the Wanxiang video lineup. When you need stronger narrative or reference control, compare 2.7 against 2.6 by workspace tier.
Division of labor with Seedance and Kling
Compare Seedance 2.5 when you need a longer single-pass brand narrative in one generation; prefer Kling 3.0 for complex body motion and action sequences.
How to choose vs. Wan 2.6 and Seedance 2.5
All are mainstream contemporary video choices. The differences are mainly Wanxiang generation, clip length, and whether you value multi-shot narrative or a longer single-pass output more.
| Dimension | Wan 2.7 | Wan 2.6 | Seedance 2.5 |
|---|---|---|---|
| Clip length | Follows workspace tier | Up to ~15s (typical official tier) | Native ~30s single pass |
| Resolution | Follows workspace tier | Up to 1080p · ~24fps | HD tiers available (follows workspace) |
| Native audio | Follows current workspace capability | Native A/V and lip sync (per official description) | Follows current workspace capability |
| Multimodal references | Text / image / first-last frame and multi-image (follows workspace) | Text / image / reference video / audio | Full-modal multi-reference (~50 per official spec) |
| Motion & physics | Multi-shot narrative and shot continuity first | Multi-shot narrative with character-reference footage | Longer-segment consistency first |
| Prefer when | Latest Wanxiang multi-shot film narrative | Native A/V and reference-video control already suffice | Generating a full ad segment / short-drama beat in one pass |
Prefer Wan 2.7
For new projects in the Wan family where multi-shot narrative and shot continuity are the main need.
Prefer Wan 2.6
When the workspace already has the 2.6 tier open, and native A/V plus reference-video control already meet the deliverable.
Prefer Seedance 2.5
When you need a native ~30s single pass with larger reference scale to tell a beat in one go.
Using Wan 2.7 on iMini
Three steps from opening the workspace to exporting a clip.
01
Open the video workspace
Go to iMini video creation and select Wan 2.7.
02
Write a prompt or upload references
Spell out shot order, subject, and mood; upload first-frame or multi-image references if you have them.
03
Generate and export
Export once shot continuity and narrative pacing meet the bar. If not, revise the shot descriptions and references first.
Using Wan 2.7 on iMini
Quotas, specs, migration, and how to choose.
Generate Wan 2.7 free on iMini
Latest Wanxiang multi-shot film narrative. Open the video workspace to use it—no separate vendor API key needed.
No separate vendor API key needed.