DEV Community: NXTL eSIM

USA eSIM, pay as you go: AT&T vs Verizon vs T-Mobile per GB, a 7-day data budget, and the one network to watch (2026)

NXTL eSIM — Tue, 10 Nov 2026 08:13:35 +0000

Disclosure: I work on NXTL eSIM, a pay-as-you-go travel data eSIM. The rates below are NXTL eSIM's own, taken from its United States page and rate feed on 10 November 2026 (feed last updated 14 October 2026). Check the live page before you travel. Nothing here is a speed or coverage guarantee.

The US is a strange country for travel data. There's no ID registration for a prepaid SIM or eSIM, the big networks cover the cities well, and yet the price you pay per gigabyte on a pay-as-you-go eSIM can differ by a factor of forty depending on which network your phone lands on. Here's the arithmetic, so you know before you fly.

The quick answer

On NXTL eSIM, data in the US is charged from prepaid balance at the per-GB rate of the network you're connected to, metered in 1 KB steps (you pay for what you use, not a whole gigabyte). On 10 November 2026 the US page listed four networks:

Network	Listed technology	€/GB
AT&T USA	5G, LTE	1.00
Verizon USA	5G, LTE	1.45
T-Mobile USA	5G, LTE	3.73
The Alaska Wireless Network	LTE	41.22

Live table: nxtlsim.com/pricing/?country=United States. The default "Cheapest" network preference prioritises the lowest-priced supported network available (AT&T here), and you can choose another listed network manually in the app.

A 7-day budget, calculated

NXTL's US data-planning guide (editorial facts last checked by NXTL on 2 October 2026) works through a standard 7-day New York or California trip:

Turn-by-turn GPS and transit routing, about 2.5 hours a day: about 140 MB
WhatsApp, photo uploads and family video calls: about 90 MB
Tickets, museum audio guides and restaurant bookings: about 55 MB
Social feeds, stories and evening browsing: about 205 MB
Background sync, email and weather: about 110 MB

That is about 600 MB a day, 4.2 GB for the week, or about 4.6 GB with a 10% buffer. The guide's recommendation is a 5 GB allowance. At the 10 November rates, 4.6 GB costs roughly:

AT&T USA: about €4.60
Verizon USA: about €6.67
T-Mobile USA: about €17.16
The Alaska Wireless Network: about €189.60

The first three are the realistic range for a mainland trip. The fourth is why the last section of this post exists.

The guide's broader ranges: 1 to 2 GB for a 3 to 4 day city break, 3 to 5 GB for a typical week, 5 to 10 GB for a two-week road trip, and 15 to 20+ GB only if you plan daily video calls, laptop hotspotting or remote cloud work. To plug in your own days and habits, the free trip data budget tool works in the browser with no sign-up.

Three US trips, three data profiles

The same guide models three itineraries, and the numbers are surprisingly close:

5 days in New York City: about 580 MB a day, plan for 3 to 4 GB. 5G is strong across Manhattan, Brooklyn and Queens; signal drops between subway stations.
10 days on California's Pacific Coast Highway: about 570 MB a day, plan for 6 to 8 GB. Big Sur's cliffs and canyons have no reception at all, so download the route first.
14 days in the Southwest national parks: about 520 MB a day, plan for 8 to 10 GB. Long desert stretches between parks have zero signal.

The lesson for a US road trip isn't "buy more data", it's "download offline maps". Offline Google Maps gives driving directions, which is what you need between parks.

The three things that blow up a data budget

None of them is navigation, which the guide puts at 15 to 30 MB an hour:

Laptop hotspot tethering, 500 MB to 2+ GB an hour, because a laptop treats a phone hotspot like unmetered Wi-Fi. One hour a day for a week is 3.5 to 14+ GB: roughly €3.50 to €14 on AT&T's listed rate, or €13 to €52 on T-Mobile's. Mark the connection as metered and pause OS updates. Hotspot support follows operator and OS policy, so test it briefly after landing if your laptop depends on it (hotspot checklist).
Cloud photo and video backup, 200 MB to 2+ GB a day in the background. Set iCloud or Google Photos to Wi-Fi only.
Autoplaying video feeds, 300 to 700 MB in an hour of casual scrolling. Switch autoplay to Wi-Fi only.

