She wanted to print it. A4, framed, the whole thing. I took the photo on my Pixel, it looked incredible on screen — sharp, warm, exactly the moment. She took it to a print shop. The person behind the counter told her the resolution was too low to print at A4 without it looking blurry.

I had sent a 12-megapixel original. What arrived on my mum's phone was a 2-megapixel JPEG. WhatsApp had compressed it to roughly 1/6th of the original quality during the transfer. The moment was still there but the detail was gone, permanently, and neither of us had any idea it had happened.

That was the thing that made me actually sit down and figure out how file transfer works — and why the tools most of us use by default are genuinely bad at the one job we use them for.

The Problem With WhatsApp (And Every Messaging App)

WhatsApp processes billions of file transfers every day. At that scale, storing and serving original-quality files would cost an enormous amount of money. So they compress. Images get reduced to approximately 1600×1200 pixels. Videos get re-encoded to 720p at less than 1 Mbps bitrate. The compression is aggressive and it is invisible — you cannot see it happening, the recipient has no idea the file they received is a degraded copy, and there is no warning that says "hey, we destroyed your photo on the way."

Instagram does the same. Telegram does the same when you send photos (not files). Facebook Messenger does the same.

There is a WhatsApp workaround — sending as a Document instead of a photo bypasses the compression. Tap the paperclip, choose Document, navigate to the photo file. It sends the original. But it is buried in a submenu, it is not obvious, and most people never find it. Including me, for years.

The Problem With Google Drive

After the wedding photo incident I switched to sharing everything via Google Drive links. Problem solved, right?

Not really.

First: I did not realise how much storage I was using. Google's free tier is 15GB shared across Drive, Gmail, and Photos. After two years of "temporary" file shares — client work, family photos, documents from jobs I no longer have — I hit the limit and had to pay for storage. For files that were never meant to be stored permanently. I was paying a monthly subscription to store a graveyard of one-time transfers.

Second: the links never expire. A Drive link I shared with a colleague in 2022 still works in 2026. If that person forwarded it to someone else, or if it ended up in a Slack channel with wider membership than I intended, or if it got picked up by anyone who had access to that email thread — the file is still there, still accessible. I checked recently. There were 47 Drive links I had shared over three years that still had "Anyone with the link can view" enabled. I had completely forgotten about most of them.

Third: Google scans everything you upload to Drive. It is in the Terms of Service. For most files this probably doesn't matter. For anything with any professional sensitivity — client work, financial documents, anything with personal information — putting it in Google's content analysis pipeline is not something I would have chosen if I had thought about it deliberately.

What I Actually Use Now

I spent a few weeks genuinely researching this after the wedding photo situation. Here is the workflow I landed on.

For sending files to someone who is online right now: I use Zapfile. It is browser-based — no app, no account on either end. Open the site, drop the file, copy the link, send it. The person opens the link and downloads. The file transfers directly between our browsers as encrypted packets. Nothing is stored on any server. The link dies when I close my tab.

The quality thing is what sold me. A 24-megapixel photo sent via Zapfile arrives as a 24-megapixel photo. Same file size. Same format. Because there is no server in the middle making decisions about what quality is "good enough," the file just goes from me to them untouched.

There is no file size limit from the service. I have sent 3GB video files through it. The only limit is your connection speed, which is also the limit for every other method — you just feel it more because cloud transfer has the same speed limit for the upload and then adds a second trip for the download.

The Thing Nobody Tells You About File Transfer

The default tools — WhatsApp, Google Drive, email — were not designed for point-to-point file delivery. They were designed for messaging, storage, and communication respectively. File sharing got bolted on as a feature. The limitations you bump into (compression, size limits, permanent storage, account requirements) are consequences of using tools for a job they weren't built for.

Purpose-built transfer tools don't have these problems because they started from a different design brief. The brief was: move this file from here to there, at original quality, with as little friction as possible, without leaving a copy anywhere that doesn't need one.

That is a solved problem in 2026. Most people just haven't updated their defaults since 2015.

The Specific Things I Changed

• Stopped sending photos via WhatsApp media. Use Zapfile for photos I care about, WhatsApp Document method as a fallback.
• Stopped using Google Drive for one-time delivery. Drive is for files that need to live somewhere and be accessed repeatedly. Not for "here is your invoice."
• Audited and revoked all my old Drive sharing links. Took about 20 minutes. Should do it every 6 months.

None of this required new accounts, new subscriptions, or significant behaviour change. It just required knowing that better tools existed and that the defaults I had been using were actively making things worse in ways I hadn't noticed until a print shop told me my sister's wedding photo was too low resolution to print.

If you want to try the browser-based transfer method: zapfile.ai — no account needed on either end.