How Many GB Do I Need for Nepal? A Guide by Travel Profile

Nepal is one of those destinations where the question of how many GB I need has an unexpected answer: fewer than you think. Kathmandu and Pokhara are full of Wi-Fi, and on the trekking routes—Everest Base Camp, Annapurna Circuit—you'll spend entire days without coverage, so there's no data to use. Here's the number, the why, and what will really be a hassle up there, which isn't the gigabytes.

The short answer, straight to the point

For 10 days in Nepal combining Kathmandu, Pokhara, and some trekking, most people will find 3 GB more than enough, and 5 GB will be ample. If you go for two weeks to Everest Base Camp, you'll use even less: there's no coverage to consume data up there.

I know this sounds strange coming from someone who sells data, but it's what I see time and again with Nepal. The average traveler returns with half their data package untouched. And not because they're restraining themselves: it's because the country itself cuts off the supply. In cities, you have Wi-Fi everywhere, and in the mountains, there's no network.

My honest recommendation, depending on your trip:

• Classic 10-12 day trip (Kathmandu, Pokhara, Chitwan, short trek like Poon Hill): 3 GB is plenty.
• Long trek of 14-18 days (Everest Base Camp or Annapurna Circuit): 3 GB and you'll still have some left over, because half the trip is spent without signal.
• City trip, photos, and lots of social media stories, two weeks: 5-8 GB.
• Working from there (Pokhara has become fashionable for this): 20 GB or more, and even then, the bottleneck will be speed, not volume.

If you've never used an eSIM and want to understand exactly what it is before deciding on the size, take a look first and then come back here for the number. It's important to buy with your actual trip in mind, not out of fear of running out.

Why Nepal splits your data consumption into two halves

Nepal is not one destination, but two. And they consume data in opposite ways.

Half one: the cities. Kathmandu and Pokhara work quite well. The 4G of local operators ranges from 20 to 50 Mbps in good areas, enough for maps, messaging, uploading photos, and decent video calls. And most importantly: in Thamel (Kathmandu) and Lakeside (Pokhara), almost every guesthouse, cafe, and restaurant has free Wi-Fi. If you eat breakfast, lunch, and dinner at places with Wi-Fi, a lot of your mobile data usage shifts to the local network. In Chitwan and on the road, it drops to 3G in many stretches, but it's still fine for WhatsApp and maps.

Half two: the mountains. Here, it's not just slow; it's non-existent. In the higher reaches of Everest and the Annapurnas, the signal disappears for days. And that, for your data bill, is an absurd blessing: these are days of zero consumption.

There's a third, intermediate scenario that people often forget: journeys. The Kathmandu-Pokhara bus takes between 6 and 8 hours, and a good part of the road has a signal. If you start watching videos to kill boredom, you can easily burn through 1 GB in one afternoon all by yourself. That bus journey is the biggest data devourer of the entire trip, more than any temple or any peak. Download your series or podcasts at the hotel, using Wi-Fi, the night before.

If you're still deciding how to connect, you'll find a detailed breakdown in the guide to internet in Nepal.

How much data each activity will actually use there

