DEV Community: NXTL eSIM

How Much Mobile Data Do You Actually Use When Travelling?

NXTL eSIM — Sun, 25 Oct 2026 00:37:45 +0000

A realistic, activity-by-activity estimate — plus how to measure your own usage and cut it down

Disclosure: this article is written by the NXTL team. NXTL makes a travel eSIM, which we mention briefly below.

"How many gigabytes do I need for two weeks in Spain?" is one of the most common travel questions, and the honest answer is: it depends almost entirely on what you do with your phone. A traveller who navigates and messages might get by on a few hundred megabytes a week. One who uploads Stories and takes video calls every evening can burn through several gigabytes.

Below is a breakdown by activity. All figures are rough estimates. Real usage varies with app versions, video quality settings, network speed, and how much of your phone's background activity you allow. Treat these as planning ranges, not guarantees.

Rough data use by activity

Maps and navigation

Live navigation (Google Maps, Apple Maps): roughly 2–10 MB per hour of active driving or walking directions.
Browsing a map, searching places, loading photos and reviews: can be higher, around 10–30 MB per hour of heavy exploring, because place photos are the expensive part.
Offline maps: close to zero once downloaded (download them on Wi-Fi beforehand).

Navigation is far cheaper than most people fear. It is rarely what drains a travel data budget.

Messaging

Text-only chats (WhatsApp, Telegram, iMessage, Signal): a few KB per message — often under 1–5 MB a day even for chatty users.
Photos: roughly 0.1–0.5 MB each after app compression; more if you send "HD" or original quality.
Voice notes: roughly 0.5–1 MB per minute.
Videos sent in chats: anywhere from 2 MB to 50+ MB per clip.

Group chats full of forwarded videos are a hidden cost. Auto-download is usually the culprit (more on that below).

Social media

Scrolling Instagram, TikTok, or Facebook: roughly 300 MB–1 GB+ per hour. Short-form video feeds are the heaviest because videos autoplay and preload.
Posting a photo: a few MB.
Posting a Story or Reel: roughly 10–50 MB per upload, depending on length and quality.

If you only change one habit while abroad, make it this one: scroll on Wi-Fi, post on mobile data.

Music and podcasts

Music streaming: roughly 40–150 MB per hour depending on quality setting.
Podcasts: roughly 30–60 MB per hour-long episode.
Downloaded playlists and episodes: near zero while travelling.

Video streaming

Standard definition (480p): roughly 0.5–1 GB per hour.
HD (720p–1080p): roughly 1.5–3 GB per hour.
4K: 5–7 GB+ per hour — rarely worth it on a phone screen.

A single HD movie can cost more data than a week of navigation and messaging combined.

Video calls

Audio-only internet calls (WhatsApp, FaceTime Audio, etc.): roughly 0.5–1.5 MB per minute, or about 30–90 MB per hour.
Video calls (FaceTime, Zoom, Google Meet, WhatsApp video): roughly 300 MB–1.5 GB per hour, depending on resolution and the number of participants.

Group video calls on Zoom or Meet sit at the top of that range.

Hotspotting a laptop

This is where estimates break down, because a laptop behaves very differently from a phone:

Light work (email, docs, chat): roughly 100–300 MB per hour.
Cloud sync, OS updates, or app updates in the background: can quietly consume several GB in one session.
Video meetings from the laptop: similar to video calls above, often at the higher end.

Before tethering, pause cloud sync (Dropbox, iCloud, OneDrive, Google Drive) and mark the connection as metered so Windows or macOS doesn't start large downloads.

A few sample trip profiles (rough estimates)

Traveller type	Typical daily use	One week
Light: maps, messaging, occasional browsing	50–150 MB	0.4–1 GB
Moderate: plus social posting and some music	200–500 MB	1.5–3.5 GB
Heavy: plus video calls, scrolling, some streaming	1–3 GB	7–20 GB
Working remotely via hotspot	2–5 GB+	15–35 GB+

For more detail on how travellers actually use data, NXTL published a travel eSIM usage study with its methodology.

How to measure your own usage before you go

The best estimate is your own history. Check it a week or two before you travel.

On iPhone: go to Settings → Cellular (or Mobile Data). You'll see "Current Period" usage and a per-app list. Scroll to the bottom to find Reset Statistics — reset it at the start of a normal week, then check after seven days. Note that iPhone doesn't reset this counter automatically.

