en-US chrome computer user

WebRTC IP handling

Verified with Google Chrome — updated on July 10, 2026 Supported on: Microsoft Windows 7 or later

Google Chrome

Path in the GPO console

Computer Configuration\Administrative Templates\Google\Google Chrome\WebRtc settings

Registry

HKLM Software\Policies\Google\Chrome
HKCU Software\Policies\Google\Chrome

Other deployment channels

Intune (ADMX ingestion)
./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~WebRtc/WebRtcIPHandling

OMA-URI published by Google. It requires the Chrome ADMX templates (chrome.admx, google.admx) to be imported in Intune first.

macOS / Linux preference WebRtcIPHandling
Supported platforms
  • Google Chrome (Linux) — since version 91
  • Google Chrome (Mac) — since version 91
  • Google Chrome (Windows) — since version 91
  • Google ChromeOS (Google ChromeOS) — since version 91

Source: official Chrome policy list, version 157.0.8103.79 Chrome Enterprise policy page

Options

WebRTC IP handling
WebRtcIPHandling enum
  • default WebRTC will use all available interfaces when searching for the best path.
  • default_public_and_private_interfaces WebRTC will only use the interface connecting to the public Internet, but may connect using private IP addresses.
  • default_public_interface_only WebRTC will only use the interface connecting to the public Internet, and will not connect using private IP addresses.
  • disable_non_proxied_udp WebRTC will use TCP on the public-facing interface, and will only use UDP if supported by a configured proxy.

Description

This policy allows restricting which IP addresses and interfaces WebRTC uses when attempting to find the best available connection. Valid values: * default - WebRTC uses all available network interfaces. * default_public_and_private_interfaces - WebRTC uses all public and private interfaces. * default_public_interface_only - WebRTC uses all public interfaces, but not private ones. * disable_non_proxied_udp - WebRTC uses either UDP SOCKS proxying or will fallback to TCP proxying. When unset, defaults to using all available network interfaces. See RFC 8828 section 5.2 (https://tools.ietf.org/html/rfc8828.html#section-5.2) for a detailed description of all the handling values. Example value: default

Export Builder

BETA

Configure the state, scope and options, then generate .reg, PowerShell, Intune and SCCM outputs — or add the setting to a multi-setting collection.

These exports write the registry — this is not a managed GPO. ⓘ

Scope

.reg file

Windows Registry Editor Version 5.00

; Exported from gporais.com
; Policy: WebRTC IP handling
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Windows 7 or later

[HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome]
"WebRtcIPHandling"="default"
More formats (PowerShell, Intune, SCCM)

PowerShell

# Exported from gporais.com
# Policy: WebRTC IP handling
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Windows 7 or later

$path = 'HKLM:\Software\Policies\Google\Chrome'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'WebRtcIPHandling' -Value 'default' -Type String

Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.

Open the Builder

Embed this policy on your site

What to embed
Theme

Adds one script line: the theme follows your site’s appearance and the height fits the content. If your site blocks scripts, the embed follows the visitor’s system theme.

Preview