Cheapest network or widest reach?

NXTL's US page is direct about the trade-off. Verizon has the longest-standing reputation for rural reliability, while coverage in New York, Los Angeles, Chicago, San Francisco and Miami is strong across all three national networks. The practical gaps for a visitor are national parks, mountain regions and the emptiest interstate stretches, not cities.

There's also a phone detail worth checking: T-Mobile's rural reach depends heavily on its 600 MHz low band (n71), and the fastest Verizon and AT&T 5G uses C-band (n77). Most unlocked phones from recent years support these, but an older or regional model may not.

So my practical rule: leave "Cheapest" on for city trips. If you're losing signal on a rural stretch, switch to Verizon manually in the app (the listed rate is €1.45/GB, so the cost difference over a few hundred MB is small), and switch back when you're back in town. Check the network name in your status bar so you know what you're paying.

The one network to watch: Alaska

The fourth listed network, The Alaska Wireless Network, is LTE-only at €41.22/GB, about forty times AT&T's listed rate. If your trip includes Alaska, look at the status bar network name before doing anything data-heavy, keep photo backup and video on Wi-Fi, and budget per megabyte rather than per gigabyte. Pay-as-you-go helps here in one way: nothing forces you to pre-buy gigabytes at that rate, you only pay for what you actually use.

What changes in Canada and Mexico

The same installed eSIM and balance keep working across the border with no new profile; the US page lists Canada and Mexico as land neighbours. The price doesn't carry over, though. Cheapest listed network per country from the same rate feed:

United States: €1.00/GB (AT&T USA)
Canada: €2.03/GB (Freedom Mobile; seven networks listed, up to €4.72/GB on Rogers)
Mexico: €2.13/GB (up to €5.59/GB)

So a Seattle to Vancouver or San Diego to Tijuana day roughly doubles the per-GB price compared with AT&T in the US. Not dramatic, but worth knowing before a long video call on the Canadian side. The North America region page shows the three together.

Do you need a US SIM instead?

The US doesn't require ID registration for a prepaid SIM or eSIM, so there's no passport desk either way. A local US prepaid line can make sense if you're staying for months and need a US phone number. For a holiday or work trip, NXTL eSIM is data-only, so keep your home SIM active for calls, SMS and bank codes, and use the eSIM for data (dual SIM).

Setup checklist

Confirm your phone supports eSIM and is carrier-unlocked: compatible devices and checker.
Install over Wi-Fi before you fly, then turn the eSIM on for mobile data after landing, with data roaming enabled for that line. If your phone asks for an APN, the setup guide lists internet and plus.
Check the network name in your status bar after landing, especially outside the big cities.
Download offline maps for any national park or long desert drive.

About the price

The web starter is US$11.99, which includes US$10.00 of usable prepaid balance (shown as €10.74 including €8.96 when the site is set to euros on 10 November 2026); in-app prices can differ. At AT&T's listed rate, the included balance covers the 5 GB planning allowance above with some left over. Unused balance stays in your account for the next trip, so what you don't spend in the US can cover the next one. It is not a refund. Details: balance conditions and the global eSIM product page.

Doing the East Coast by train? NXTL also has a Northeast Corridor train itinerary guide.

Sources, all checked 10 November 2026: United States eSIM page, pricing, US data planning, Canada page, setup. Rates move with network feeds, so verify live before you buy. Written by the NXTL eSIM team, nxtlsim.com.

Mexico eSIM, pay as you go: what each network costs per GB, a 7-day data budget, and what changes at the border (2026)

NXTL eSIM — Thu, 05 Nov 2026 08:18:28 +0000

Disclosure: I work on NXTL eSIM, a pay-as-you-go travel data eSIM. The rates below are NXTL eSIM's own, taken from its Mexico page and rate feed on 5 November 2026 (feed last updated 14 October 2026). Check the live page before you travel. Nothing here is a speed or coverage guarantee.

If you've only ever bought fixed travel bundles, pay-as-you-go pricing feels vague: how much will Mexico actually cost? It's one multiplication, so here it is worked out.

The quick answer

On NXTL eSIM, data in Mexico is charged from prepaid balance at the per-GB rate of the network your phone is connected to, metered in 1 KB steps (you pay for what you use, not a whole gigabyte). On 5 November 2026 the Mexico page listed four networks:

