Why Your Webcam Uploads Are Huge on Fedora
A 42-minute recording was 3GB on Windows and 7GB on Fedora from the same webcam. The cause: Chrome falling back to software H.264 encoding because Fedora's stock Mesa strips patented H.264 support. Here's the five-minute diagnostic and fix.
Same Logitech Brio, same 1080p, same frame rate, dual-booted machine: a Riverside podcast session came out more than twice the size on Fedora as on Windows. I trace it here from "is this the network or the OS" all the way to the actual cause, which is a licensing decision baked into the distro, not a missing driver. This one is Fedora-specific; Ubuntu and other distros fall back for different reasons.
Key takeaways
- Skip chrome://webrtc-internals (needs a live call): check chrome://gpu for "Video Encode"; "software only" means the CPU is encoding, at much higher bitrates
- Fedora's stock Mesa strips H.264 encode (patent-encumbered): RPM Fusion's freeworld build re-enables it:
sudo dnf swap mesa-va-drivers mesa-va-drivers-freeworld --allowerasing(adnf update --refreshfirst usually clears the dependency fight) - Verify with
vainfo: you wantVAProfileH264Main : VAEntrypointEncSlice - The driver fix alone isn't enough: the old Chrome flag is gone as of 131; launch with
--enable-features=AcceleratedVideoDecodeLinuxZeroCopyGL,AcceleratedVideoDecodeLinuxGL,AcceleratedVideoEncoderand quit Chrome fully first - Not Riverside-specific: Zoom web, Meet, StreamYard, any Chrome WebRTC capture on Linux hits the same fallback
Who this is for
People who record calls or podcasts on Fedora (especially with AMD GPUs) and are burning bandwidth and disk for no reason. Assumes you're comfortable in a terminal with dnf. There's a copy-paste checklist at the end.
The full write-up, with the diagnostic path and the permanent launcher fix, is on Substack.