A four-person, thirty-minute video call costs $0.20 on one published price list and $1.92 on another. Same four people, same half hour, list prices as published in October 2026.

The gap is not the rate. It is what each provider counts. Per participant minute pricing looks like one small number, usually around $0.004, but the bill is that number multiplied by a count, and the count grows faster than the meeting does. This post takes the meter apart. For what it adds up to over a month at enterprise scale, see what enterprise teams actually pay per minute at scale.

What per participant minute pricing actually counts

The unit is simple once it is written down. Twilio defines a participant-minute as "the time that a participant remains connected to a Video Room, measured in minutes". Daily puts it as the number of participants multiplied by the meeting length.

So the first multiplier is the number of people. A thirty-minute meeting with four people is 120 billable minutes. The meeting lasts half an hour; the bill counts two hours. Add a fifth person and the same meeting is 150.

Most published rates sit in a narrow band once you line them up:

Provider

Video rate per participant-minute

Worth knowing

Twilio Video

$0.004

TURN relay included

Daily

$0.0015–$0.004

Graduated; up to 63% off at 50M+ minutes a month

Vonage Video API

$0.0041

A participant is "a connection through the API"

Azure Communication Services

$0.004

Audio and video billed at the same rate

Amazon Chime SDK

$0.0017

Billed in 6-second increments, whatever media is used

Cloudflare RealtimeKit

$0.002

Audio-only participants $0.0005

If the count stopped at people, budgeting would be easy. It does not.

Multiplier two: what each person receives

Some providers do not bill the person at all. They bill what the person subscribes to.

Agora says plainly that it calculates usage "based solely on a user's subscriptions in the channels they join. Whether they publish streams does not matter." The rate then depends on the aggregate resolution of everything that user is watching at once, the total pixels across every video tile on their screen. Under Agora's published rules, up to 921,600 pixels (one 720p stream) is billed as HD; up to 3,686,400 is billed as 2K.

Now take the four-person call in a gallery view. Each person watches the other three. If those three tiles are sent at 720p, each viewer is receiving 2,764,800 pixels, which is the 2K tier at $15.99 per 1,000 minutes. Send the same tiles at 360p and the total is 691,200 pixels, billed as HD at $3.99. Same call, same people, four times the rate, decided by a layout setting.

ZEGOCLOUD shows the other version of the same idea. Its former billing method counted every stream each user subscribed to: "total service minutes = N × (N-1) × M". Five people talking for ten minutes was 200 service minutes under that rule, against 50 under the per-user method it uses now.

Streams are the number to watch, because they grow much faster than people:

People in the call

Participant-minutes per minute

Subscribed streams per minute

2

2

2

4

4

12

8

8

56

16

16

240

Even where your provider bills per person, this quadratic is still in the system. It is the reason media server bandwidth scales with viewers, not publishers, and someone pays for it somewhere.

The practical consequence for a buyer: on subscription-based pricing, decisions that look like product design, such as the default gallery size, the tile resolution or whether screen share is on, are pricing decisions.

Multiplier three: every add-on runs its own meter

The base rate covers people being connected. Almost everything else is metered separately, and the meters do not share a unit.

  • Per participant. Twilio charges $0.004 per participant-minute to record individual tracks, the same rate as the call itself. Daily bills real-time transcription at $0.0059 per unmuted participant-minute.
  • Per room. Twilio charges $0.01 per composed minute to turn those tracks into one video file. Daily charges $0.01349 per recorded minute; Vonage $0.0363 per minute for an HD composed archive.
  • Per gigabyte or per day. Storage, egress and relay traffic sit outside the minute meter entirely.

On the same four-person, thirty-minute call on Twilio's list prices: the call is $0.48, recording every participant adds $0.48, and composing one file adds $0.30. Recording alone takes the bill from $0.48 to $1.26, more than 2.6 times the headline. Storage, egress and relay come on top; they are priced line by line in what your video bill actually adds up to.

One call, seven price lists

Put the three multipliers together and the same thirty minutes looks like this at list price, before free tiers or volume discounts:

