A single day of serious travel photography can produce 20 to 50GB of RAW files and 4K video: more than most monthly mobile data plans are designed to move. That single mismatch, between what a camera writes and what a network carries, is the root problem of every on-the-road photo workflow, and pretending it does not exist is how photographers end up with three months of unbacked-up work on one SD card in one bag.

The professionals who make it work do not have secret bandwidth. They have a workflow that respects the mismatch: shoot everything, cull hard, upload the few files that matter now over whatever connection exists, and let the bulk archive travel on unmetered wifi or physical drives. Data becomes a budget to allocate rather than a wall to hit.

This guide builds that workflow piece by piece: the real numbers on file sizes, the cull-then-upload discipline, cloud backup across hotel wifi and cellular, a data budget for social posting, and the settings that quietly halve your upload volume.

In this guide:

The gap between file sizes and mobile data

Cameras have grown faster than networks in exactly the dimension that hurts travellers: file size. A decade ago a RAW file was 15MB; today a 45MP body writes around 50MB per frame, smartphone 48MP RAW modes can produce files of similar weight, and one minute of high-bitrate 4K video outweighs an entire day of photos from that older camera.

Mobile data, meanwhile, is sold in plans measured in gigabytes per week or month. The arithmetic is unforgiving: a 20GB plan is roughly 400 large RAW files, or under half an hour of 100Mbps 4K footage. Shoot a festival, a wedding or two good street days and you have out-produced the plan.

Upload speed compounds the problem. Networks are engineered for downloads; upload is the narrow lane. A connection advertising fast downloads may offer a fraction of that upstream, and hotel wifi is notorious for single-digit Mbps uploads. At 5Mbps up, a 10GB archive takes around four and a half hours; at 2Mbps, most of a night.

The conclusion is not that mobile uploading is hopeless; it is that undifferentiated uploading is hopeless. Every file needs to be classified: does it need to leave the camera today, this week, or just eventually?

What photo and video files actually weigh

Budgeting starts with knowing the numbers. Sizes vary with compression, scene detail and settings, so treat these as typical 2026 figures rather than gospel.

File typeTypical sizeUpload cost, per 100 files or 10 minutes
Smartphone photo (HEIC)2-4MB0.2-0.4GB per 100
Smartphone RAW (48MP class)25-75MB2.5-7.5GB per 100
Mirrorless JPEG (24MP)8-15MB0.8-1.5GB per 100
RAW, 24MP25-35MB2.5-3.5GB per 100
RAW, 45MP class45-60MB4.5-6GB per 100
Smartphone 4K30 videoaround 170MB per minutearound 1.7GB per 10 min
Mirrorless 4K at 100Mbpsaround 750MB per minutearound 7.5GB per 10 min
ProRes or RAW videomultiple GB per minuteeffectively wifi-only

Two lessons jump out of the table. First, format choice is a 10x lever: the same scene shot as JPEG instead of RAW uploads for a tenth of the data, which is why many photographers shoot RAW plus JPEG and upload only the JPEGs from the road. Second, video is the real budget-killer; a photographer who also shoots reels needs to think in video terms, with photos as a rounding error.

Cull first, upload second

The single highest-leverage habit in a travel workflow is culling before any byte moves. Most shoots follow a brutal ratio: of several hundred frames, perhaps thirty are worth editing and five are worth publishing. Uploading the whole card means paying data costs on the 95 percent you will never touch again.

Make the cull a daily ritual, not a someday task. The same evening, on the camera or a phone or tablet, sweep the day’s take and flag it into three tiers:

  • Selects: the handful of frames that need to reach the cloud, a client or a feed now. Upload these over anything, cellular included.
  • Keepers: solid frames worth archiving. These wait for real wifi or move to a drive.
  • The rest: out-of-focus, duplicates, misfires. Delete or ignore; they never earn upload bandwidth.

Daily culling has a second, underrated payoff: it is when you notice problems. The corrupted card, the back-focus issue, the dust spot on the sensor all surface the same evening rather than three cities later, while the location is still one taxi ride away.

For deadline work, cull one level harder: transfer selects to the phone, edit the best three or five there, and upload finished exports rather than source files. A processed JPEG for delivery is a few MB; the RAW it came from is fifty.

Cloud backup: hotel wifi vs cellular

Treat your two connection types as two different tools rather than one interchangeable internet.

Hotel and accommodation wifi is unmetered but unpredictable. Upload speeds are commonly a small fraction of download, shared with every guest, and worst in the evening when everyone is streaming. Its job is bulk: start the full-archive cloud sync when you go to bed and let it grind all night. Test the upload lane on arrival with a speed test; if the connection cannot manage a couple of Mbps up at midnight, plan around it and treat that stay as an SSD-only stop.

