Vozo lip-sync minutes per plan vs Sume per-second lip sync

Vozo lists about 15 lip-sync minutes at $29 and 60 at $99. Sume bills H3 Max lip sync per second with no plan. The per-minute math and where each fits.

5 min readSume
All posts

Vozo's pricing page lists roughly 15 lip-sync minutes on its $29 Creator plan and roughly 60 on its $99 Studio plan, which works out to about $1.93 and $1.65 a minute if you use every minute. Sume's MiniMax H3 Max lip sync has no plan: it bills per second, which derives to $6.00 a minute at 768p. On paper Vozo is cheaper per minute at full use. The products also do different jobs, so the number alone should not decide it.

Vozo figures come from Vozo pricing, read 2026-10-06. Sume's per-second rates come from the Sume models docs, read the same day: a list rate of $0.05, $0.08 or $0.16 a second at 480p, 768p or 1080p, multiplied by Sume's 1.25 margin.

What does the arithmetic look like?

The table divides each Vozo plan by its listed lip-sync minutes and prices an equal number of Sume minutes at the three resolutions. All Vozo minutes are approximate on the vendor's page, so treat the Vozo column as an upper bound on value.

Vozo plans from https://www.vozo.ai/pricing and Sume rates derived from docs.sume.com (list x 1.25), read 2026-10-06. Per-minute figures computed by Sume.
OptionLip-sync allowanceCost per minute at full useNotes
Vozo Freeabout 2 minutes$0No API access
Vozo Creator, $29about 15 minutesabout $1.93API access listed
Vozo Studio, $99about 60 minutesabout $1.65API access listed
Sume H3 Max, 480ppay per second$3.75No plan, 5 to 14.8 s per clip
Sume H3 Max, 768ppay per second$6.00No plan
Sume H3 Max, 1080ppay per second$12.00No plan

Why are they not the same product?

Vozo's page frames its plans around translation and dubbing: it lists 111 source and 165 target languages for Translate and Dub, and visual translation in 58 source languages, with per-file limits of 60 minutes on Creator and 120 on Studio. Lip sync there belongs to a dubbing workflow on footage you upload.

Sume's H3 Max lip sync takes one still or a ready avatar plus an audio file you host on Sume, 5 to 14.8 seconds long and under 10 MB, and returns one talking clip. It is a building block: you produce the audio with Sume TTS or your own pipeline, cut it to length, and chain clips. It does not translate, it does not take a video, and it does not do a 60-minute file. If your need is a translated talk from existing footage, Vozo-style tools are built for that and Sume is not.

When is the pay-per-second shape the better fit?

Sume's clip window is the real constraint. A voiceover over 14.8 seconds must be split by sentence, and each part must be at least 5 seconds; the window post explains the cut rules. If a typical line of yours is 40 seconds, plan for three jobs, not one, and price accordingly.

A practical way to decide is to count your monthly lip-sync seconds for the last quarter. At 768p, $29 buys about 4.8 minutes of Sume lip sync ($29 divided by $6.00), so below roughly five clip-minutes a month pay-per-second is cheaper than the Creator plan, even before you count the minutes you would leave unused. Above that, a plan's per-minute rate is lower, but only if the product matches what you do. Check the output on your own faces and languages before you compare prices at all.

  • Spiky use. A plan's minutes are paid for whether or not you use them; a per-second route costs nothing in a quiet month.
  • Short, generated presenters. A 12-second welcome line at 768p is $1.20, with no allowance to manage.
  • Programmatic jobs. Each submit reserves the amount, captures it on completion and refunds it on failure (refund details).
  • Queued bursts. Excess jobs wait as queued instead of failing, per Generation admission.

Sources

Related posts

More in Comparisons

All Comparisons posts

Written by Sume