Release 2026.07.24
Activity planning table
Values are per active session. They are intentionally rounded for planning. Service modes, quality settings, codecs, devices, and routes can change actual use.
| Activity | Download | Upload | Ping target | Jitter target | Evidence basis |
|---|---|---|---|---|---|
Web browsing and email Per active user; large attachments need more upload capacity. | 5 Mbps | 1 Mbps | ≤ 150 ms | ≤ 40 ms | Editorial planning baseline for an active browser and email session. Editorial composite; no single vendor minimum. |
HD video stream Per simultaneous 1080p stream across common adaptive services. | 8 Mbps | 1 Mbps | ≤ 100 ms | ≤ 30 ms | Editorial planning baseline informed by official service recommendations. |
4K video stream Per simultaneous 4K stream; some services adapt below this. | 25 Mbps | 1 Mbps | ≤ 100 ms | ≤ 30 ms | Conservative editorial planning baseline informed by official service recommendations. |
HD video call Per active camera; stability matters more than excess download speed. | 4 Mbps | 4 Mbps | ≤ 100 ms | ≤ 30 ms | Rounded planning baseline informed by official 1080p video-call requirements. |
Remote work session (excluding video calls) Covers cloud apps, messaging, and normal file transfers; add video calls separately. | 10 Mbps | 3 Mbps | ≤ 100 ms | ≤ 30 ms | Editorial composite for concurrent work applications, not a vendor minimum. Editorial composite; no single vendor minimum. |
Online gaming Game downloads need far more throughput; live play prioritizes latency. | 10 Mbps | 3 Mbps | ≤ 50 ms | ≤ 15 ms | Editorial gameplay baseline; title, platform, and route conditions vary. Editorial composite; no single vendor minimum. |
1080p livestream upload Per active 1080p broadcast, including encoder and audio traffic. | 10 Mbps | 10 Mbps | ≤ 80 ms | ≤ 20 ms | Conservative editorial baseline informed by official broadcast bitrate guidance. |
Cloud backup or large upload Higher upload speed shortens completion time; latency is less critical. | 10 Mbps | 25 Mbps | ≤ 150 ms | ≤ 40 ms | Editorial target chosen for practical completion time rather than a service minimum. Editorial composite; no single vendor minimum. |
Calculation method
Combine only activities that can overlap
- 1. Count active sessions. Two simultaneous HD calls count twice; ten idle devices do not automatically count as ten active sessions.
- 2. Add download and upload separately. The constrained direction may be upload even when the plan advertises a large download number.
- 3. Apply planning headroom. The linked calculator adds 25% to the capacity totals. That is an editorial allowance, not a vendor requirement or guarantee.
- 4. Use the strictest responsiveness target. If a workload includes a real-time activity, its latency and jitter planning targets remain relevant even when file transfers need more Mbps.
- 5. Validate the real application.Compare with the service's current requirements and in-app diagnostics, then repeat the browser test under the actual household load.
Evidence register
Visible sources and reusable data
Retrieved 2026-07-24
2024 Section 706 Report broadband benchmark
Household-level context: the FCC raised its fixed broadband benchmark to 100 Mbps download and 20 Mbps upload.
Federal Communications Commission sourceRetrieved 2026-07-24
Netflix-recommended internet speeds
Service baseline: 5 Mbps for 1080p and 15 Mbps for 4K UHD on Netflix.
Netflix sourceRetrieved 2026-07-24
Zoom Web App system and bandwidth requirements
Service baseline: Zoom lists 3.8 Mbps upload and 3.0 Mbps download for 1080p HD video.
Zoom sourceRetrieved 2026-07-24
Broadcasting Guidelines
Service baseline: Twitch lists a 6,000 Kbps video bitrate for 1080p60 and emphasizes connection stability.
Twitch sourceWhat this table does not prove
- A plan meeting the total does not guarantee Wi-Fi coverage, provider routing, application-server health, or low loaded latency.
- Ping and jitter targets are editorial diagnostics for planning; they are not universal pass/fail rules for every game or call.
- A browser test measures one device-to-endpoint path. Repeat under controlled conditions and confirm with the application itself.
- Requirements can change. The release date and source retrieval dates make the assumptions auditable instead of timeless.
Read the SwiftSpeedTest methodology for measurement scope, confidence, and privacy.