Cellular is metered but consistently better than its reputation, and on modern 4G and 5G networks often dramatically faster than the accommodation lobby. Its job is the urgent small stuff: today’s selects, the client preview gallery, the social post, the one RAW file an editor needs immediately. A prepaid travel eSIM makes this lane cheap to keep open: plans from Viasimo arrive instantly by email and install via QR in minutes, your home SIM stays active alongside, and coverage spans worldwide destinations, so the workflow survives every border on a multi-country shoot. Run your gear through the device compatibility checker before relying on a phone as your upload hub.

The hybrid habit that ties it together: queue everything to your cloud service with cellular sync restricted to selects only, and let the app flush the full queue automatically whenever it sees wifi. Every major photo cloud platform supports some version of this split. Photographers who also work remotely will find the deeper connection playbook in our remote work abroad internet guide.

Build a three tier backup system

Uploads are only half of safety; the classic 3-2-1 backup rule translates cleanly to the road. Three copies of anything that matters, on two different types of storage, with one copy off-site. Travelling, that becomes:

  1. In-camera redundancy. If your body has dual card slots, write to both simultaneously; a card failure then costs nothing. Single-slot shooters should rotate cards daily rather than filling one giant card, capping the blast radius of any failure.
  2. A local copy on different hardware. Each evening, ingest to a portable SSD via a card reader, or to a phone or tablet with enough storage. Crucially, keep this copy in a different bag from the camera; theft takes bags, not files, and two copies in one stolen backpack is one copy.
  3. The off-site copy in the cloud. Selects go up daily over whatever connection exists; the full archive drains upward on good-wifi nights. On a long trip the cloud copy is the only one that survives every physical disaster at once.

The discipline that makes the system real: no card gets formatted until its contents exist in at least two other places, one of them off-site. Write the rule on the card wallet if you have to.

Social posting cadence and data budgets

Creators have a second data stream beyond backup: publishing. It is smaller than most people fear, provided photos and video are budgeted separately.

Photo posting is nearly free. Apps compress on upload, so a daily photo post with stories attached typically consumes well under 100MB a week. No cadence of still photography needs rationing on any sensible plan.

Video is the line item. Uploading a one-minute vertical video commonly costs tens to a few hundred MB depending on export settings, and apps that upload high-quality originals cost more than their defaults. A creator posting one reel daily plus stories should budget several GB a month for publishing alone, before any backup traffic. Batch heavy exports, upload them on wifi where deadlines allow, and save cellular for the posts that are genuinely time-sensitive.

Then add the invisible half: engagement. Scrolling feeds, answering DMs and watching competitors is a browsing workload that runs 1 to 3GB a month at moderate use. Our breakdown of how much data you need for travel covers the general baseline this sits on top of; a photographing creator should sit one plan size above whatever a normal traveller with their itinerary would buy.

Settings and gear that cut upload pain

A handful of one-time decisions permanently shrink the problem:

  • Shoot RAW plus JPEG and make the JPEGs your travel currency: uploads, previews, client galleries. The RAWs ride the SSD home.
  • Use compressed or lossless-compressed RAW where your camera offers it; savings of a third or more per frame, invisible in the edit.
  • Match resolution to purpose. Shooting 4K60 high-bitrate for content that publishes as compressed vertical video pays a storage and upload tax with no visible return. Many working creators shoot social content at settings a tier below their client work.
  • Turn off automatic full-resolution sync on phone photo apps while abroad, or every camera-roll screenshot competes with your selects for bandwidth.
  • Carry the right small hardware: a USB-C card reader, one fast portable SSD per month of trip as a rule of thumb, and a power bank, because ingest and upload sessions drain phones fast.

If a connection problem does strike mid-deadline, work the layers in order: toggle aeroplane mode, retry on the other line, move to where the signal is; and if the eSIM itself misbehaves, support is available 24/7.

Build your upload routine

Everything above compresses into a nightly rhythm that takes twenty minutes: cull the day into selects and keepers, push selects to the cloud over the best connection available, start the archive sync if the wifi deserves it, copy the card to the SSD, and charge everything for tomorrow.

Set it up before the trip: cloud plan with enough headroom, sync app configured for the selects-only cellular split, SSD tested, and a travel eSIM installed on home wifi so the cellular lane works from the first shot at the first location. Photographers on multi-month projects should pair this workflow with the plan-buying strategy in our long-term travel connectivity guide; the shooting does not stop at a border, and neither should the uploads.