Most sizing advice divides a total by the number of nights, which is the one method guaranteed to be wrong on this kind of trip. A three-week Asia-Pacific route is not twenty-one similar days. It is five or six days that consume almost everything and fifteen that barely register, and the whole question is how many of the first kind you have booked.
If you want the number before the reasoning: a few days in one city runs on roughly 1 to 3 GB, a week on 3 to 5 GB, and a two-week multi-country route on something like 8 to 12 GB, with 15 GB and upwards if you are working as you go. The Asia Pacific eSIM sells in five sizes, and on a long route the validity window matters as much as the gigabytes.
The sizes, and how long each one lasts
| Data | Validity | | --- | --- | | 1 GB | 30 days | | 3 GB | 30 days | | 5 GB | 30 days | | 10 GB | 30 days | | 20 GB | 90 days |
The step from 10 GB to 20 GB is not only a step up in allowance. It is also the step from a month to three months, and on a long Asia-Pacific circuit that is frequently the deciding factor rather than the data.
So work out how many days you need covered first, look only at the steps that reach that far, then choose the allowance from what is left. The other order produces a plan that runs out of calendar with gigabytes still on it. A generous allowance on a short window is not generous.
Count the days that move
A moving day is any day the itinerary changes location or mode: an airport day, an intercity train, a ferry, a border, the first day in a new city. On those days the phone is open continuously — a boarding pass, a live map, a driver's approach, a booking that needs re-reading — and it is doing all of it outdoors, on the move, on an unfamiliar network.
A static day is the opposite. You wake in the same place, walk somewhere, and use the phone in short deliberate bursts with Wi-Fi at both ends of the day. Three days in one city with the same hotel each night is a light week's worth of use, not three days' worth.
Worked through on a real shape: three weeks running Sydney, Queenstown, Tokyo, Kyoto, Singapore and Bali. That is five flights, one intercity rail leg and six first-days-in-a-new-place, so roughly twelve heavy days inside a twenty-one-day trip. Sized on twelve moving days rather than twenty-one average ones, the estimate lands in a different place — and it tells you which days are worth preparing for in advance.
What a 5 GB allowance actually buys
Abstract gigabytes are hard to reason about, so here is the same allowance expressed as things you recognise. Roughly, 5 GB covers any one of these:
| Activity | Roughly | | --- | --- | | Maps and navigation | about 1,000 hours | | Social feeds and browsing | about 83 hours | | Music streaming | about 63 hours | | Photos shared | about 1,700 | | Video calls | about 15 hours |
Read down that column and the shape of the problem changes. Navigation is effectively free at this scale. Video calling is the expensive one, and video streaming — not on the list because it is not really a travel activity — is what turns a comfortable estimate into a tight one.
What eats the allowance on this route
Ranked roughly by how much they surprise people here specifically:
- Live navigation in dense cities. A Tokyo or Bangkok day following a moving blue dot through interchanges is the heaviest map use of the trip.
- Translation. Camera and voice translation are used constantly in this region and almost never budgeted for.
- Ride-hailing. The location stays live through the wait, the ride and the payment.
- Check-ins. Airline, ferry and rail apps, always opened at the least convenient moment.
- Photo and video backup. The largest line item on most trips, and the easiest to move onto Wi-Fi.
Messaging apps barely register. Maps and messaging together rarely explain a blown allowance; automatic uploads and video usually do.
Tip: If a laptop is going to join the phone's connection, size for the laptop rather than the phone. Where the selected plan and the device allow it, sharing works, but a laptop that runs system updates and syncs a photo library can move more in one hour than a phone does in a full day of maps. If someone is working on this trip, that single fact matters more than every other item on this page.
Which size fits which trip
One city, a few days. 1 to 3 GB. The map is downloaded on the first evening and the rest goes on messaging and searches.
A week, one or two countries. 3 to 5 GB. Enough for daily navigation, photos going home and a couple of video calls.
Two weeks, several countries. 8 to 12 GB, so the 10 GB step. This is where most multi-country Asia-Pacific routes land: navigation every day, frequent translation, and a run of moving days rather than one.
Three weeks or more, or you are working. 20 GB, and note that this is also the step that reaches 90 days. Anyone sharing to a laptop should start here rather than expecting to correct it later.
Translation is the one people forget
In Japan, Korea, Thailand and Vietnam the phone spends more time translating printed things than spoken ones — a menu, a ticket machine, a station notice, a label in a pharmacy. That happens in short bursts many times a day, outdoors, exactly where you cannot fall back on Wi-Fi.
It is not enormous in total, but it clusters on the same moving days that already carry the navigation load. Downloaded language packs cover much of it and ask nothing of the allowance at the moment you need them most, which makes this the simplest adjustment here.
Four ways to make the number smaller
- Set photo and video backup to Wi-Fi only, before you leave rather than after the first big upload.
- Download the offline area for tomorrow's city while you are at tonight's hotel.
- Download language packs for every country on the route in one sitting.
- Keep long video for the evenings, where a hotel connection carries it instead.
None of these is dramatic alone. Together they routinely move a route down one step on the ladder.
Short answers
Can I start smaller and add data later? Only where the package you chose supports it, and support is not universal — read the details of that exact plan rather than assuming. Where it is offered, it turns sizing from a forecast made at home into a correction you can make in week two.
Does the allowance reset at each border? No — the same single balance carries across every destination named in the plan, for as long as that plan runs.
Is the top step too much for a fortnight? Usually. A fortnight of ordinary use sits nearer the 10 GB rung. Reach for the top of the ladder when the calendar is long rather than when the days are busy, or when a second device is sharing the line.
What if one stop is not on the list? Then that leg needs its own plan. Which destinations a regional label includes is settled in Asia eSIM vs APAC eSIM, and the long-haul route this sizing usually belongs to is mapped in one eSIM for Australia, New Zealand, Japan and Southeast Asia.
Ready to pick a size? The sizes and validity periods sit beside the destinations they apply to on the Asia Pacific eSIM page — give the live destination list a last check for each stop before buying, since coverage can change. Single-country sizing is worked through in how much data for a Bali trip and in the best eSIM for Thailand.