Methodology

How we estimate data usage

Our per-app rates, the sources behind them, and how we turn them into a recommended plan range.

The short version

For each app, we use a published data rate (where the company has one) or a community-measured average (where they don't). We multiply the rate by your estimated hours per day, sum across apps, multiply by trip length, and apply a Β±20% range to account for the fact that real usage varies.

The recommended plan size targets the upper end of that range. We'd rather you buy a slightly larger plan than run out mid-trip β€” eSIM top-ups exist but are usually more expensive per GB than the original plan.

Why a range, not a single number

Two people with identical app habits can use very different amounts of data over a week. Network conditions affect streaming quality, autoplay behaviour varies, and one Reels rabbit-hole can add a GB. A Β±20% band reflects this.

If your trip is short or you're cost-sensitive, plan for the lower end. If you're working remotely or you hate running out, plan for the upper end.

Per-app data rates

All values are megabytes per hour of active use. "Active" means foreground β€” apps in the background generally use far less.

AppVariantMB / hourSource
YouTubeSD 480p500Google: video resolution data use
YouTubeHD 1080p1,500Google: video resolution data use
YouTube4K 2160p7,000Google: video resolution data use
NetflixSD1,000Netflix Help Center: data usage per stream
NetflixHD3,000Netflix Help Center: data usage per stream
NetflixUltra HD7,000Netflix Help Center: data usage per stream
TikTokDefault feed700Independent measurements (community-reported, ~600–840 MB/h)
InstagramFeed/Stories200Independent measurements
InstagramReels600Independent measurements (similar to TikTok)
Google MapsNavigation10Empirical: Maps caches map tiles aggressively. Reported usage is consistently 3–10 MB/hour.
WhatsAppText + media1Independent measurements; depends on attachments
WhatsAppVoice call30WhatsApp FAQ + community measurements (~0.5 MB/min)
WhatsAppVideo call300Community measurements (~5 MB/min)
SpotifyNormal 160 kbps72Spotify quality settings Β· 160 kbps Γ— 3600 s Γ· 8 = 72 MB
SpotifyHigh 320 kbps144Spotify quality settings Β· 320 kbps Γ— 3600 s Γ· 8 = 144 MB
Zoom1:1 SD600Zoom Support: bandwidth requirements
Zoom1:1 HD1,200Zoom Support: bandwidth requirements
ZoomGroup HD2,000Zoom Support: bandwidth requirements
FaceTimeVideo call300Apple support guidance + independent measurements
Web browsingArticles, search, shopping60Average page weight ~2 MB; ~30 pages/hour
Photo backupiCloud / Google Photos1,000Highly variable; assumes ~30 photos/min averaging ~500 KB after compression
EmailGmail / Outlook10Average message ~75 KB with occasional attachments

Last reviewed: April 2026. Rates evolve as apps change codecs and resolutions β€” we revisit this table at least quarterly.

Caveats

  • Background data (app updates, OS sync, push notifications) can add 100–500 MB/day on its own. The calculator doesn't model this directly β€” the Β±20% range absorbs it for typical phones.
  • Hotspot / tethering use can be 5–10Γ— heavier than phone-only use. If you're tethering a laptop, double your estimate.
  • Network quality matters: on weak signal, video apps often re-buffer and re-download segments, inflating the real number.
  • App settings override defaults. If you've manually set YouTube to 4K, the SD/HD figures don't apply.

Embed this calculator

Travel bloggers, expat sites, and digital-nomad publications: the calculator is free to embed on your site. It's a single iframe, no JavaScript to install, no tracking beyond standard CocoRoam analytics.

<iframe
  src="https://cocoroam.com/embed/data-calculator"
  width="100%"
  height="900"
  style="border:0;border-radius:24px;max-width:960px;"
  loading="lazy"
  title="Travel Data Calculator by CocoRoam"
></iframe>

Credit isn't required but appreciated. A link back to cocoroam.com/tools/data-calculator helps us keep the tool free.

Back to the calculator