Network	Listed technology	€/GB
Altan	LTE	2.13
Movistar	5G, LTE	3.04
AT&T	5G, LTE	4.41
Telcel	LTE	5.59

Live table: nxtlsim.com/pricing/?country=Mexico. The network you end up on changes the bill by a factor of 2.6 for the same gigabytes, which is the most useful thing to know before you land.

A 7-day budget, calculated

NXTL's Mexico data-planning guide (last checked by NXTL on 2 October 2026) has a worked 7-day Mexico City and Teotihuacan example:

Ride-hailing and walking directions: about 130 MB a day
WhatsApp, photo uploads and family calls: about 85 MB
Tickets, passes and restaurant look-ups: about 50 MB
Social feeds and evening browsing: about 195 MB
Background sync, email and weather: about 100 MB

That is about 560 MB a day, 3.9 GB for the week, or about 4.3 GB with a 10% buffer. Its own recommendation is a 5 GB allowance. At the 5 November rates, 4.3 GB costs roughly:

Altan: about €9.18
Movistar: about €13.11
AT&T: about €19.02
Telcel: about €24.11

Same trip, same phone use. If you'd rather plug in your own days and habits, the free trip data budget tool works without signing up, and the guide's typical ranges are 1 to 2 GB for a 3 to 4 day city break, 3 to 5 GB for a week, and 5 to 10 GB for two weeks across regions.

The three things that blow up a data budget

The same guide lists the usual culprits, and none of them is Google Maps:

Laptop tethering. The guide puts it at 500 MB to 2+ GB per hour, because a laptop treats a phone hotspot like unmetered Wi-Fi. One hour a day for a week is 3.5 to 14+ GB. At Altan's rate that's roughly €7 to €30; at Telcel's it's roughly €20 to €78. Mark the connection as metered and pause OS updates. NXTL lists hotspot as supported, so test it briefly after you land: hotspot checklist.
Cloud photo and video backup. 200 MB to 2+ GB a day, quietly. Set Google Photos or iCloud to Wi-Fi only.
Video pre-buffering. Autoplaying feeds can pull 300 to 700 MB in an hour of casual scrolling. Switch autoplay to Wi-Fi only.

Lowest rate or widest reach?

NXTL eSIM's default "Cheapest" network preference prioritises the lowest-priced supported network available, and you can pick another listed network manually in the app. In Mexico that means Altan by default.

The NXTL pages are candid that terrain matters: the Mexico page says remote tracks such as Copper Canyon and Sian Ka'an routes and some Pacific surf villages can fade, and the planning guide says remote jungle highways in Chiapas and mountain coastal roads can have intermittent reception, and that metro tunnels and thick-walled colonial buildings dampen signal. So for a Mexico City, Oaxaca or Cancún trip, the default is the cheap choice. For a long road trip, download offline maps first (offline Google Maps gives driving directions only, not walking or transit routing), and if you're losing signal on a stretch, try another listed network manually and compare the status-bar name. Switching networks in the app is free.

What changes at the border

The same installed eSIM and balance keep working in neighbouring countries on NXTL's list, with no new profile. The price doesn't carry over, though. From the same 5 November 2026 rate feed (cheapest listed network per country):

Mexico: €2.13/GB
Guatemala: €5.81/GB
Belize: €11.40/GB
United States: €1.00/GB at the cheapest network, up to €41.22/GB at the most expensive

Mexico's page lists Belize, Guatemala and the US as sharing a land border. The Belize and Guatemala figures are why a "same eSIM everywhere" story isn't the same as "same price everywhere": check the destination's rate before a cross-border day trip, and keep heavy downloads for Wi-Fi.

Do you need a local SIM instead?

Probably not for a holiday or short work trip, per NXTL's own page: local prepaid SIMs are sold at OXXO, airports and operator stores with passport registration, while NXTL's data-only eSIM gives no local number, so there's no shop registration. A local SIM can still be the right call if you're living in Mexico for months and need local calls or a local number for delivery and concierge apps. NXTL eSIM is data-only, so keep your home SIM active for calls, SMS and bank codes (dual SIM).

Setup checklist

