Comparisons
How to choose between Wan 3.0 Video, Video LoRA and Pro LoRA
Compare APIXO’s three Wan 3.0 variants by inputs, resolution, limits and USD API rates, with reference-video and smart-duration billing examples.
APIXO Team
Start creating
Comparisons
Compare APIXO’s three Wan 3.0 variants by inputs, resolution, limits and USD API rates, with reference-video and smart-duration billing examples.
When choosing Wan 3.0 on APIXO, start with two questions: Do your references need to include a file or web link? Do you need 1080p output, or a 2K or 4K deliverable? These requirements narrow the choice more directly than the words “LoRA” or “Pro” in a name.
For file or link references, check Wan 3.0 Video first. For 2K or 4K output, Wan 3.0 Video Pro LoRA is the option among these three. If you only need image, video and audio references at up to 1080p, both Video and Video LoRA offer relevant settings; compare the same resolution tier and your own samples.
This article uses APIXO model pages, published schemas, API documentation and API pricing checked on October 21, 2026. It compares exposed inputs, parameters and billing conditions. It contains no controlled comparison of visual quality, completion time or reliability.
Generation modes: Text / Image / Reference to video
Image-to-video: 1–2 images: first frame + optional last frame
Fixed output duration: Integer 2–30 s; combined limit applies with reference video
Smart duration: Supported; API duration=-1
API defaults: resolution / duration: 1080p / 5 s
Output resolution: 480p / 720p / 1080p
Reference media: Images / Video / Audio; also a file or link
File / link references: At most 1 file or 1 link; mutually exclusive
Output resolution: 480p / 720p / 1080p
Reference media: Images / Video / Audio
File / link references: Fields not exposed in the public interface
Output resolution: 1080p / 2K / 4K
Reference media: Images / Video / Audio
File / link references: Fields not exposed in the public interface
Open the pages for Wan 3.0 Video, Wan 3.0 Video LoRA and Wan 3.0 Video Pro LoRA to inspect each option. The table describes APIXO’s published interfaces; it does not import capabilities from other platforms or upstream models.
The documentation for both LoRA variants explicitly says they do not accept custom LoRA configuration parameters. Their names do not mean you can upload LoRA weights, set a LoRA strength or train your own LoRA through these interfaces. See the published fields in the Video LoRA documentation and Pro LoRA documentation.
All three have three modes. Supporting images, video and audio does not mean every mode accepts every type of reference.
text-to-video requires a non-empty prompt, with a maximum of 20,000 characters. It does not accept image, video or audio reference URLs. If you have a product image or motion clip, use the appropriate image or reference mode instead of adding those inputs to a text-only request.
All three offer auto, 16:9, 4:3, 1:1, 3:4 and 9:16 aspect ratios. The API default is auto; specify the ratio when a landscape or portrait delivery format is already decided.
image-to-video requires 1–2 images: the first frame and an optional last frame. Its two-image limit is different from the ten-image limit in reference mode. It does not accept video or audio references. The prompt is optional; choose reference mode when the brief combines different media types.
For example, a product opening image and a closing composition can define the intended endpoints, with a prompt describing camera movement. Those frames constrain the input; the movement between them still needs inspection in the result.
reference-to-video requires at least one reference input. The prompt is optional. These limits apply to all three models:
Images — Maximum count: 10; Duration limits: No duration field
Videos — Maximum count: 5; Duration limits: Each 1–15 s; at most 15 s in total per media type
Audio files — Maximum count: 5; Duration limits: Each 1–15 s; at most 15 s in total per media type
Video additionally exposes file_urls and link_urls, with at most one item in either field. They cannot be used together in one request. A web-based brief may make Video’s link-reference route useful, but this does not guarantee access to every website, file format or private link. Supply accessible materials that meet the selected route’s requirements.
Fixed output seconds plus total reference-video seconds must not exceed 30 seconds. With 8 seconds of reference video, the fixed output can be at most 22 seconds. Asking for 30 output seconds would exceed the combined limit. Reference audio has its own 15-second total limit; do not add audio seconds to this video-duration formula.
Check the Video input documentation, Video LoRA documentation and Pro LoRA documentation. Where the public schemas do not specify media formats, file sizes or pixel limits, unspecified does not mean unlimited. Check the current entry point’s requirements before submitting.
All prices below are APIXO API usage prices in US dollars (USD), per billable second. They come from the APIXO Price column on the API pricing page, checked on the date above. They are not Market Price or Studio credits. The page states that Studio monthly credits do not apply to API, MCP, Skill or LLM calls, so do not convert these dollar figures directly into workspace credits.
480p — Video (USD/s): $0.05; Video LoRA (USD/s): $0.0525; Pro LoRA (USD/s): Tier not offered
720p — Video (USD/s): $0.10; Video LoRA (USD/s): $0.105; Pro LoRA (USD/s): Tier not offered
1080p — Video (USD/s): $0.20; Video LoRA (USD/s): $0.21; Pro LoRA (USD/s): $0.20
2K — Video (USD/s): Tier not offered; Video LoRA (USD/s): Tier not offered; Pro LoRA (USD/s): $0.23
4K — Video (USD/s): Tier not offered; Video LoRA (USD/s): Tier not offered; Pro LoRA (USD/s): $0.26
For each model, the three modes share the same unit rate at a given resolution. Reference mode can involve more billable seconds: actual reference-video seconds are charged together with output seconds. Images and audio add no separate billable seconds. Video’s files and links add none either. The API documentation gives the formulas.
Names do not predict price order. At 1080p, Video and Pro LoRA currently have the same rate, while Video LoRA costs $0.01 more per second. This is a published-rate comparison, not proof of better visuals, faster generation or better value for your task.
These examples use one API text-to-video or image-to-video request, five output seconds and no reference video. They multiply rate by duration; they are not actual invoices and do not include another generation after revisions.
480p — Video (× 5 s): $0.05 × 5 s = $0.25; Video LoRA (× 5 s): $0.0525 × 5 s = $0.2625; Pro LoRA (× 5 s): Tier not offered
720p — Video (× 5 s): $0.10 × 5 s = $0.50; Video LoRA (× 5 s): $0.105 × 5 s = $0.525; Pro LoRA (× 5 s): Tier not offered
1080p — Video (× 5 s): $0.20 × 5 s = $1.00; Video LoRA (× 5 s): $0.21 × 5 s = $1.05; Pro LoRA (× 5 s): $0.20 × 5 s = $1.00
2K — Video (× 5 s): Tier not offered; Video LoRA (× 5 s): Tier not offered; Pro LoRA (× 5 s): $0.23 × 5 s = $1.15
4K — Video (× 5 s): Tier not offered; Video LoRA (× 5 s): Tier not offered; Pro LoRA (× 5 s): $0.26 × 5 s = $1.30
Video and Video LoRA offer 480p and 720p for lower-resolution drafts. Pro LoRA starts at 1080p. If delivery requires 2K or 4K, calculate using Pro LoRA’s corresponding tier rather than comparing its 4K rate with another model’s 480p starting price.
For the same reference mode at 1080p, assume ten output seconds and five seconds of reference video in total:
Billable duration = 10 output seconds + 5 reference-video seconds = 15 seconds.
Video — Calculation: 15 s × $0.20/s; Estimated cost per API request: $3.00
Video LoRA — Calculation: 15 s × $0.21/s; Estimated cost per API request: $3.15
Pro LoRA — Calculation: 15 s × $0.20/s; Estimated cost per API request: $3.00
The five seconds are the sum of all reference clips. Add their durations, not their file counts. Charging only the ten output seconds would omit the input-video cost.
All three use duration=-1 for smart duration. Because output length is unknown before generation, the published formulas are:
With five reference-video seconds at 1080p and $0.20 per second, the pre-charge is 35 × $0.20 = $7.00. If a successful result is ten seconds long, the final charge is $3.00 and $4.00 is refunded. Ten output seconds are an assumption for the example, not a promised smart-duration result.
Budget separately for the balance needed to start the task and the cost settled after success. The 30-second combined limit for fixed duration is not the smart-duration pre-charge ceiling. Successful smart-duration responses expose data.billing for checking input-video, output and total billable seconds; do not treat a processing task’s pre-charge as its final bill.
Only Video exposes file and link reference fields among these three interfaces. If that context is essential, it is a clear selection criterion. Then choose 480p, 720p or 1080p and verify reference accessibility.
Pro LoRA offers the 2K and 4K tiers in this comparison. Start from the delivery requirement, such as a 4K file or more output pixels for later cropping. Higher resolution alone does not establish natural motion, consistent characters or more accurate detail.
If a task requires both file/link references and 4K output, none of these published interfaces covers both requirements together. Rework the materials or reassess the workflow before choosing; do not describe one model as satisfying both.
Video and Video LoRA share the generation modes, first/last-frame count and image/video/audio reference limits at these tiers. Video exposes more reference types and has the lower published API rate at each of these resolutions. That is useful when the verified capabilities meet your needs and single-request cost is your priority.
Whether Video LoRA produces results worth the difference for your characters, style or motion needs requires samples. This article cannot conclude that it guarantees steadier style or characters, or that it is not worth choosing. At 1080p, Pro LoRA can also enter the sample comparison; equal unit prices do not imply equal results, waiting times or retry counts.
Published parameters answer what can be submitted, which output tiers exist and how billing works. To compare results, hold materials, prompt, aspect ratio, duration and a shared resolution constant. Keep every relevant attempt and its settings, then check:
A matching seed does not guarantee identical output. A single success or failure cannot establish a lasting ranking for quality, speed or reliability.
Choose materials, mode and output specification first. API defaults are 1080p and five seconds. Set 480p explicitly for a draft instead of accidentally submitting at the default tier. Check the browser workspace’s displayed defaults separately; API defaults do not establish its current selections.
Canonical API model IDs are wan-3-0-video, wan-3-0-video-LoRA and wan-3-0-video-pro-LoRA. Preserve their case; the 2K/4K API values are 2k/4k. All three default to sound enabled. Video also exposes watermark, defaulting to false; the LoRA interfaces do not list that field. Do not copy it across or infer watermark behavior solely from its absence.
Start online with Wan 3.0 Video, or use the separate Video LoRA and Pro LoRA pages as needed. Before an API call, recheck APIXO API pricing, resolution, output duration and total reference-video seconds.
Pro LoRA and Wan 3.0 Prime are different versions. None of these specifications or prices establishes Prime’s capabilities or cost.
Build with APIXO
Explore image, video, and audio models in one place.