BHuman 1 credit per personalized video vs a Sume per-recipient clip

BHuman lists 1 shared credit per personalized video, so Growth works out to $0.39 each. A Sume 10-second Plus clip per recipient costs $2.45; Standard is $1.84.

4 min readSume
All posts

The short answer

BHuman's pricing page states that one personalized video uses one shared credit, which puts its Growth plan ($39 for 100 credits) at $0.39 per video. A Sume avatar clip generated per recipient is a fresh render priced by the second: 10 seconds is $1.84 on Standard or $2.45 on Plus. They solve different problems, so decide which one you are buying before comparing the numbers. Source: BHuman pricing (read 2026-10-04).

What BHuman prints

The page lists Free at $0 with 15 credits, Growth at $39 with 100, Scale at $99 with 300 and Ultimate at $150 with 500. It also states that 1 Speakeasy minute equals 15 shared credits, and API access is listed on Ultimate.

BHuman plans (read 2026-10-04)
PlanPriceCreditsCost per personalized video
Free$015$0
Growth$39100$0.39
Scale$99300$0.33
Ultimate$150500$0.30

What a per-recipient clip costs on Sume

Per-recipient clips on Sume are separate talking-video jobs, one per script. A mail-merge style batch is therefore a loop of requests, each with its own script text for that person. Costs add up with seconds, so keep recipient clips short:

Sume per-recipient clips, no product image (read 2026-10-04)
Clip lengthStandardPlusFor 100 recipients on Plus
4 seconds$0.736$0.98$98.00
10 seconds$1.84$2.45$245.00
15 seconds$2.76$3.675$367.50

The Speakeasy minute

BHuman also lists 1 Speakeasy minute as 15 shared credits. On Growth, 100 credits is 6.67 Speakeasy minutes, which is $39 / 6.67 = $5.85 a minute. A rendered minute on Sume is $11.04 on Standard, so the live-style minute looks cheaper on paper, but the two are different products and you should compare finished clips of the length you ship. For 100 recipients with a 4-second Standard greeting, Sume totals 100 x $0.736 = $73.60.

Where the difference comes from

If a vendor reuses one base recording and swaps a name, the unit cost can be a fraction of a full render. Sume does not publish a name-swap mode in its avatar docs I read, so each recipient is a new render and the cost scales with length. That makes Sume the better fit when the whole script differs per person, and a shared-credit plan the better fit when only a few words change.

Whichever you pick, set a spend cap before looping. Submit with an Idempotency-Key so a retry does not bill twice, and read the limits by plan to size the queue.

Sources

Related posts

More in Comparisons

All Comparisons posts

Written by Sume