Hey fellow travelers—mobile data packages are weirdly hard to size up until you burn through them on day three.
Here’s how much you actually need for the common stuff (maps, messaging, video calls home, uploading photos), with real GB ranges so you can pick a plan without wasting money.
Why “unlimited” feels different once you’re abroad

The hidden catch: data isn’t infinite (and speed can drop)
Most “unlimited” plans either:
- slow you down after a threshold
- cap hotspot/tethering
- limit roaming add-ons
- or just make the data so expensive you avoid using it
So you end up doing the math anyway—just later, while you’re stressed.
Why people overbuy (and how to fix that fast)
I’ve done it. You land somewhere new, you want to livestream your first sunset, and suddenly you’re watching the data counter like it’s a stock chart.
The usual overbuying triggers are:
- assuming maps use a lot (they usually don’t)
- underestimating “background” usage (social apps, iCloud/Google Photos sync)
- forgetting you’ll upload way more than you think
- buying a big bundle “just in case” and then barely touching it
The smartest way to choose: estimate your worst day
Instead of averaging your whole trip, think:
- What’s the day you’ll be most online?
- For most travelers, it’s usually: arrival day + a photo-heavy outing + a video call home.
Once you know that worst day, the rest of the trip becomes pretty easy.
Real-world data costs for the stuff you’ll actually do

Quick GB ranges (not perfect, but they’re useful)
Below are typical ranges people see while roaming. Your mileage will vary with signal strength, app settings (HD video? autoplay?), and whether you’re on Wi‑Fi sometimes.
Still, these numbers are good enough to stop guessing.
Data use by activity (use this to build your total)
Think of each bullet as something you’ll “spend” data on. Add the ones that match your trip.
- Google Maps navigation (about an hour total): ~100–300 MB
- Checking maps in bursts (a few searches without long navigation): ~20–80 MB
- Messaging (WhatsApp/iMessage/Telegram, normal use): ~20–200 MB per day (mostly depends on sending/receiving photos)
- Light web browsing (news, emails, airline/app check-ins): ~50–200 MB per day
- Scrolling social media (not downloading/reposting a lot): ~150–500 MB per day
- Posting photos (one post with image upload): ~1–10 MB per photo (the upload isn’t huge—the background sync is)
- Uploading lots of photos (burst of 30–100 pics): ~0.3–2 GB total depending on resolution and compression
- Auto-syncing your camera roll to the cloud (overnight or while you’re out): ~0.5–3 GB per day if you take lots of photos
- Short voice call (10–20 minutes): ~10–40 MB
- Video call home (10–15 minutes): ~60–300 MB (HD vs lower quality can swing this a lot)
- Streaming music (Spotify/Apple Music) for an hour: ~50–200 MB
- Streaming video (YouTube/Netflix on the move) for an hour: ~0.7–3 GB
Where your plan usually gets wrecked
The biggest “surprise bills” for most people aren’t maps.
They’re usually:
- social apps autoplaying and downloading
- cloud photo backup syncing while you’re out and about
- video calls in higher quality
- streaming video when you’re tired and want background entertainment
Simple GB-per-day budgets (so you can buy less)

