You come back from three weeks in Southeast Asia with 2,400 photos and 60 GB of storage gone. Your phone nags you daily. The blog post you wanted to publish from a guesthouse in Ubud is still sitting in drafts because the café wifi gave up halfway through the third upload.
Every traveller who takes photos seriously runs into this. The fix isn’t shooting less or buying more cloud storage — it’s understanding that most of the weight in your photos is invisible, and learning to strip it out before you upload.
Why travel photos are so heavy
A current phone shoots at 48 megapixels. A single frame lands somewhere between 4 and 12 MB, and if you shoot in RAW or ProRAW it can be 25 MB or more. That’s wonderful if you’re printing a temple sunrise at poster size. It’s absurd for a photo that will be viewed on a 6-inch screen.
The problem gets worse on the road, where you’re rarely on good wifi. Hotel connections in remote places are shared between thirty guests. Café wifi in a beach town drops every few minutes. Mobile data on a local SIM is often capped. Uploading ten 8 MB photos over a connection like that can take twenty minutes and fail twice.
A properly compressed version of the same photo is typically 300–600 KB and looks identical on any screen. That’s the entire trick.
Formats: what to use and when
HEIC — if you shoot on an iPhone, this is probably what you have. It’s efficient, but it travels badly. Most blog platforms reject it, many Windows laptops can’t open it, and the fellow traveller you met in a hostel probably can’t view the photos you AirDropped them. Convert to JPG before sharing or uploading — it’s the single most common headache in travel photography, and it takes seconds to avoid.
JPG — the universal option. Every platform, every device, every browser. Use it for anything you’re sending to another person or uploading somewhere unfamiliar.
WebP — for your own blog. Typically 25–35% smaller than a JPG at the same visual quality, and supported by every current browser. If your posts are image-heavy — and travel posts always are — this alone can halve your page weight.
AVIF — newer, often around half the size of a JPG. Excellent if your audience is on modern devices.
PNG — keep this for screenshots: metro maps, booking confirmations, currency conversion tables, anything with text or sharp lines. PNG keeps text crisp where JPG would smear it. Just don’t use it for photographs — it can produce files five times larger for no visible benefit.
Compressing without visible loss
The instinct is to protect quality by never touching the original. In practice, two adjustments cut file size dramatically without any visible change:
Resize first. If your blog displays photos 1200 pixels wide, a 6000-pixel original is 25 times more data than the page can show. Resizing to roughly twice your display width — 2000–2400 pixels — is plenty, even for high-resolution screens.
Then compress to around 80% quality. Going from 100% to 80% typically removes more than half the file size while producing a difference invisible on screen. Push below 60% and it starts to show, first in skies and gradients — a sunset over Krabi is exactly where over-compression becomes obvious.
Two habits worth building: keep your untouched originals in a separate folder (compress copies, never the master), and compress once rather than repeatedly re-saving the same JPG, since each re-save loses a little more detail.
When you’re on the road with only a phone or a borrowed laptop, browser-based tools are far more practical than installing software. Convertorium handles compression and conversion between JPG, PNG, WebP, AVIF, and HEIC for free without an account, and processes files in the browser rather than uploading them to a server — which matters when you’re on public café wifi and would rather your photos not travel further than they need to.
Handling a whole trip’s worth of photos
The moment that defeats most people is coming home to a card with 2,000 images. A routine helps:
- Cull hard, and cull first. Most of those 2,000 are near-duplicates — eight versions of the same beach. Keep the best one. Deleting ruthlessly before you process anything saves more time than any tool.
- Back up the originals to an external drive or cloud folder before you touch anything.
- Convert HEIC to JPG in one batch if you shot on an iPhone.
- Resize and compress the ones you’ll actually publish or share. There’s no point processing photos that will only ever live in your archive.
- Convert blog images to WebP as the last step, once you know which ones made the cut.
Doing this in batches rather than photo by photo turns an evening’s work into about twenty minutes.
One more thing: your travel documents
Since we’re on the subject of files — the same logic applies to the paperwork side of a trip, and it’s an underrated bit of preparation.
Instead of hunting through your email for a boarding pass while standing at a check-in desk with bad signal, combine everything into a single offline PDF before you leave: flight confirmations, hotel bookings, visa approval, travel insurance, and a photo of your passport page. Merging them into one file means one tap to open, no signal required, and nothing to search for at the moment you’re most stressed.
If you’ve scanned documents and they came out sideways — as scanned pages almost always do — rotating the pages before you save takes a few seconds and saves real irritation later. And if you only need to send one page from a longer document, splitting out that page range means you’re not forwarding your entire itinerary to a hotel receptionist.
The short version
Shoot at full quality, always. Then, before anything gets uploaded or shared: convert HEIC to JPG, resize to about twice your display width, compress to roughly 80%, and use WebP for your own site. Keep the originals safe and untouched.
It takes a few minutes per post, and it’s the difference between a blog that loads instantly on a phone in a train station and one your readers give up on — and between an evening lost to failed uploads and one spent doing something better with your trip.
