Simulcast and SVC for AI Voice Agents: Multi-Quality Streams in 2026

Voice agents started growing video avatars in 2025. By 2026 most production voice stacks include an optional video channel. Simulcast and SVC are how you ship that video without melting subscriber bandwidth.

What it is and why now

flowchart LR
  Mobile[iOS / Android SDK] --> WHIP[WHIP ingest]
  WHIP --> Mux[Mux / LiveKit]
  Mux --> Brain[AI brain]
  Brain --> WHEP[WHEP egress]
  WHEP --> Web[Web viewer]

Simulcast: the publisher sends 3 layers at different resolutions/bitrates; the SFU forwards the layer that fits each subscriber. Browser support is rock-solid in 2026.

SVC (Scalable Video Coding): the publisher sends one stream with multiple temporally/spatially scalable layers; the SFU peels off layers per subscriber. AV1 SVC and VP9 SVC are both shipping in Chrome and Safari 26.4 in 2026, though VP8 + simulcast remains the most reliable cross-browser baseline.

For voice-AI agents that include a video avatar (think Tavus, HeyGen, Hedra), you need at least one of these so a 4K subscriber gets 1080p and a mobile subscriber gets 360p without re-encoding.

How WebRTC fits AI voice (architecture)

A typical voice-with-avatar flow:

1. AI worker publishes audio (single Opus track) plus avatar video as a simulcast track with three layers.
2. SFU subscribes each user only to the layer that matches their bandwidth.
3. SFU watches `qualityLimitationReason` and re-routes layers automatically.
4. Subscribers re-render lipsync with RTP timestamps; jitter buffer keeps audio + video aligned.

For voice-only flows, simulcast is overkill — but the SFU still benefits from RTP timestamping and BWE.

CallSphere implementation

CallSphere is voice-first by default. Our /demo path is voice-only. For Real Estate OneRoof and Healthcare we add an opt-in avatar (Tavus) for high-touch interactions; that avatar publishes simulcast at 360p / 720p / 1080p. The SFU (LiveKit or our own Pion gateway) selects the layer per subscriber.

We default to VP8 simulcast for compatibility — across our 6 verticals and 37 agents, VP8 + simulcast handles every browser without negotiation pain. AV1 SVC remains an A/B test in 2026 because some older Android Chromes still struggle.

Code snippet (TypeScript, simulcast publish)

```ts const stream = await navigator.mediaDevices.getUserMedia({ video: { width: 1280, height: 720 }, audio: true }); const videoTrack = stream.getVideoTracks()[0];

const sender = pc.addTransceiver(videoTrack, { direction: "sendonly", sendEncodings: [ { rid: "h", maxBitrate: 1_500_000, scaleResolutionDownBy: 1 }, { rid: "m", maxBitrate: 500_000, scaleResolutionDownBy: 2 }, { rid: "l", maxBitrate: 150_000, scaleResolutionDownBy: 4 }, ], }).sender;

const params = sender.getParameters(); params.encodings.forEach((e) => (e.priority = "high")); await sender.setParameters(params);

const audioTrack = stream.getAudioTracks()[0]; pc.addTrack(audioTrack, stream); ```

Build / migration steps

1. Decide between simulcast (broad compat) and SVC (efficiency) — start with simulcast.
2. In Chrome/Safari, set `sendEncodings` with three layers.
3. On the SFU side, enable simulcast forwarding (LiveKit and mediasoup default-on).
4. Watch `qualityLimitationReason` per subscriber; if it stays at `bandwidth`, switch them to a lower layer.
5. Keep audio on a separate simple track — never simulcast Opus.
6. Run an A/B comparing AV1 SVC vs VP8 simulcast for your audience; cut over per-region.

FAQ

Does this matter if I am voice-only? Not directly — but the same SFU patterns help BWE. What's better, simulcast or SVC? SVC is more efficient on the wire; simulcast is more compatible. Can I mix simulcast and SVC? Yes, on the same connection — though tooling is uneven. Is AV1 ready for production? In 2026, mostly — older Android Chromes can struggle. Does this slow down voice latency? No — voice is on its own track and gets priority.

Sources

• https://www.forasoft.com/blog/article/webrtc-architecture-guide-for-business-2026
• https://w3c.github.io/webrtc-svc/
• https://www.digitalsamba.com/blog/the-role-of-scalable-video-coding-in-modern-communication
• https://bloggeek.me/webrtcglossary/svc/

Avatar-grade voice agents are on the $1499 plan — see /pricing. Or talk to one on /demo.