Skip to content

docs: remove webrtc not support H.265 tips #20769

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
+3 −2
Open

docs: remove webrtc not support H.265 tips #20769

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7e11839
docs: remove webrtc not support H.265 tips
ZhaiSoul Nov 3, 2025
0244909
docs: add browsers h.265 support tips
ZhaiSoul Nov 4, 2025
59353f8
Change H.265 compatibility link in live.md
ZhaiSoul Nov 5, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/docs/configuration/live.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ The jsmpeg live view will use more browser and client GPU resources. Using go2rt
| ------ | ------------------------------------- | ---------- | ---------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| jsmpeg | same as `detect -> fps`, capped at 10 | 720p | no | no | Resolution is configurable, but go2rtc is recommended if you want higher resolutions and better frame rates. jsmpeg is Frigate's default without go2rtc configured. |
| mse | native | native | yes (depends on audio codec) | yes | iPhone requires iOS 17.1+, Firefox is h.264 only. This is Frigate's default when go2rtc is configured. |
| webrtc | native | native | yes (depends on audio codec) | yes | Requires extra configuration, doesn't support h.265. Frigate attempts to use WebRTC when MSE fails or when using a camera's two-way talk feature. |
| webrtc | native | native | yes (depends on audio codec) | yes | Requires extra configuration. Frigate attempts to use WebRTC when MSE fails or when using a camera's two-way talk feature. |

### Camera Settings Recommendations

Expand Down Expand Up @@ -127,7 +127,8 @@ WebRTC works by creating a TCP or UDP connection on port `8555`. However, it req
```

- For access through Tailscale, the Frigate system's Tailscale IP must be added as a WebRTC candidate. Tailscale IPs all start with `100.`, and are reserved within the `100.64.0.0/10` CIDR block.
- Note that WebRTC does not support H.265.

- Note that some browsers may not support H.265 (HEVC). You can check your browser's current version for H.265 compatibility [here](https://caniuse.com/hevc).
Copy link
Collaborator

@NickM-27 NickM-27 Nov 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be good to call out that H.265 playback is not universal. A browser might support H.265 HLS playback but not WebRTC for example.

Copy link
Contributor Author

@ZhaiSoul ZhaiSoul Nov 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's unfortunate. Currently, I haven't found any official documentation clearly stating whether WebRTC H.265 is officially supported :(

Copy link
Collaborator

@NickM-27 NickM-27 Nov 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Safari requires a developer flag to be enabled. Chrome on MacOS and Windows has added support, not sure about linux or any other browsers

Copy link
Collaborator

@NickM-27 NickM-27 Nov 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is all already documented in go2rtc https://github.com/AlexxIT/go2rtc?tab=readme-ov-file#codecs-madness


:::tip

Expand Down