On Android: go to Settings → Network & internet → SIMs (or Mobile network) → App data usage. Menu names vary by manufacturer; on Samsung it's Settings → Connections → Data usage → Mobile data usage. You can set the date range to match a week and see which apps use the most.

Then adjust: if most of your home usage is streaming you won't do abroad, subtract it; if you'll rely on mobile data instead of home Wi-Fi, add more.

How to cut usage without missing out

Download offline maps for each city before leaving.
Turn off auto-download for photos and videos in WhatsApp, Telegram, and other messengers.
Lower streaming quality in Netflix, YouTube, and Spotify settings, or download content on hotel Wi-Fi.
Disable background app refresh for apps you don't need (iPhone: Settings → General → Background App Refresh; Android: per-app "Background data" toggle or Data Saver).
Turn off autoplay in social apps; Instagram and Facebook both have data-saver options.
Stop automatic app and OS updates over mobile data.
Pause photo backup (iCloud Photos, Google Photos) until you're on Wi-Fi.
Watch for "Wi-Fi Assist" / adaptive Wi-Fi, which can switch to mobile data when hotel Wi-Fi is weak.

Choosing a plan that matches your estimate

Once you have a realistic number, the plan type matters. Fixed bundles suit travellers who know their usage well. If your estimate is uncertain — say, somewhere between 1 and 5 GB — a pay-as-you-go option lets you pay only for what you use.

NXTL's Global eSIM is one such option: a data-only, prepaid-balance eSIM where usage is charged proportionally in 1 KB increments at the published rate for the network you're on. On the web, the starter is US$11.99, which includes US$10 of usable balance plus US$1.99 for the eSIM (in-app prices may differ). Per-GB rates vary widely by country and network, so check the current rates on the pricing page for your destination before you estimate costs.

Whatever you choose, measure first, cut the obvious waste, and budget a little headroom. The traveller who runs out of data is usually not the one who navigated too much — it's the one whose phone backed up 400 photos over mobile data on day one.

Staying online as a remote developer across countries: a practical connectivity checklist

NXTL eSIM — Sat, 24 Oct 2026 23:48:22 +0000

Written by the NXTL team. We make a travel eSIM, which we mention in a few places below as one option among several. The rest of the checklist applies whatever connection you use.

Working from a new country is great until your laptop is on hotel Wi-Fi that drops every twenty minutes, and you're 4 GB into a Docker pull on a mobile plan you didn't size. Here's the checklist we use: what to sort out before you fly, and how to keep your data use predictable once you land.

1. Treat your phone as your primary uplink, not a backup

Hotel, café and coworking Wi-Fi varies a lot. A mobile hotspot from your own phone is often the most consistent connection you have, and you control it.

Test tethering before you travel. Turn on Personal Hotspot (iOS) or Wi-Fi hotspot (Android), connect your laptop and run a real task: git fetch, a short video call. Some plans and profiles limit tethering, so find out at home.
Use USB tethering when you can. It's usually steadier than Wi-Fi tethering and charges the phone at the same time. Bluetooth tethering works, but it's slow.
Watch battery and heat. Running a hotspot for long stretches drains the battery fast. Carry a power bank and a short cable.
Mark the hotspot as metered on your laptop. Windows and macOS will both cut back on background downloads over a connection they know is limited (more on this below).

2. Check eSIM compatibility properly

An eSIM lets you add a local or travel data plan without hunting for a SIM shop at arrival. Before you rely on one, check that:

Your phone supports eSIM. Many recent phones do, but regional models vary.
Your phone is carrier-unlocked. A locked phone may reject third-party eSIM profiles.
You install the eSIM before you leave, on reliable Wi-Fi. Installation needs a connection, and you won't want to be doing it at an airport gate.
You know how to switch data lines. Keep your home SIM active for calls and texts if you need them, and set mobile data to the travel eSIM. Turn off data roaming on the home line to avoid surprise charges.

Most eSIM providers publish a device list. NXTL's is at the eSIM compatible devices page, and it's a quick way to check your model even if you end up choosing someone else.

3. Budget data for developer workloads

This is where remote developers get caught out. Ordinary browsing is cheap. Development work isn't. The figures below are rough and vary with project size, codec and settings, so use them for planning and then measure your own usage (section 4).

