Wan API Family
Use one EvoLink API to compare the Wan family across video and image workflows. Choose the right route first, then open pricing, comparison, or production guides when you need route-level detail.
3 routes
Cinematic video, daily video, and image generation
Unified API access
One key for all Wan models, async task pattern
Choose by workflow
Match route to task before integrating
Compare the Wan routes
Use workflow type first: newest video route, lower-cost video route, or image generation inside the same family.
| Route | Best for | Modality | Workflow type | Reference control | Pricing snapshot |
|---|---|---|---|---|---|
Wan 2.6 Latest cinematic | Cinematic multi-shot video, reference-video identity continuity, brand campaigns. | Video | Newest cinematic video route | Text, image, and reference video (wan2.6-r2v) | $0.0708/s |
Wan 2.5 Workhorse tier | Daily UGC, social feeds, SaaS video features, content volume with predictable unit cost. | Video | Daily production video route | Text and image inputs (no reference video at this tier) | $0.0708/s |
Wan Image Image family sibling | Text-to-image creation and image-to-image fusion for batch creative workflows. | Image | Image generation and image-to-image fusion | Text prompts and multi-image fusion inputs | $0.0208/image |
How to decide which Wan route to use
Follow these 4 rules to narrow down your choice.
Start with output type
Video or image? If your workload is image generation, go straight to Wan Image. Otherwise, compare video routes.
Then check quality tier
Cinematic multi-shot storytelling, reference video, brand campaigns — start with Wan 2.6. Daily UGC, social feeds, SaaS features — start with Wan 2.5.
Then check reference needs
If you need character identity continuity across episodes via reference video (r2v), Wan 2.6 is the only option.
Finally, consider iteration speed
For faster image-to-video and reference-video iteration, use Wan 2.6 Flash variants instead of the standard Wan 2.6 tier.
If you already know your workflow type, find the recommended starting point in the table below.
Choose a Wan route by workflow: cinematic, daily video, image, and migration
Match your primary workflow to the right Wan route.
| Your workflow | Recommended start | Good fit if... | Watch out for |
|---|---|---|---|
| Cinematic multi-shot video | Wan 2.6 | Brand campaigns, narrative storytelling, high-end output that needs cinematic quality | Higher per-second cost than Wan 2.5 for standard tier |
| Reference video continuity | Wan 2.6 (r2v) | Character identity must carry across episodes or scenes | Reference video has its own input-plus-output duration billing |
| Daily UGC and social content | Wan 2.5 | Predictable per-second cost, 5 or 10 second social clips, audio output | No reference video at this tier |
| Text-to-image and image editing | Wan Image | Batch creative workflows, campaign banners, product shots | Billed per image, not per second |
| Faster video iteration | Wan 2.6 Flash | Speed matters more than peak quality for i2v and r2v loops | Flash variants may trade some quality for speed |
Wan API workflows: cinematic video, daily content, reference video, and image generation
See how Wan routes fit into real production pipelines and content workflows.
Text-to-video storytelling
For brand campaigns, multi-shot narrative video, and cinematic output. Start with Wan 2.6 for the latest cinematic tier. Use Wan 2.6 Flash for faster iteration when testing concepts before final renders.
Image-to-video production
For turning product images, campaign stills, or concept art into motion. Both Wan 2.6 and Wan 2.5 support image-to-video workflows. Choose by quality tier: Wan 2.6 for cinematic, Wan 2.5 for daily volume.
Reference video and character continuity
For carrying character appearance across episodes, maintaining subject identity in a series, or brand mascot consistency. Wan 2.6 is the only Wan tier with reference video (wan2.6-r2v).
Batch image generation and creative refresh
For text-to-image creation, image-to-image fusion, campaign banners, product shots, and batch creative workflows. Wan Image handles image generation on the same account as Wan video routes.
Explore each Wan route
Use this page to compare, then visit individual route pages for pricing details, playground access, and integration guides.
Access Wan models through one EvoLink API
All Wan routes are available through a single EvoLink API key and async task endpoint. Switch between Wan 2.6, Wan 2.5, and Wan Image by changing the model parameter — no separate accounts or keys needed.
Switch model="wan-2.6" to model="wan-2.5" without rebuilding your integration.How to think about Wan API cost: cinematic video, daily content, and image generation
Cinematic quality amplifies per-second cost
Multi-shot storytelling, reference video, and brand campaigns work best with the latest cinematic tier. If output quality drives business value, Wan 2.6 quality may matter more than per-second savings.
Daily volume needs predictable unit cost
UGC pipelines, social content schedules, and SaaS video features generate high call volume. If the bottleneck is cost at scale rather than peak quality, Wan 2.5 keeps per-second cost defensible.
Image tasks use per-image billing
Text-to-image and image-to-image fusion are billed per image, not per second. Multi-image fusion costs the same as single-image generation. Budget separately from video workflows.
Pricing summary
This family page summarizes the pricing shape of the Wan lineup. The route pages own exact live pricing, and the dedicated Wan API pricing guide owns the full price breakdown. The short version: Wan 2.5 and the standard Wan 2.6 tiers share a predictable per-second video rate, Wan 2.6 Flash runs lower for image-to-video and reference-video iteration, Wan 2.6 reference video has its own input-plus-output duration logic, and Wan Image is billed per image rather than per second.
Wan 2.6
$0.0708/s
Latest cinematic tier. Standard per-second rate, plus Wan 2.6 Flash variants and separate reference-video billing logic.
Wan 2.5
$0.0708/s
Daily workhorse tier. Same standard per-second rate, tuned for 5 or 10 second social-style clips with audio output on current routes.
Wan Image
$0.0208/image
Image generation. Billed per image, not per second. Multi-image fusion costs the same as single-image generation.
Related Wan guides
The family page routes users to the right next question, not try to own every Wan intent itself.
Wan API Pricing Guide
Use the pricing guide for the per-second video rates, Wan 2.6 Flash ranges, reference-video billing, and Wan Image per-image rates.
Wan 2.5 vs Wan 2.6
Use the head-to-head guide when the decision is which Wan tier should own a specific workflow.
Wan 2.6 API Production Guide
Use the production guide for async orchestration, budget guardrails, and integration patterns for CTOs and engineers.
Wan 2.5 API Review
Use the review for a hands-on Python integration walkthrough and a head-to-head against Google Veo 3.
Wan API Family FAQ
Everything you need to know about the product and billing.