Confirm your phone supports eSIM and is carrier-unlocked: compatible devices and checker.
Install over Wi-Fi before you fly, then turn the eSIM on for mobile data after landing, with data roaming enabled for that line. If your phone asks for an APN, NXTL's APN is plus (setup guide).
Check the network name in your status bar after landing.
Mexico is more expensive per GB than much of Europe or Asia on NXTL, so size your balance before you go rather than guessing.

About the price

The web starter is US$11.99, which includes US$10.00 of usable prepaid balance and a US$1.99 eSIM; the site shows a conversion in your checkout currency, and in-app prices can differ. Unused standard balance stays in your account while the account is active, subject to the terms, so what you don't spend in Mexico can cover the next trip. It is not a refund. Details: balance conditions and the global eSIM product page.

Planning a Mexico City and Oaxaca route? NXTL has an 8 to 10 day itinerary and safety guide too.

Sources, all checked 5 November 2026: Mexico eSIM page, pricing, Mexico data planning, setup. Rates move with network feeds, so verify live before you buy. Written by the NXTL eSIM team, nxtlsim.com.

Does my phone support eSIM? A two-minute check before your trip (and why "has eSIM" isn't enough)

NXTL eSIM — Sun, 01 Nov 2026 08:12:14 +0000

Disclosure: I work on NXTL eSIM, a pay-as-you-go travel data eSIM. The checker described below is our own free, open-source tool. Facts were checked on 1 November 2026 against the linked manufacturer and nxtlsim.com pages.

Every week someone buys a travel eSIM, lands, and finds out their phone can't install it. Usually the phone does have eSIM hardware. The problem is one of three other things: the phone is carrier-locked, it's a regional version without eSIM, or the menu they were told to look for doesn't exist on their software version.

Here's the check I'd do before paying for any eSIM, from any provider. It takes about two minutes.

Step 1: The 10-second hardware test (`*#06#`)

Open the phone dialler and type *#06#.

If you see an EID (a long 32-digit number) alongside your IMEI, the device has an eSIM chip.
If you only see IMEI numbers, treat that as a strong sign the phone has no eSIM, and check the exact model (step 3).

This is the fastest test because it doesn't depend on menus, which move around between Android skins and iOS versions.

A note on "IMEI eSIM checkers": an IMEI identifies your device (its first 8 digits, the Type Allocation Code, identify the model), but it doesn't tell you whether your carrier locked the phone. That's step 2, and it's the one people skip.

Step 2: Is the phone carrier-unlocked?

Having eSIM hardware is not enough. To install another provider's eSIM, the phone must accept third-party profiles, which means it must be network-unlocked.

iPhone: Settings → General → About. Under Carrier Lock, "No SIM restrictions" means it's unlocked.
Samsung Galaxy / Google Pixel: there's no single universal screen for this. If a carrier supplied the phone (contract, financing, "free phone" deals), ask that carrier whether it's unlocked before you travel.

Step 3: Check the exact model and where it was sold

Model names hide regional versions. Two examples from manufacturer pages:

Samsung Galaxy A54: Samsung's eSIM support page lists eSIM for the Galaxy A54 in "Europe, North America, Korea, and Japan only". The Galaxy A35 and A36 are listed for "Europe, North America, and Korea only". So "does the Samsung A54 have eSIM?" really means "does my A54 have eSIM?", and the answer depends on where it was sold. (Samsung eSIM support page)
iPhone bought in mainland China, Hong Kong or Macao: several iPhone generations were sold there in dual-physical-SIM versions with no eSIM. For example, the iPhone 15's mainland China model A3092 has two physical SIM slots and no eSIM. Check the model number (Settings → General → About), not just the name.

Then confirm the option actually exists in settings:

iPhone: Settings → Mobile Data (or Cellular) → Add eSIM
Samsung Galaxy: Settings → Connections → SIM manager → Add eSIM
Google Pixel: Settings → Network & internet → SIMs → add an eSIM
Windows laptop: Settings → Network & internet → Cellular, look for eSIM profiles (a Wi-Fi-only laptop can't install one)
Tablets: you need the cellular version; Wi-Fi-only tablets can't install an eSIM

Two things not to do: don't delete an existing eSIM "to test" compatibility (you may not be able to reinstall it), and don't assume 5G means eSIM. 5G is a network technology; eSIM is a separate device feature.

Step 4 (optional): Look it up in a checker

We built a small, free eSIM compatibility checker because most checkers either live behind a provider's checkout or only list marketing model names.

How it works, for the curious:

It's a static page plus one JSON file (devices.json, currently 407 devices: phones, tablets, laptops, routers and vehicle equipment). No backend, no sign-up, no trackers. Source on GitHub.
Each device has a status rather than a yes/no: supports eSIM, depends on region/version, cellular version needed, depends on configuration, needs an eSIM adapter, or no eSIM. The Galaxy A54, for instance, comes back as "depends on region / version".
You can search by model number, not only name. Samsung SM-xxxx codes are matched on their base code, and Apple Axxxx numbers map to the right model, including notes on mainland-China variants. Model codes come from Google Play's public supported-devices list and Apple's model-identification pages.
Every result is a shareable URL, so you can send "check this" to a travel companion and they see the same result.
Each entry links the manufacturer source it was taken from. The device list mirrors the compatible devices page on nxtlsim.com, last reviewed 9 September 2026.

It's not authoritative over your phone's own settings screen. If the checker says yes but Add eSIM isn't there, trust the phone.

What about routers and hotspots?

If you want one connection for a laptop, tablet and a partner's phone, a travel router can be simpler than hotspotting from your phone. Check that the exact router model accepts third-party eSIM profiles, not just a physical SIM or the vendor's own plans. Some routers need an eSIM adapter. Devices that join a hotspot over Wi-Fi don't each need their own eSIM.

The short version

Dial *#06#: EID shown means eSIM hardware.
Confirm the phone is carrier-unlocked.
Check the exact model number and where it was sold (Galaxy A54/A35/A36, China/HK/Macao iPhones).
Confirm Add eSIM appears in settings, or look the model up in the free checker.

Once your phone passes, then compare eSIMs. If you travel more than once a year, a reusable pay-as-you-go eSIM like ours avoids re-checking and re-installing for every trip: NXTL Global eSIM is a data-only eSIM for 180+ countries where you pay per GB used, and your balance stays while your account is active. Setup steps are on the eSIM setup guide.

Checked 1 November 2026. Menu names vary by software version; if something differs on your device, the manufacturer's guidance wins.

Four small travel-data web tools we open-sourced (static PWAs, no sign-up, shareable by URL)

NXTL eSIM — Tue, 27 Oct 2026 16:41:32 +0000

Written by the NXTL team. We make a pay-as-you-go travel eSIM, and these tools come from questions our customers ask. They work whatever provider you use, and everything is MIT-licensed on GitHub.

Most "how much data do I need?" answers online are a single number with no workings. We wanted small tools that show their assumptions, run entirely in the browser, and give you a link you can send to whoever you're travelling with. Here are the four we've shipped so far, plus a few build notes in case you're making something similar.

1. Trip Data Budget Planner

Live: nxtlsim.github.io/trip-data-budget · Code: github.com/nxtlsim/trip-data-budget

Pick destinations and days, choose a preset (Light, Normal, Heavy, Remote work) or set hours per activity, and you get a per-day and per-trip estimate in MB/GB. Every assumption is in a table on the page, with a 10% buffer for background use, so you can see exactly why the number is what it is.

The whole state lives in the query string, so a plan is just a link:

https://nxtlsim.github.io/trip-data-budget/?d=Turkey:7,Japan:5&p=normal

The figures are rounded estimates, not measurements. If your usage is different, change the hours and the total follows.

2. eSIM Compatibility Check

Live: nxtlsim.github.io/esim-compatibility-check · Code: github.com/nxtlsim/esim-compatibility-check

"Does my phone support eSIM?" sounds simple until you hit regional variants. The checker covers 407 phones, tablets, laptops and routers, and each entry links to the manufacturer's own documentation, so you can check the source rather than trust us.

The interesting part was detection without permission prompts:

Android Chromium: navigator.userAgentData.getHighEntropyValues(['model']) returns the model code (for example SM-S921B), which we match to its device family. If that isn't available we fall back to the user-agent string.
iPhone/iPad: iOS doesn't expose the model to websites at all, so the page shows iPhone guidance and lets you pick your model, with per-SKU exceptions flagged (some mainland-China models use two physical SIMs instead of eSIM).

It also shows the on-device way to confirm: dial *#06# and look for an EID.

3. Team & Hotspot Data Planner

Live: nxtlsim.github.io/team-data-planner · Code: github.com/nxtlsim/team-data-planner

For teams and device fleets: add laptops, work phones, backup routers, GPS trackers, cameras or POS terminals, set quantities and days, and get data per day, per 30 days and in total, with a per-item breakdown. The presets (for example 1,500 MB/day for a remote-work laptop, 3 MB/day for a GPS tracker) are labelled as rough starting points, and every one is editable. Replace them with your real usage stats when you have them.

?i=laptop:3,router:1:500&c=Germany&days=30

4. travel-connection-check (CLI)

Code: github.com/nxtlsim/travel-connection-check

Is the hotel Wi-Fi good enough for a video call, or should you switch to mobile data? One command gives latency, jitter, packet loss and download speed, and appends a row to a CSV, so you build up a log of every network you've tested across countries.

git clone https://github.com/nxtlsim/travel-connection-check
cd travel-connection-check
python3 travel_connection_check.py --country JP --network "hotel wifi"

It's standard-library Python 3.8+ only, so it runs on macOS, Linux, Windows and Termux on Android. Because speed tests on metered data aren't free, it also prints roughly how much data the test itself used, and you can pass --no-download for a latency-only check that uses about 0.05 MB.

Build notes

Static and installable. The three web tools are plain HTML/JS on GitHub Pages with a manifest and service worker, so they install to a phone home screen and keep working on flaky connections, which is exactly when you need them.
State in the URL. No accounts and no database. Sharing a result is sharing a link, and preview cards come from static Open Graph tags.
Show the assumptions. Each estimate sits next to the table that produced it. People trust a number more when they can argue with it.
Live data with a fallback. The cost line in the two planners reads per-country rates from a public endpoint and falls back to a bundled JSON snapshot if that request fails, so the planners still work offline.
No trackers. Nothing is stored and there's no analytics script on the pages.

Where NXTL fits

The planners show an optional cost line at NXTL's pay-as-you-go per-GB rate for the country you pick. That's the only NXTL part, and current prices are on nxtlsim.com/pricing. The data estimates themselves are provider-neutral.

Issues and pull requests are welcome, especially corrections to the device list (with a manufacturer source) and better usage figures for specific apps.

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.

DEV Community: NXTL eSIM

USA eSIM, pay as you go: AT&T vs Verizon vs T-Mobile per GB, a 7-day data budget, and the one network to watch (2026)

The quick answer

A 7-day budget, calculated

Three US trips, three data profiles

The three things that blow up a data budget

Cheapest network or widest reach?

The one network to watch: Alaska

What changes in Canada and Mexico

Do you need a US SIM instead?

Setup checklist

About the price

Mexico eSIM, pay as you go: what each network costs per GB, a 7-day data budget, and what changes at the border (2026)

The quick answer

A 7-day budget, calculated

The three things that blow up a data budget

Lowest rate or widest reach?

What changes at the border

Do you need a local SIM instead?

Setup checklist

About the price

Does my phone support eSIM? A two-minute check before your trip (and why "has eSIM" isn't enough)

Step 1: The 10-second hardware test (*#06#)

Step 2: Is the phone carrier-unlocked?

Step 3: Check the exact model and where it was sold

Step 4 (optional): Look it up in a checker

What about routers and hotspots?

The short version

Four small travel-data web tools we open-sourced (static PWAs, no sign-up, shareable by URL)

1. Trip Data Budget Planner

2. eSIM Compatibility Check

3. Team & Hotspot Data Planner

4. travel-connection-check (CLI)

Build notes

Where NXTL fits

How Much Mobile Data Do You Actually Use When Travelling?

Rough data use by activity

Maps and navigation

Messaging

Social media

Music and podcasts

Video streaming

Video calls

Hotspotting a laptop

A few sample trip profiles (rough estimates)

How to measure your own usage before you go

How to cut usage without missing out

Choosing a plan that matches your estimate

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

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

2. Check eSIM compatibility properly

3. Budget data for developer workloads

4. Measure your usage, don't guess

5. VPN notes

6. Have backup connectivity

The short version

Step 1: The 10-second hardware test (`*#06#`)