Why can't you force a video resolution in WebRTC calls

6 Dec 2024 · 1 min

Watch on YouTube

0:57

A short conversational explanation (Q&A) about why you cannot always force a specific video resolution in WebRTC calls. Speakers explain that when network bandwidth is insufficient the system must compromise (e.g., lower resolution or reduce frame rate) to keep video real-time; the conversation explicitly gives the example that 1080p is unrealistic on a 100 kbps link and notes you can instead force lower frame rate with trade-offs.

Questions this video answers

100 kbps

Reduce the frame rate

Why can't we force a video resolution in WebRTC codes?
So that's a question that is surprisingly common. People often complain, oh, WebRTC lowers my resolution. And why does it do that? Because at some point the network doesn't have enough bandwidth to encode the resolution you want, and webc needs to compromise to ensure we still get the stuff across in real time. So you can actually change and control a bit how it behaves there. But in the end, it's going to have to compromise.
So don't expect to do 1080p resolution when you only have 100kbps on the network.
Exactly. You can force WEAPONC to reduce the frame rate instead, but of course that will cause other complaints.
Yeah, okay.
So it's a compromise.
Thank you.
Thank you.