Task	Typical data use (rough)	How to cut it
Video call, 1 hour (HD)	~1–3 GB	Drop to audio-only or 360p, turn off your camera when you don't need it
Video call, 1 hour (audio only)	tens of MB	Default for standups
`git clone` of a large repo with full history	hundreds of MB to several GB	`git clone --depth 1`, `--filter=blob:none`, sparse checkout
`npm install` / `pip install` on a fresh project	tens to hundreds of MB	Reuse caches, use lockfiles, avoid deleting `node_modules`
Container image pulls	hundreds of MB to several GB each	Pull on Wi-Fi beforehand, use slim base images, prune less often
OS / IDE / toolchain updates	hundreds of MB to several GB	Pause automatic updates while you're on a hotspot
Cloud photo / file sync	unpredictable	Pause sync while tethered
Screen sharing (static code)	modest	Lower the frame rate in call settings

Practical rules:

Prefetch on good Wi-Fi. Pull images, clone repos and run installs the night before you switch to mobile data.
Shallow and partial clones are the biggest single saving for git: git clone --filter=blob:none <url> fetches file contents only when you need them.
Keep package caches warm. npm, pip, Cargo and Go all cache locally. Don't wipe them before a trip.
Push CI to the cloud. Let remote runners do heavy builds and pull only the artifacts you actually need.
Use a remote dev box for heavy work. SSH or a remote editor session to a cloud machine moves only keystrokes and screen updates, while the big downloads happen in the data centre.

4. Measure your usage, don't guess

On the phone: reset the cellular data counter when you arrive (iOS: Settings → Mobile Data; Android: Network & internet → Data usage). Check it daily for the first few days.
On the laptop: tools like nettop (macOS), nethogs or vnstat (Linux), or Windows' Data Usage settings show which apps are using bandwidth. Background sync clients and update services are the usual culprits.
Set metered connections: Windows (Wi-Fi properties → Metered connection) and macOS Sonoma or later (Low Data Mode for that network) both cut back on background traffic.
Know how your plan bills. Fixed bundles can run out or expire mid-trip, while pay-as-you-go plans only charge for what you use. Either works if you understand it.

5. VPN notes

Use a VPN on shared Wi-Fi if your company requires it or you're handling anything sensitive. Expect a little overhead in data and latency.
Know where your traffic exits. Some travel eSIMs route traffic through a fixed region, so websites may see an IP from a different country than the one you're in. That affects geo-based content, login checks and occasionally CAPTCHAs. With NXTL, for example, consumer traffic exits via London, which is explained on the global routing page.
Tell your security team before you travel. Logins from unexpected countries can trigger account locks. Allow-list or pre-announce your travel.
Split tunnelling can keep big public downloads (package registries, for example) off the corporate VPN, if your policy allows it.

6. Have backup connectivity

Plan for at least two independent ways online:

Primary: a phone hotspot on a local SIM or travel eSIM.
Secondary: coworking or accommodation Wi-Fi you've actually tested, not just read about in a review.
Tertiary: a second data line, on a different network if possible, so one outage doesn't take everything down.

One way to set up a reusable data line is a pay-as-you-go travel eSIM. NXTL Global eSIM is a data-only eSIM covering 180+ countries and 460+ networks. Usage comes out of a prepaid balance and is billed in 1 KB increments, so you aren't buying a bundle per country. On the web it starts at US$11.99, which is US$10 of usable balance plus US$1.99 for the eSIM (in-app prices may differ). Unused standard balance doesn't expire while your account stays active, subject to the terms. Coverage and speed depend on the local network, as with any provider, so compare it against local SIMs and other options for your route.

Also pack: offline docs (DevDocs offline, man pages, downloaded dependency docs), a written list of your critical passwords and 2FA backup codes stored securely offline, and a plan for what you'll do if you're offline for a day.

The short version

Test hotspot and tethering at home.
Confirm eSIM support and carrier unlock, and install before departure.
Prefetch repos, images and packages on Wi-Fi.
Mark mobile connections as metered and pause sync and updates.
Measure daily usage for the first few days.
Know where your VPN and eSIM traffic exits.
Keep two independent backups.

With a bit of setup beforehand, being in a new country stops being a connectivity problem and you can just get on with work.