The numbers people have in their heads are usually wrong in both directions: they think maps devour data (they don't) and that social media is harmless (not at all). Here's the table I use for calculation:

Notice the jump between the last two rows: the same movie, five times more data, on a six-inch screen where you barely notice the difference. You have the full breakdown in the data usage statistics by activity.

How many GB according to your profile and the length of your stay

This is the table that matters. It's calculated assuming what actually happens in Nepal: that you'll almost always sleep in places with Wi-Fi, and that if you're doing high-altitude trekking, several days will have zero consumption.

A couple of nuances that make the table more useful:

• The trekking profile uses less data than the maps and WhatsApp profile for the same number of days. This is not an error in the table: it's because half of those days you have no network.
• If you're going to share your connection with your partner or group, add between 50% and 80%, not double: much of the consumption is shared (maps, looking up places) and doesn't double.
• Remote work is a different game. Work video calls use 200-600 MB per hour, and for that, you really need volume.

If you're torn between two sizes, go with the smaller one and top up if necessary. I explain this in detail below. And if you want the general method applied to any country, it's in the guide on how much data I need for travel.

Trekking: where mobile data becomes useless

Let's get straight to the point with this, because it causes the most confusion. At Everest Base Camp and in the upper part of the Annapurna Circuit, mobile data does not work. Not yours, not a local SIM's, not anyone's. There are patches of signal in some villages and passes, but you can't rely on them.

Of the two Nepalese operators, the state-owned (NTC) holds up a bit better at altitude, and the private one (Ncell) is faster at lower elevations. But beware: holding up better at altitude means it cuts out 200 meters higher, not that you'll have Instagram at base camp.

The practical conclusion is inconvenient for someone who sells gigabytes: for pure trekking, data is not the solution. The solution is to prepare your phone to function without it.

Teahouse Wi-Fi and its cost

In the mountain lodges, they do sell internet, almost always via satellite, with cards or codes for hours or by session. It works, but it's good to know what you're buying before getting indignant up there.

These are indicative prices from a recent season: they change per lodge, per season, and depending on how far the generator is. What doesn't change is the experience: the connection is slow, it's shared with the entire dining room, and it cuts out when the weather worsens. It's enough to send an "I'm okay" message and little else. Uploading a photo carousel to Instagram from Lobuche is an expensive way to get frustrated.

My advice is to budget for two or three connections for the entire trek, not a daily one: one halfway up, one upon reaching the top, and one on the way back. With that, you can let people at home know you're fine, check the weather forecast, and keep walking. It's cheaper and more enjoyable.

Battery is the real problem, not gigabytes

Here is the real bottleneck of trekking in Nepal, and almost no one mentions it when talking about data: the problem isn't how many GB you have, it's that your phone dies.

Three things conspire against you:

• The cold. Below zero, lithium batteries lose capacity drastically. A phone at 60% can suddenly turn off when you take it out of your pocket in the morning.
• No free sockets. Lodges run on solar and generators, and the dining room socket is shared by twenty people.
• They charge for charging. Between 200 and 500 rupees per charge, and more the higher up you go. Charging your phone, camera, and headlamp every night for two weeks becomes a serious expense.

What works, in order of usefulness:

1. 20,000 mAh power bank (the usual limit for carry-on luggage). Provides four or five full phone charges.
2. Airplane mode almost all day. This is the biggest battery saver: without a signal, the phone drains itself constantly searching for a network. And it saves you data too.
3. Sleeping with your phone and battery inside your sleeping bag. Body heat prevents them from waking up at 20%.
4. Low brightness and gray screen when you only use it for the camera and maps.

If you're low on battery, the gigabytes in your package don't matter: you won't be able to use them even if there's coverage. That's why a good power bank is worth more than any data top-up for a multi-day trek.

What to download before leaving Kathmandu

If trekking is going to be the bulk of your trip, preparation matters more than the package size. Here's what I get ready using hotel Wi-Fi, the night before heading up:

• Offline maps. Download the entire area in Google Maps, and even better, install a hiking map app with downloaded routes. Your phone's GPS works without coverage and without data: what's missing when there's no network is the map, not your position.
• Permits and bookings in PDF saved on your phone (TIMS, national park entry tickets, travel insurance, Lukla flight) and also in print.
• Translator with the language pack downloaded, in case you need to understand each other off the tourist routes.
• Music, podcasts, and series stored locally. Ten days of walking provide plenty of audio, and downloaded content doesn't use a single megabyte.
• Photos of your itinerary shared with someone at home: approximate villages and dates.

And now the part that isn't technical but is the most important: let people at home know you'll be out of touch. Explain before you leave that you'll be without signal for several days, state which villages you'll try to write from (Namche on the way up, Namche on the way back, for example), and make it clear that silence is normal, not a bad sign. This conversation prevents more distress than any data package.

If you're traveling alone on remote routes, consider a satellite messenger with an emergency button. It's the only thing that truly works where there's no network, and it has nothing to do with mobile data.

Calculate your own consumption before traveling

All of the above are averages. Your actual consumption is already measured in your pocket, and you just need to check it. It's the most reliable method I know and it takes two minutes:

• On Android: Settings → Network & Internet → Mobile data usage. You'll see the total for the last cycle and the breakdown by app.
• On iPhone: Settings → Cellular. Scroll down to the list of apps. Note: this counter accumulates since the last time it was reset, so set it to zero one month before your trip to get a clean reading.

With that monthly number, make three adjustments:

1. Divide by 30 to get your daily consumption and multiply by the number of travel days.
2. Subtract the video and music you consume at home via Wi-Fi but won't watch in Nepal: on a trek, there's no time or desire for it.
3. Subtract the days spent in high mountains. If out of 14 days, 6 have no coverage, your calculation drops by almost half. This adjustment is unique to destinations like this and is what throws everyone off.

A real-world example: if you spend 8 GB per month in Spain, that's about 270 MB per day. Fourteen days would be 3.7 GB, but removing at-home video and six days without signal leaves you with less than 2 GB. That's the figure you should buy with, not the one dictated by fear.

How to stretch your data in Nepal

Even if you buy little, these habits will ensure you have plenty left over. None of them force you to give up anything important:

• Data saver mode activated from day one. On Android, it's in Settings → Network & Internet; on iPhone, it's "Low Data Mode" within Cellular Data. This cuts down on background updates and syncs.
• Photo backups only via Wi-Fi. This is the number one leak: Google Photos or iCloud uploading 300 Annapurna photos in the background will eat up your entire plan without you even noticing.
• Disable auto-play for videos on Instagram, TikTok, X, and Facebook. This alone can halve your social media data usage.
• Lower the upload quality of photos and videos in WhatsApp. The visual difference on your mom's phone is negligible.
• Take advantage of Wi-Fi in guesthouses and cafes in Thamel and Lakeside for all heavy tasks: uploading carousels, updating apps, long video calls, downloading series.
• Download maps even in the city. Kathmandu is a labyrinth, and using offline maps saves you data and battery.

With these six habits, a two-week trip can easily fit into 3 GB. I have more tricks, some quite specific, in the guide on how to save data while traveling.

What happens if you run out of data?

The question that stops many people from buying the small package. The short answer: running out is not a disaster; overpaying is guaranteed wasted money.

When you run out of data, you simply stop browsing. There are no surcharges or surprises on your bill, and calls and SMS from your home line still work as usual. To get internet again, you have three options, all easy:

1. Recharge from your phone, using hotel Wi-Fi, in two minutes and without changing any settings.
2. Use Wi-Fi until the next city: in Kathmandu and Pokhara, it's on every corner.
3. Buy an additional package of the size you need, not more than you need.

Compare that to the opposite scenario: you pay for 20 GB, use 4, and the remaining 16 evaporate when the plan expires. Data doesn't come home with you. That's why my rule for Nepal is as boring as it is effective: start small and recharge. It's the only destination where I openly recommend the basic package to almost everyone.

Just check one thing before buying: the validity in days. A 3 GB package with 7 days validity is useless if you're staying for three weeks. Adjust the days first, then the gigabytes. Coverage and activation details are in the eSIM for Nepal guide.

Frequently Asked Questions

Conclusion

Nepal is the destination where I most confidently recommend buying a small amount. 3 GB will cover a typical ten- or twelve-day trip, and if your plan is a long trek, you probably won't even use that much, because Everest Base Camp and the upper Annapurnas simply have no coverage. The challenge there isn't gigabytes: it's battery life, downloaded maps, and having informed home that you'll be out of touch. Don't let anyone tell you otherwise: no data package, no matter how large, can put antennas where there aren't any, and in Khumbu above Dingboche, there simply aren't any.

So the recommendation is simple: 3 GB for almost everyone, 5-8 GB if you're someone who uploads a lot of photos and will be spending two weeks in cities, and only large sizes if you plan to work remotely from Pokhara. If you run short, you can recharge in two minutes from your hotel's Wi-Fi. I'd prefer you come back saying you had plenty left over rather than having sold you a package that ran out in a valley without antennas.

Once you've decided, here's the data eSIM for Nepal: activate it before leaving home and arrive in Kathmandu with internet working.

Written by Marc González Sáez Founder of PuraSim and a specialist in eSIM and connectivity for travelers. He has been helping people travel connected worldwide for years without overpaying for roaming, and personally tests eSIMs in each destination before recommending them.