Provider and setting

Arithmetic

Cost of the call

Amazon Chime SDK

120 × $0.0017

$0.20

Cloudflare RealtimeKit

120 × $0.002

$0.24

Twilio, Daily (list), Azure

120 × $0.004

$0.48

Vonage

120 × $0.0041

$0.49

Agora, three 360p tiles each

120 × $3.99 ÷ 1,000

$0.48

Agora, three 720p tiles each

120 × $15.99 ÷ 1,000

$1.92

Twilio with track recording and composition

$0.48 + $0.48 + $0.30

$1.26

None of these numbers is large. That is the trap. Per participant minute pricing is designed to look like a rounding error per call, and it is one. The bill is what happens when every multiplier above is applied to every call, every day.

When per participant minute pricing is the right deal

This is not an argument against the model. For a lot of products it is the best one available.

There is no idle cost: a month with no calls costs nothing, and most providers include free minutes (Daily and Agora each list 10,000 a month). Volume discounts are real; Daily's graduated pricing reaches 63% off list. And relay, scaling and operations are bundled into the rate rather than becoming your team's job. For low, irregular or early-stage volume, that is hard to beat.

The trap is narrower than the model. It is budgeting with meeting-minutes × rate, when the real formula is:

participants × minutes × rate for the billing unit, plus every add-on on its own meter.

What to check on a per participant minute price page

Six questions turn a headline rate into a forecast:

  • What is the billable unit? A connected participant, a subscribed stream, or the aggregate resolution a user receives?
  • Is audio-only cheaper? Some providers charge less for it (RealtimeKit, Daily); some charge the same (Azure, Chime).
  • What is the rounding increment? Chime bills in six-second increments; check whether others round up to the minute.
  • Which add-ons are per participant and which per room? Recording, composition and transcription rarely share a unit.
  • Is relay traffic included? Twilio lists TURN relay as included; on per-gigabyte models, relay traffic is a cost of its own.
  • Where do discounts start? List price is rarely the price at volume, so ask for the tier table, not the headline.

The Bottom Line

Per participant minute pricing bills people, and sometimes the streams between them, not meetings. Every extra person multiplies the minutes, subscription-based models multiply them again by what each person watches, and recording and transcription each run their own meter. Model the count before the rate, and the bill stops being a surprise.

What's Next

Once you can count the minutes, the next question is when paying for them stops making sense. The crossover math compares per-minute, per-user, per-gigabyte and flat pricing at the same usage.

Frequently Asked Questions

How does per participant minute pricing work?

You are billed for each participant for each minute they are connected. A 30-minute call with four people is 120 participant-minutes; at $0.004 that is $0.48. Some providers instead bill what each participant subscribes to, which can raise the count further.

Why is my video API bill higher than I expected?

Usually because the forecast multiplied meeting length by the rate. The real count is participants × minutes, sometimes multiplied again by subscribed streams or resolution tiers, plus recording, composition and transcription on separate meters.

Is audio billed the same as video?

It depends on the provider. Azure Communication Services bills audio and video at the same rate, and Amazon Chime SDK bills per attendee regardless of media. Others publish lower audio-only rates, such as Cloudflare RealtimeKit at $0.0005 against $0.002 for video.

Does video resolution change the per-minute price?

On some pricing models, yes. Agora bills each user on the total resolution of all the streams they receive, so three 720p tiles fall in its 2K tier at $15.99 per 1,000 minutes, while three 360p tiles are billed as HD at $3.99.

Are recordings billed per participant?

Sometimes. Twilio bills individual track recording per participant-minute, then charges again per minute to compose a single file. Others bill per recorded minute of the room. Check which unit applies before estimating.

Is per-minute pricing or flat licensing cheaper?

Per-minute is cheaper at low or irregular volume because there is no idle cost. Flat licensing becomes cheaper once steady usage pushes the per-minute bill above the licence fee. Samvyo, based on SFU architecture, is offered with flat licensing rather than per-minute billing, so it is worth comparing against your measured participant-minutes rather than meeting-minutes.