You've got your flights, your itinerary is more or less set, and one silly question keeps nagging at you: how many GB do I need for the United States so I don't run out or overpay? I'll answer you with numbers, not "it depends." Because in the United States, the number changes significantly depending on whether you're in a city or on the road, and that's the whole story.
The short answer, no beating around the bush
For 10 days in the United States, most people will be fine with 3 GB if they're moving around a city and using hotel Wi-Fi. If you're doing a road trip—maps and music for hours a day—count on 10 GB. And if you're teleworking or sharing a connection with family, 20 GB.
That's the real range, and it's huge for one specific reason: in the United States, there are two completely different types of trips within the same country. Someone who lands in New York, gets around by subway and Uber, and sleeps in a hotel with decent Wi-Fi will barely touch their data. Someone who rents a car in Las Vegas and covers a thousand miles of desert with Google Maps on and Spotify playing will multiply their consumption by five or six.
My initial advice: don't buy thinking about the worst imaginable day. Buy thinking about your normal day and leave room for two or three bad days. If you have half the package left over, you've overpaid; if you run out, you can top up in two minutes from your phone, and it's no big deal. The asymmetry works in favor of being just right.
If you're coming from another destination and want the general overview before delving into the specifics of the United States, you can find the complete summary in the guide on how much data I need for travel. Here, I'm going straight to what makes this country special.
Why the United States changes the number
There are four factors that, together, explain why the recommendation for the United States is unlike that for a weekend in Rome.
- Distances. Here, you don't go from one city to another in 40 minutes by train. You go by car, four or five hours, with your phone navigating the whole time and no Wi-Fi handy during the entire journey.
- Free Wi-Fi is everywhere. And this seriously works in your favor. Starbucks offers it in all its own cafes across the country, as do Dunkin', Panera, McDonald's, Target, Walmart, and any shopping mall. Hotels and motels provide it as standard. A city traveler can spend 70% of the day connected to someone else's Wi-Fi without even trying.
- Uber and Lyft are essential. Outside of New York, Chicago, or Boston, public transportation is minimal. You'll be ordering cars daily. The good news: ordering and tracking a ride uses very little data, barely a few megabytes.
- National parks have no coverage. This sounds like a problem, and partly it is, but for data consumption, it's the opposite: days in Yellowstone or Death Valley are days of almost zero consumption, because there's no network to use.
If you're also wondering what type of connection is best for you—and not just how many gigabytes—I break that down in the guide to internet in the United States. This article assumes you've already decided to buy data and just want to get the size right.
How much each app really uses
Before choosing a package, it's good to have the numbers in mind, because almost everyone makes the same mistake: they think maps are the monster and social media is harmless. It's exactly the opposite.
| Activity | Approximate Consumption |
|---|---|
| Google Maps navigating with live traffic | 5–10 MB per hour |
| Google Maps with map already downloaded | less than 1 MB per hour |
| WhatsApp: messages, audios, and loose photos | 2–5 MB per hour |
| WhatsApp video call | ~300 MB per hour |
| Instagram or TikTok scrolling | 700–850 MB per hour |
| Uploading a photo from phone to cloud or group | 3–5 MB per photo |
| Spotify in normal quality | ~40 MB per hour |
| Spotify in high quality | ~150 MB per hour |
| YouTube at 480p | ~300 MB per hour |
| YouTube at 1080p | ~1.5 GB per hour |
| Zoom video call at 720p | ~1 GB per hour |
| Ordering and tracking an Uber or Lyft | 5–10 MB per trip |
| Email, searching restaurants, reading reviews | 10–25 MB per hour |
Notice the contrast: a full hour navigating with Google Maps uses less than ten seconds of scrolling on TikTok. That's why road trips don't gobble up gigabytes for maps, but for music and for the bored co-pilot with a phone in hand. I have a detailed breakdown in the data usage statistics by activity, with more apps and scenarios. Remember this: video rules, and the rest is noise.
City profile: fewer GB than you think
A city trip in the United States—New York, Miami, Los Angeles, Chicago, San Francisco—is one of the least data-consuming trips in the world, and Wi-Fi is to blame. You have breakfast in a cafe with Wi-Fi, the museum has Wi-Fi, the mall has Wi-Fi, the hotel has Wi-Fi. The hours of actual mobile data use are reduced to travel and time spent on the street.
A typical city day looks like this: twenty minutes of Google Maps spread across short trips, three or four Ubers, a handful of restaurant searches, the family WhatsApp group, and some time on social media. Total: between 150 and 500 MB per day, depending on how much you scroll.
If you're someone who only uses maps and WhatsApp, and uploads photos at night from the hotel, your actual consumption will be around 100 MB per day. Ten days like that is just over 1 GB. With 3 GB, you'll have plenty to spare for unexpected situations. To tell you otherwise would be to sell you hot air.
If you're someone who uploads stories daily, watches reels in line at the Empire State Building, and sends videos to the group, bump it up to 500-600 MB per day and the calculation changes: 5 GB for ten days, 10 GB for two weeks. It's still reasonable.
Beware of a classic trap: automatic mobile backups. If you have Google Photos or iCloud uploading every photo as you take it, your consumption will skyrocket without you noticing. That can be turned off in two taps, and we'll cover it below.
Road trip profile: the gigabyte guzzler
This is the real data consumer on a trip to the United States. A road trip day is an entire day away from any Wi-Fi, with your phone working non-stop: Google Maps on for four or five hours straight, streaming music in the car, and that very American habit of deciding on the fly—finding the cheapest gas station, checking if the motel at the next exit has good reviews, seeing if the diner is still open at ten.
Compare the two days with the same figures from the table above:
| Usage | City day | Road trip day |
|---|---|---|
| Maps and navigation | 20 min ≈ 3 MB | 4-5 h ≈ 40 MB |
| Streaming music | 30 min ≈ 20 MB | 4 h ≈ 160 MB |
| Social media and video | 30 min ≈ 350 MB | 45 min ≈ 550 MB |
| WhatsApp and photos to group | ≈ 60 MB | ≈ 80 MB |
| Searching gas station, motel, reviews | ≈ 20 MB | ≈ 90 MB |
| Uploading photos to cloud | Hotel Wi-Fi: 0 | Motel Wi-Fi: 0 |
| Approximate total | ≈ 0.45 GB | ≈ 0.9 GB |
In other words: a road trip day easily doubles a city day, even assuming you sleep in places with Wi-Fi. If you're camping or staying nights in rural areas without decent connection, add another 30%, because backups and downloads will accumulate until you find a network. A two-week road trip through the West Coast comfortably reaches 12-15 GB of actual consumption.
The table: GB by profile and duration
This is the table you came looking for. Find your profile, cross-reference with your days, and you'll have the number. These are recommendations with a reasonable margin, not absolute limits.
| Travel Profile | 5 days | 10 days | 15 days | 30 days |
|---|---|---|---|---|
| Tourist with maps and WhatsApp (city) | 1 GB | 3 GB | 3 GB | 5 GB |
| Photos and social media (city) | 3 GB | 5 GB | 10 GB | 20 GB |
| Classic road trip (car, maps, and music) | 5 GB | 10 GB | 15 GB | 30 GB |
| Digital nomad / telework | 10 GB | 20 GB | 30 GB | unlimited |
| Family sharing one line | 10 GB | 20 GB | 20 GB | unlimited |
Three honest nuances about this table. First: if your trip mixes city and road—the typical, New York for four days and then a car trip—choose the road trip profile and don't overthink it, because the city days will give you leftover gigabytes that compensate for the road days.
Second: in the family and nomad rows, the jump to "unlimited" is not just marketing. Sharing a connection with three phones for a month, or making work video calls from an Airbnb with bad Wi-Fi, can easily consume 30 GB.
Third: if you're between two packages, choose the smaller one. Seriously. It's the advice I give most often and the one people believe least until they come back from their trip with half the package untouched.
My rule: look at your actual daily consumption at home, subtract what you'd do over Wi-Fi, multiply by the number of travel days, and add a 30% buffer. If the result falls between two packages, always choose the smaller one. Topping up takes a minute; you can't return gigabytes.
National parks: where you'll use nothing
National parks are the big exception of the American trip: these are the days you'll use the least data, precisely because there's no coverage to use. The problem isn't consumption, it's arriving without having prepared your phone.
| Area | Approximate coverage | What to download |
|---|---|---|
| Yellowstone | Only in core areas (Old Faithful, Canyon, Grant, Mammoth); none in Hayden and Lamar Valley | Offline map of the entire park |
| Death Valley | Practically none outside Furnace Creek | Map and complete route before entering |
| Zion, Bryce, Arches (Utah) | Acceptable at visitor centers and access points; drops in canyons and trails | Map of the area and saved tickets or reservations |
| Grand Canyon (South Rim) | Coverage in the Village, spotty at viewpoints | Map and shuttle schedules |
| Roads between parks | Long stretches without signal, especially in Nevada, Utah, and Wyoming | Downloaded music and podcasts |
Actual coverage depends on the carrier and the exact area, so take this as guidance, not a guarantee. The important thing is the habit: the night before, with hotel Wi-Fi, download the map of the next day's area. Google Maps allows you to save entire areas, and navigation still works without a network.
And yes, this means your park days will consume almost nothing. Count that when you do your calculation: a fifteen-day itinerary with six national park days consumes as much as a nine-day one. This is one reason why many people buy twice as much as they need for this destination.
How to know how much you use
All of the above are averages. Your actual number is in your pocket, free, and in thirty seconds. It's the most honest method I know for choosing the right package.
On iPhone: Settings, Mobile Data, and scroll down to see current period usage and per-app breakdown. On Android: Settings, Network & Internet, Data usage, and there you have the monthly cycle with details. Look at the full month and divide by 30. That's your daily consumption outside the home.
Now adjust with two corrections. First: on your trip, you'll use more maps, more searches, and more photos than in your routine. Second: in the United States, you'll have more Wi-Fi available than you probably have in your daily life on the street. The two corrections balance each other out quite well, so your monthly average divided by 30 is usually a surprisingly good starting point.
An extra tip: reset your counter just before a normal weekend and see how much you use in two days out and about. Multiply by the number of travel days, and you'll have an estimate calibrated to your habits, not the average.
If that exercise shows you use 200 MB per day, don't buy 20 GB just because the trip is "important." Buy 5 GB and enjoy. Data doesn't expire better just because there's more of it.
How to stretch your data on the road
With four adjustments made before leaving home, a road trip through the United States will use half the data. None of them will detract from your trip.
- Offline maps. In Google Maps, search for the city or area, tap on the name, and choose "Download offline map." Step-by-step navigation will still work. You go from 10 MB per hour to practically zero.
- Downloaded music and podcasts. The biggest savings on a road trip. Spotify, Apple Music, and YouTube Music allow you to save entire playlists using hotel Wi-Fi. Four hours in the car go from 160 MB to zero.
- Backups only over Wi-Fi. On iPhone: Settings, your name, iCloud, Photos, and disable mobile data upload. On Android, do the same from Google Photos. This alone is the difference between 3 GB and 10 GB on a photo-heavy trip.
- Disable auto-play. Instagram, TikTok, and X play videos just by scrolling past them. In each app's settings, you can limit this to Wi-Fi.
- Data saver mode. This is in your system settings and in major apps. It lowers video quality and curbs background activity.
I have a longer list, with step-by-step instructions for each app, in the tips for saving data while traveling. If you only do two things, make them offline maps and downloaded music: together, they will save you more than half of your road trip consumption.
If you run short (and why that's okay)
Let's talk about what almost no one tells you when they try to sell you the big package: running short is not a drama. When you run out of data, the connection simply stops working; you're not charged extra or blocked. You'll still have Wi-Fi at the hotel, cafe, and mall, and from there you can top up in a couple of minutes.
Overbuying, on the other hand, does have a cost: you've paid for gigabytes you'll never use. And in a destination like the United States, where Wi-Fi is so widespread and park days consume nothing, overbuying is the easiest thing in the world.
That's why the correct order is: buy the package that your calculation suggests, review your consumption on the third or fourth day—when you have a real average for the trip—and then decide. If you're at 40% with a third of the trip done, you're perfect. If you're at 70%, top up and you're good to go.
This works because the eSIM for the United States is managed entirely from your phone: you see your usage, add data, and it activates instantly, without going to a store or changing anything physical on your phone. It's the opposite of the prepaid SIM you buy at the airport, where you're stuck with what it came with.
Frequently asked questions
How many GB do I need for 15 days in the United States?
Between 3 and 15 GB depending on the trip: 3 GB if it's a city with hotel Wi-Fi, 10 GB if you mix city and photos, 15 GB if it's a road trip. Fifteen days is the most common duration and also the one with the most variation, as it often mixes a city week with a road trip week. If the itinerary includes several national parks, aim for less: those days use almost no data.
Is 5 GB enough for a West Coast road trip?
For one week, yes; for two, it's just enough. A road day averages around 0.9 GB of actual usage, so 5 GB is enough for about five or six days of intense driving. If you download music and maps before you leave, those same 5 GB can stretch up to ten days without a problem. Without prior downloads, they'll be gone in five.
Does Google Maps use a lot of data in the United States?
No: between 5 and 10 MB per hour navigating, and less than 1 MB if you have the map downloaded. It's the most common and most false myth. Five hours of navigation use the same amount of data as one minute of video on Instagram. The problem with road trips is never maps, but streaming music and the co-pilot's scrolling.
Can I share data with my family?
Yes, by tethering from one phone, and it's the cheapest way to connect four people. A single 20 GB package is better than four 5 GB packages. However, the phone sharing the connection uses a lot of battery: carry a car charger and activate it only when you really need it, not all day.
Is there free Wi-Fi in the United States?
Plenty, and it's the main reason you need fewer GB than you think. Starbucks offers it in all its own cafes, as do Dunkin', Panera, McDonald's, Target, Walmart, shopping malls, public libraries, and practically all hotels and motels. In the city, you can spend half a day connected without using a single megabyte.
What happens if I run out of data halfway through my trip?
Nothing serious: the connection stops, and you can top up from any Wi-Fi in a couple of minutes. There are no surprise charges or penalties. That's why I recommend buying just enough and topping up if necessary, instead of buying too much "just in case." Check your usage around the third day of your trip, and you'll know if you have enough.
Do I need unlimited data for the United States?
Only if you work remotely, make daily video calls, or are sharing a connection for more than three weeks. For a normal tourist trip, it's a waste of money. A one-hour work video call uses 1 GB; then it makes sense. For taking photos, finding restaurants, and browsing, a fixed package is much better. If you still have doubts about how the format works, I explain it in what an eSIM is.
Conclusion
In short, without embellishments: if your trip is to a city, 3 GB for ten days is more than enough. If it's a road trip, count on 10 GB for ten days or 15 GB for two weeks. If you work remotely or are sharing a connection with family, 20 GB. Everything else is fine-tuning based on that.
And the two things that really move the needle in the United States: download maps and music before each leg of your road trip, and turn off automatic backups over mobile data. With that, the small package will be enough, and you'll travel more peacefully in parks, where you won't have signal even if you wanted it.
Once you're clear, choose your size for the US eSIM and install it before you leave home: you land at JFK or LAX and have internet as soon as you turn on your phone, without looking for a store or waiting in line. And if you run short, you can top up from your phone in two minutes. Have a good trip.
