Skip to main content
SwiftSpeedTest
Speed TestQualityStabilityBufferbloatPlan auditCalculatorProvider testsDataSlow InternetGuides
Speed TestQualityStabilityBufferbloatPlan auditCalculatorProvider testsDataSlow InternetGuides
Call quality guide

Speed test results for Zoom, Teams and Google Meet

Start with the exact vendor scenario, add a versioned planning baseline for simultaneous household use, then verify the real call. A single Mbps, ping, or jitter cutoff cannot guarantee meeting quality.

Source-checked July 24, 2026No app requiredBrowser-based speed test
Vendor guidance is app and mode specific
Planning dataset 2026.07.24 uses one documented HD-call row
The real meeting remains the acceptance test

Quick next step

Test your connection first

Run SwiftSpeedTest, save the download, upload, ping, and jitter numbers, then use this guide to see what they mean and what to fix next.

Start speed test

Works on desktop and mobile. No account required.

On this page

Number typesVendor guidancePlanning targetDiagnose a failed call
Published by Swift Speed Test. See our testing method, sourcing standards, limitations, and corrections policy.

Evidence labels

Vendor requirement, planning target, and measurement are different

Vendor guidance
The app publisher's minimum, recommended, or maximum usage for a named resolution and meeting mode.
Editorial planning target
A rounded workload baseline used to combine simultaneous activity. It is not a vendor promise.
Measured diagnostic
One browser-to-test-endpoint path. It helps isolate a problem but does not measure the meeting vendor path directly.

Current first-party guidance

Match the app, direction, and meeting mode

Checked July 24, 2026. These are examples from the vendors' current pages, not interchangeable household speed tiers.

Vendor scenarioVendor-published bandwidthImportant scope
Zoom Web App, 1080p video3.8 Mbps up / 3.0 Mbps downZoom says usage adapts to participant network conditions. Zoom source
Teams group video, recommended2.5 Mbps up / 4.0 Mbps down per endpointMicrosoft separates minimum, recommended, and best performance and says actual use varies. Teams source
Meet, 1080p individual guidanceUp to 3.6 Mbps outbound and inboundGoogle publishes different rows for group meetings and organizational planning. Meet source

Versioned editorial planning target

One active HD call in dataset 2026.07.24

Download

4 Mbps

Upload

4 Mbps

Planning ping ceiling

100 ms

Planning jitter ceiling

30 ms

This row is a rounded editorial baseline informed by Zoom's 1080p guidance. It is per active camera and is not a guarantee at the boundary. Add every simultaneous call and other activity using the calculator. The dataset was updated 2026-07-24. Download the versioned data.

Acceptance test

Diagnose the exact meeting that fails

  1. 1. Test from the actual room, device, network, and meeting hour. Keep a quiet baseline.
  2. 2. Repeat while the household has its normal call-time load. Note loaded latency, jitter, unsuccessful probes, and confidence.
  3. 3. Run the vendor's real test call or meeting with the same camera, layout, screen share, VPN, and participants when possible.
  4. 4. Compare Wi-Fi and Ethernet on the same device. Change one variable at a time.
  5. 5. Use the app's own call-health or administrator telemetry when available; it observes a different path than this browser test.

Do not apply blanket QoS, VPN bypass, or band-forcing advice to an employer-managed network. Zoom, Teams, and Meet publish different network guidance; follow the organization's administrator and vendor documentation.

Primary sources and versioned data

Source-checked July 24, 2026. Recheck the vendor page for the exact app, client, resolution, layout, and meeting mode.

  • https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0058323
  • https://learn.microsoft.com/en-us/microsoftteams/prepare-network
  • https://knowledge.workspace.google.com/admin/meet/prepare-your-network-for-meet-meetings-and-live-streams?hl=en
  • https://swiftspeedtest.com/data/internet-speed-requirements/2026.07.24.json

Frequently asked questions

Quick answers about this topic

What speed-test result should I use for an HD video call?
SwiftSpeedTest dataset 2026.07.24 uses an editorial planning baseline of 4 Mbps download, 4 Mbps upload, ping no higher than 100 ms, and jitter no higher than 30 ms per active HD call. It is a planning target, not a universal vendor minimum or guarantee.
Do Zoom, Teams, and Google Meet use the same bandwidth?
No. Each vendor adapts media and publishes scenario-specific guidance. Resolution, layout, participant count, screen sharing, device, and network conditions change usage, so consult the current first-party row for the exact app and mode.
Why does a call freeze when the Mbps result looks sufficient?
A browser throughput result does not prove packet delivery to the meeting service. Wi-Fi variation, loaded latency, jitter, unsuccessful probes, congestion, VPN routing, device load, and the vendor service can still affect a call.

Related guides

Keep going with the next best page

Work-from-home speed test

Combine calls with cloud apps and other simultaneous household activity.

Ping versus jitter

Use latency variation as a diagnostic rather than a universal grade.

Requirements calculator

Add simultaneous calls and other workloads with documented headroom.

Test from the room and network used for meetings

Capture idle and loaded latency, jitter, unsuccessful probes, download, upload, and confidence, then validate with the exact call scenario.

Check the meeting connectionBrowse more guides

© 2026 SwiftSpeedTest. All rights reserved.

Open dataShare resultsWebsite widgetSupport reportProvider testsSpeed historyPlan auditCompare resultsQuality testStability testBufferbloat testGaming testStreaming testWork-from-homeSlow internetWi-Fi vs EthernetGood speed resultsSpeed calculatorHow it worksGuidesRSS feedPrivacyTerms