In short: A travel photographer needs an eSIM, primarily for upload volume rather than browsing: RAWs to the cloud, gallery delivery to clients, and agency communication from any destination. With a 20-30 GB plan and good management of Wi-Fi vs. data, work doesn't stop even if the hotel lacks decent coverage.
What a connected travel photographer really needs
When people think about mobile data for travel, they imagine Google Maps, WhatsApp, and Instagram Stories. But for a professional or semi-professional photographer, consumption is different: it's about upload traffic, not download, and that completely changes the calculation. A RAW file from a modern DSLR or mirrorless camera weighs between 20 and 45 MB depending on the sensor; if you work with cRAW or compressed files, it drops to 12-20 MB. Uploading 60 photos from a sunrise session to Lightroom Cloud or Google Drive can be more than 1 GB in a single batch, before even touching any social media.
Added to this is the management aspect: reviewing contracts or agency feedback via email with heavy attachments, sending a selection of 20 photos to a client via WeTransfer from the airport, searching for a location with Google Lens, or checking cloud forecasts for the next day's golden hour. None of this is optional when you're working, and it all depends on having reliable data right when the light is no longer there.
This is where traditional data roaming falls short: your Spanish operator's roaming outside the EU skyrockets in price or is simply not activated by default, and relying on hotel Wi-Fi to upload an entire report is a gamble. A local or regional eSIM fills that gap without having to change physical cards or lose your main number for calls.
How many GB you need depending on your workflow
There's no single figure: it depends on whether you upload only an edited selection or the full raw material, and whether you work solo or coordinate with an agency that requires daily deliveries. The table below is a consumption reference by activity, useful for calculating your plan before traveling.
| Activity | Approximate Data | Typical Frequency |
|---|---|---|
| Upload uncompressed RAWs to cloud | 20-45 MB per photo | End of each session |
| Automatic background backup (JPEG) | 2-6 MB per photo | Continuous while covered |
| Gallery delivery to client (WeTransfer/SmugMug) | 200 MB - 1.5 GB per delivery | 1-2 times per travel week |
| Email and messaging with agencies | 5-50 MB per thread with attachments | Daily |
| Location research / Google Lens | 1-10 MB per query | Several times a day |
| 4K support video (behind the scenes, reels) | ~200-300 MB per minute | Occasional |
With these numbers, a photographer who uploads selected RAWs (not the entire roll) during a one-week trip usually uses between 15 and 25 GB. If you also do automatic backups of everything shot or deliver video, it easily goes up to 30-40 GB. My honest recommendation: overestimate your data needs for your first trip with an eSIM, and if you have data left over, buy less next time. Running out of data on the day of the final delivery is much worse than spending too much.
How to upload photos without losing the light session
The most common mistake is not data-related, but workflow-related. Many photographers wait until they get back to the hotel to upload the day's material, relying on Wi-Fi, and then find themselves with a network shared by 40 guests that can barely support watching a video, let alone uploading 2 GB of RAWs. The eSIM changes the order: you upload at the destination itself, as soon as the session ends, taking advantage of any downtime (the car ride, the museum queue, after-dinner conversation).
RAW, proxy, or JPEG: what to upload immediately and what to wait for
There's no need to upload the full RAW instantly. A strategy that works well on location: as soon as you finish shooting, export a preview JPEG or compressed proxy directly from the camera or mobile (many mirrorless cameras do this via Wi-Fi to the manufacturer's app) and upload it using mobile data so the client or agency has something to see that same day. The heavier full RAW can be saved for when you find a more stable network, or scheduled for overnight upload with your phone plugged in.
Hotel Wi-Fi vs. eSIM data: when to use each
Hotel Wi-Fi is free but unreliable, especially in small or rural accommodations. An eSIM costs money, but you control it: use it as your main network for urgent tasks (deadline deliveries, client communication) and reserve Wi-Fi for large, unhurried uploads, like the full daily dump to a cloud backup. If your phone supports dual eSIM or eSIM plus physical SIM, you can keep your Spanish line active for calls and the data eSIM active in parallel without touching anything.
Apps that demand data, not Wi-Fi
- PhotoPills / The Photographer's Ephemeris: calculate sun, moon, and Milky Way positions; once offline maps are downloaded, they use little data, but initial synchronization in each new destination does consume data.
- Google Lens: identify a monument, a species, or translate a sign on the spot — invaluable when you're photographing something you don't even know the name of.
- Lightroom Mobile / Capture One Cloud: synchronization of edits between camera, mobile, and laptop; consumes little if working with proxies, much if synchronizing full RAWs.
- WeTransfer / SmugMug / Pixieset: delivery of galleries to clients without relying on having a laptop or a specific network.
- Google Photos ("storage saver" quality): low-consumption automatic backup, useful as a safety net although it doesn't replace RAW backup.
If you also have video work or need to access geographically blocked services in certain countries, it's wise to understand how a VPN combined with an eSIM works before you leave, not when you're already there and can't even install it calmly.
What almost no one tells you
Airplane mode with Wi-Fi activated does not free up your mobile data line for incoming VoIP calls from your team. If you need the agency to be able to reach you via WhatsApp while you upload photos over Wi-Fi, don't completely turn off the data SIM; prioritize the eSIM in your phone settings.
Background upload pauses if your phone enters power-saving mode, which is very common in destinations where you spend hours without an outlet. Before leaving your phone uploading a large backup in your backpack, check that the app has permission for background activity and that battery saving is not active.
In areas with a lot of stone or metal — historic centers, kasbahs, cathedral interiors — the signal drops even if the destination generally has good coverage. This is not an eSIM problem, it's physical: if you're going to photograph the interior of a mosque or a crypt, upload the material before entering or right after leaving; don't count on having data inside.
Download offline maps of the specific area where you'll be shooting, not the entire city. On photographic hiking routes (Dolomites, Patagonia, Iceland outside the main ring road), coverage disappears as soon as you leave the urban area, and you need the map to reach the light spot without relying on data you won't have.
A little-known trick: some cloud apps allow limiting uploads to Wi-Fi networks by default. Check this setting before installing the eSIM: if Lightroom or Google Photos are configured for "Wi-Fi only," you'll be paying for data and nothing will upload until you manually activate mobile data upload.
Common photographic destinations and their real coverage
General mobile coverage is not the same as coverage at the exact point where you will be photographing. This table is an indicative reference by destination, but the criterion of "plan uploads in the base city, not in the remote spot" applies to all of them.
| Destination | Common Photographic Challenge | Coverage Note |
|---|---|---|
| Iceland | Northern Lights, volcanic landscapes | Good on ring road, drops in interior areas |
| Japan (Kyoto, Tokyo) | Temples, cherry blossoms, urban architecture | Very good in cities, uploads via local infrastructure |
| Morocco (Sahara, medinas) | Dunes, kasbahs, narrow alleys | Drops inside covered medinas and in the deep desert |
| Dolomites, Italy | High-altitude routes, lakes, refuge sunrises | Good in valleys, irregular in high hiking areas |
| Patagonia (Chile/Argentina) | Glaciers, Torres del Paine, multi-day trekking | Solid in access towns, none on long trekking sections |
If your route covers several countries in the same trip — for example, a European tour combining the Dolomites with other stops — check if a regional plan is more advantageous than buying country by country; for Europe specifically, you can review the eSIM data for Europe before fragmenting your trip into several purchases. And if the destination is a country where we already cover the route with a specific guide, such as Peru and Machu Picchu or Seoul and Busan, you'll find detailed coverage by area that cannot be included here.
When you DON'T need to buy an extra eSIM
Let's be honest: if you're photographing for a weekend in another Spanish city, or your operator already includes decent roaming within the EU, you don't need anything additional — your Spanish plan already covers you, and buying an eSIM would be an unnecessary expense. It also doesn't make sense if your workflow is 100% offline: you shoot, edit at night with your laptop, and don't upload anything until you get home. In that case, a few GB of backup for maps and basic communication are more than enough, not a plan designed for daily RAW uploads.
Where it does make a difference is on trips outside the EU with daily deliveries or communication involved: agency reports, weddings or events at the destination, any work where the client expects to see something that very day. In these cases, the cost of the eSIM is insignificant compared to the cost of losing a client by not being able to deliver on time.
Frequently asked questions
How many GB does a professional travel photographer need?
It depends on whether you upload an edited selection or the entire roll. As a guideline, between 15 and 25 GB covers a week of daily RAW selection uploads; if you also do automatic backups of all material or deliver video, 30-40 GB is more realistic.
Is 4G speed sufficient for uploading RAWs to the cloud?
In most destinations with reasonable 4G coverage, yes: a 25-30 MB RAW can be uploaded in a few seconds with a good signal. The bottleneck is usually not network speed but rather saturation peaks in very touristy areas at certain times.
Does an eSIM work in remote destinations like the Sahara Desert or the glaciers of Patagonia?
In access cities and towns, usually yes. In truly remote areas — deep desert, glaciers, multi-day trekking routes — coverage can be nonexistent regardless of the operator. Plan your uploads for when you are at base, not at the most isolated point of the route.
Can I make video calls with clients or agencies from my destination?
With 4G available, yes, although quality depends on the actual speed of the local network, which varies greatly from one area to another. In rural areas with only 2G/3G, a voice call or audio message is usually more reliable than a video call.
Do I need a different eSIM for each country if my route crosses borders?
Not always. If your itinerary moves within the same region, a regional plan might be simpler than buying an eSIM country by country; it's worth comparing before fragmenting the purchase into several cards.
Does the eSIM work with gallery delivery apps like SmugMug or WeTransfer?
Yes. Any app that works with an internet connection works the same with eSIM data as with Wi-Fi; there are no specific restrictions based on the connection type.
How do I avoid running out of data on the final delivery day?
Overestimate your needs from the first trip: it's better to have some GB left over than to be stranded on the day the client expects the gallery. If your plan allows, leave some margin or review in advance how to save data when traveling to stretch what you have without stopping important uploads.
