Callaba
PricingSign inStart in the cloud for free
LIVE DELIVERY PLANNER

See where streaming bandwidth actually goes

Model source ingest, average delivery throughput, data per viewer, aggregate transfer, and recording before choosing a node or CDN plan.

Calculate my live path
Live streaming bandwidth flow1 source feeds send 6.6 Mbps of planned ingest into Callaba. Delivery to 1000 concurrent viewers produces 3.85 Gbps of planned average egress.
A planning baseline for average throughput and transfer—not a CDN quote or a guaranteed capacity limit.
YOUR BANDWIDTH MODEL

Separate ingest from viewer delivery

Source bitrate sizes the incoming path. Average delivered bitrate and concurrency size egress. Keep both visible—the larger number is not automatically the more fragile one.

Planned source ingest6.6 Mbps

1 feeds with 10% headroom

Planned average egress3.85 Gbps

Average delivered bitrate × simultaneous viewers + headroom

Data per viewer3.47 GB

For 2 hours at the modeled average bitrate

Aggregate delivery transfer3.47 TB

Viewer transfer only; requests, logs, origin shielding, and retries vary

Source ingest transfer5.94 GB

Incoming source data with selected headroom

Recording media baseline5.4 GB

One copy of every source feed

Transfer formulaGB = Mbps × hours × 0.45 × streams × headroom
Launch Callaba in the cloudPlan a self-hosted node
READ THE NUMBER CORRECTLY

Bandwidth is a model until the real path is measured

  • ABR delivery: use average delivered bitrate for egress, not the sum of every ladder rendition.
  • Origin work: a packager or origin may transfer more than viewer egress alone suggests, especially with cache misses and multiple CDNs.
  • Variable bitrate: average transfer and instantaneous peaks are different capacity questions.
  • Failover: simultaneous primary and backup paths need separate headroom and rehearsal.
  • Pricing: this page provides no CDN, cloud, storage, or network cost guarantee.
FROM ESTIMATE TO ACCEPTANCE

Test the peak composition, not one idle stream

  1. 01

    Measure sources

    Record real average and peak media bitrate after the encoder stabilizes.

  2. 02

    Build the ladder

    Create only the renditions justified by devices, networks, and viewer evidence.

  3. 03

    Load the path

    Run peak feeds, viewers, recording, monitoring, and failover together.

  4. 04

    Compare telemetry

    Match node, origin, CDN, and player data on one incident timeline.

KEEP PLANNING CONNECTED

Use the calculator with the media guides

PLANNING FAQ

Streaming bandwidth calculator questions

How is streaming bandwidth calculated?

The planner multiplies bitrate by simultaneous streams or viewers, then adds the selected network headroom. Data transfer uses 0.45 decimal GB for each Mbps-hour.

Should I use peak or average bitrate?

Use a measured source bitrate for ingest and a measured or modeled average delivered bitrate for viewers. Variable bitrate peaks, protocol behavior, and traffic bursts still require separate capacity testing.

Does the estimate include CDN or cloud pricing?

No. It calculates throughput and data volume, not a vendor bill. Pricing depends on region, committed usage, request volume, cache behavior, taxes, and the selected provider contract.

Is the result a guaranteed capacity requirement?

No. It is a transparent planning baseline. Validate the full rendition ladder, concurrent viewers, failover, recording, protocol overhead, and real network behavior before production.