Browser compatibility
Latenz negotiates a video codec as the intersection of what your host encodes in hardware and what this browser can decode over WebRTC (RTCRtpReceiver.getCapabilities). If a codec is missing, the session still works — it falls back to H.264 — but you may miss better quality or lower bandwidth from H.265 or AV1.
The dashboard Browser codec compatibility card reflects your current browser. Pick the guide for your operating system below.
Quick reference
| Codec | Required? | Chrome / Edge | Firefox | Safari |
|---|---|---|---|---|
| H.264 | Yes | Supported | Supported | Supported |
| H.265 / HEVC | No | Windows / macOS only (not Linux) | Not over WebRTC | Supported (recent Apple OS) |
| AV1 | No | v90+; hw decode preferred | Recent versions | Limited hw (M3+, iPhone 15 Pro) |
Guides by platform
- Linux — H.264 + AV1; no H.265 over WebRTC
- Windows — HEVC extensions, GPU decode
- macOS — Chrome, Edge, Safari
- iOS — Safari on iPhone/iPad
- Firefox — all platforms
H.264 missing (critical)
If H.264 is not supported, you cannot start a session. This is rare on current desktop browsers.
- Update Chrome, Edge, Firefox, or Safari.
- Rule out locked-down WebViews or corporate WebRTC blocks.
- Try another browser on the same machine to isolate the issue.
Verify changes
- Reload the dashboard codec card after any fix.
- In Chromium, check
chrome://gpu(oredge://gpu). - Fully quit and reopen the browser — don't rely on tab refresh alone.
See also Video codecs for host-side negotiation.