The three traveler profiles
Use these as starting points. Then adjust for photos/video calls.
- Light user (mostly messaging + maps + occasional web): 0.5–2 GB/day
- Average user (social scrolling + some photo upload): 2–4 GB/day
- Heavy user (lots of social + regular cloud sync + video calls): 4–8+ GB/day
Make your budget smarter with “Wi‑Fi boundaries”
If you can, draw lines like:
- Only upload photos when you’re on Wi‑Fi
- Use offline maps for walking/transit
- Do video calls on Wi‑Fi when possible
This is the same strategy I used in Tokyo when my first day data consumption jumped because my phone decided it was a great time to sync everything.
Offline settings that actually change the number
Do these before you leave (or as soon as you land):
- Download offline maps for the areas you’ll realistically use.
- Turn off background app refresh for the apps you don’t need roaming.
- Stop auto photo backup from roaming (you can switch it to “Wi‑Fi only”).
- If your carrier supports it, disable roaming data for specific apps.
Build a trip total with realistic scenarios
City break (5 days) — usually the easiest to underestimate
If you’re mostly doing attractions, checking directions, and messaging friends:
- Light-ish navigation: ~0.1–0.3 GB/day
- Messaging + browsing: ~0.5–1.5 GB/day
- Social scrolling: ~0.3–1 GB/day
- Photos: ~0.2–1 GB total (or more if cloud sync is on)
A practical budget: 4–10 GB total for the whole trip.
If you’re planning a video call home once or twice:
- add 0.2–1 GB total
Beach / slow travel (7–10 days) — the photos can spike
If you’re taking lots of pics (and maybe uploading daily):
- Maps are usually low
- Messaging and social are steady
- The wildcard is cloud backup
A practical budget:
- 7 days: 6–18 GB
- 10 days: 9–25 GB
If you only post 1–2 times during the trip and disable roaming photo sync:
- you can often stay closer to the lower end.
Road trip / outdoor adventure (10–14 days) — navigation is your main job
Driving and hiking often means more map time, plus you might be tempted to stream music/video.
A practical budget:
- 10 days: 10–30 GB
- 14 days: 14–40 GB
If you keep video calls to one or two short calls and rely on Wi‑Fi at night (where available), you’ll be closer to ~10–20 GB.
Worst-case day math (my quick method)
Take your heaviest day and use this rough formula:
- Maps + checks: 0.1–1 GB
- Social scrolling: 0.5–2 GB
- Messaging + normal web: 0.3–1 GB
- Photos + any roaming sync: 0.3–5 GB
- One video call: 0.1–0.3 GB (if it’s short and not HD)
Worst day total: often 2–8 GB.
Then:
- If you have 3–4 similar days: multiply accordingly
- If the rest of the trip is lighter: use a smaller daily number and you’re back in control
How to avoid the “oops, I’m out of data” moment
Check usage early (and don’t trust your gut)
Do this in the first 24 hours:
- Look at your carrier’s usage counter
- Check in-app usage (some phones show it per app)
- Note whether cloud photo backup actually turned off
If you see an app eating data in the background, you can usually fix it before you waste the rest of your bundle.
Turn off the common silent data leaks
These settings make a bigger difference than most people expect:
- Disable auto-play in social apps
- Turn off high quality video auto-download
- Keep photo sync on Wi‑Fi only
- Avoid streaming unless you’ve got Wi‑Fi
Use a travel plan that matches your risk level
Sometimes you don’t need a huge amount—you just need enough runway until you’re on Wi‑Fi.
If you’re the kind of traveler who wants flexibility (and doesn’t want to overbuy), I’ve had decent experiences topping up or choosing data packages through Saily—it’s one of those tools that helps when your plans shift.
(Just remember: even with a good provider, Wi‑Fi habits still save you money.)
If you do run low: what to do that won’t break the trip
When you’re near the end of your allowance:
- switch messaging to Wi‑Fi only where possible
- limit social to quick checks
- save video calls for Wi‑Fi
- keep offline maps ready so navigation doesn’t surprise you
Final thoughts (and a quick rule you’ll actually remember)
The rule: maps aren’t the villain—uploading and video are
If you buy data assuming maps will consume everything, you’ll almost always overspend.
More often, your data bill comes from:
- photo cloud sync while you’re out
- social apps
- video calls and streaming
Your best next step: estimate worst-day, not average-day
Before you land, do this:
- Pick your worst online day
- Add GB for maps, social, photos, and one video call
- Multiply for the number of “similar” days
If you want a one-liner to carry with you: buy enough for your worst day, keep Wi‑Fi for photos/video, and you won’t feel like you’re rationing your life.
Safe travels—and may your data counter stay boring.