30 seconds of video: Wan 3.0 at 720p is $3.75, two H3 Max jobs $3.00

One 30-second Wan 3.0 job at 720p costs $3.75 on Sume (30 seconds at $0.125). Two 15-second MiniMax H3 Max jobs at 768p cost $3.00 in total (15 seconds at $0.10 each, so $1.50 per job). The cheaper route has a seam and two chances for a subject to drift, so price is not the whole decision.

Both ids include audio. Wan 3.0 takes 2 to 30 seconds; H3 Max takes 5 to 15 seconds, so 30 seconds on H3 Max always means at least two jobs.

Cost and shape

Rates are provider list times 1.25, rounded up to the cent per job.

The seam

A stitched clip needs a join. You can end clip one on a frame you control and open clip two from that frame with frame_images, then cut or fade between them with a timeline render. That handles position and pose. It does not guarantee the same lighting, voice or background sound, since each job generates its own audio.

If the piece is a single moment, such as a product turning or a walk across a room, the single job is the safer pick. If it is two scenes, the cut is a feature, and the cheaper route is fine.

The retry cost

Failure economics differ. A bad 30-second Wan job wastes up to $3.75 at 720p. A bad 15-second H3 Max job wastes $1.50. If your hit rate is low, shorter jobs can cost less per usable second even when the list rate is higher. Measure your own hit rate on ten generations before you decide.

Questions to ask first

Before you pick on price, answer these.

If you are still torn, run one of each on the same brief and judge the pair side by side. The $4 or so that costs is small next to a wrong pipeline choice for hundreds of clips.

• Is the piece one moment or two scenes?
• Does the audio need to stay continuous across all 30 seconds?
• How often does your prompt produce a clip you would ship?
• Do you need references that only one of the two ids accepts?