1. Network connectivity requirements

The network requirements and other information in this article applies to both Hangouts Meet and classic Hangouts.

High-quality video meetings with Hangouts Meet require a properly configured network. Verify that your network is ready for Meet traffic:

  1. Understand how the Meet architecture allows media traffic to flow through the Google infrastructure to multiple participants.
  2. Make sure that network latency is low and consistent so that Meet traffic takes the shortest path between the client and Google.
  3. Make sure your network has enough bandwidth to handle all concurrent video meetings in a location.
  4. Open the outbound ports to allow media traffic to flow to and from your network.
  5. Whitelist the URIs used by Meet for web traffic, APIs, feedback reports, logs upload, and connectivity setup.

Meet architecture

Meet makes joining meetings effortless, so people can be as productive as when they’re face-to-face. The Meet infrastructure makes this possible by transmitting media traffic for multiple participants through the Google infrastructure. 
The Google infrastructure also enables advanced features such as telephony and recording and seamlessly connects participants from different sites and telephones. 
Meet can be accessed from various sites and means
To ensure a high-quality, reliable video meeting experience, your network must provide sufficient bandwidth and low latency between the Meet client and Google back end.
Latency requirements
Meet video performs best when the network latency is low and consistent. This is best achieved when Meet traffic takes the shortest path between the client and Google.
For example, Meet performance is optimal when the round-trip latency (RTT) between the client and Google back end is lower than 100 ms.

See Measure and optimize network latency to minimize latency, including:

  • The latency between the Meet client and Google back end
  • Jitter for Meet traffic
Bandwidth requirements per participant
The bandwidth used by Meet varies to provide the best experience on participants’ networks.
Ideal bandwidth
  • 2-person HD video meetings:
    • Outbound from the participant: 3.2 Mbps
    • Inbound to the participant: 2.6 Mbps
  • Group video meetings:
    • Outbound from the participant in all situations: 3.2 Mbps
    • Inbound to the participant with 5 or more participants: 3.2 Mbps

See Measure and optimize network bandwidth for more information.

Bandwidth requirements per live stream viewer
If your organization live streams video meetings, the ideal bandwidth for each viewing participant is 2.6Mbps. This is the default 720p high quality Meet video setting, and is used if the participant has enough individual bandwidth.
If sufficient bandwidth is not available, viewers can also optionally choose to reduce the Meet video quality.
Meet video quality setting Bandwidth required Notes
720p 2.6 Mbps This is the default high quality setting that results in the best user experience.
480p 1.5 Mbps  
360p 1.0 Mbps  
240p 0.5 Mbps This results in a poor viewer experience and is not recommended.


Note: For participants and presenters in the Meet meeting, see Bandwidth requirements per participant.

Bandwidth requirements per site

A site’s network should have enough bandwidth for all concurrent HD video meetings, plus additional bandwidth for other needs. If a site does not have enough bandwidth, Meet will gracefully lower the video definition to fit the network constraints. If the bandwidth is insufficient to transfer video, an audio only mode is used.

To calculate the optimal bandwidth requirement range, multiply the amount of bandwidth required for each audio only and HD video meeting participant with the peak number of concurrent participants or rooms. 

Avg. bandwidth per participant * peak no. of concurrent participants = Minimum Meet site bandwidth requirements

Average bandwidth per participant

  Outbound / Inbound
HD Video 3.2 / 1.8 Mbps
Audio only 12 / 18 Kbps


Peak number of concurrent participants

Determine the number of concurrent participants based on how important video calling is at each site, as shown in the following table.

Importance of videoconferencing Peak number of concurrent video meetings
High 10–20%
Normal 1–4%
Low 0.01–0.5%

For example, if video conferencing is of high importance, estimate that 20% of the users at that site will use Meet. If video conferencing is of low importance, only 0.5% of people at that site might be in a video meeting at the same time.

These estimate usually apply to specific user types, such as sales engineers or support teams who use a lot of videoconferencing to communicate with customers.

See Measure and optimize network bandwidth for more information.

Outbound ports required for media traffic

Set up your network so the following ports allow media traffic to flow to and from your organization:

  • Outbound UDP ports 19302 to 19309
  • Outbound UDP and TCP port 443

Meet port range 19302 to 19309 uses the Chrome WebRTC UDP Ports Setting.

Whitelist URIs

Ensure full network access to core Google services. If restrictions or filtering policies exist for users on your network, ensure that network access to the following URI patterns are in place.

These patterns are used by Meet for web traffic, APIs, feedback reports, logs upload, and connectivity setup. 

  • https://*.google.com/*
  • https://*.googleapis.com/*
  • https://*.gstatic.com/* 
  • https://*.googleusercontent.com/*

In addition, the following URIs are also required if your organization live streams video meetings.

  • https://*.googlevideo.com/*
  • https://*.youttube-nocookie.com/*
  • https://*.ytimg.com/*

Next step

Optimize your network for Meet.

Was this helpful?
How can we improve it?