How to send photos without losing quality.

The photo that leaves your computer and the photo that reaches the other person are often two different files. Somewhere in between, an app decided your image should be smaller, faster, and worse. If you have ever zoomed into a photo a friend sent back to you and winced, you have seen it. Sending at full quality is not hard, but it means knowing which routes touch your pixels and which ones leave them alone.

Which sending routes touch your pixels

Sort every way of sending a photo into two buckets: routes that treat it as a file, and routes that treat it as a picture. File routes move bytes and change nothing. Picture routes optimize for the screen on the other end, which means resizing and re-encoding.

Picture routes, the ones that cost you quality: text messages once they fall back to MMS, WhatsApp and Messenger by default, Instagram and every social platform, and many webmail clients that offer to resize on attach. Some of these can behave when asked, WhatsApp can send as a document for instance, but their defaults work against you.

File routes, the safe ones: email attachments sent as actual attachments, AirDrop between Apple devices, cloud drive shares of the original file, and transfer links. A transfer service is a file route by construction: it stores what you upload and serves the same bytes back, because rewriting customer files would be a liability, not a feature.

The rule that follows: any time a photo matters, choose a file route on purpose rather than letting the conversation choose a picture route for you.

Start with a file worth protecting

No sending route can restore quality that was gone at export. Before blaming the pipe, check what you put into it.

• Resolution. Export at the size the use calls for. For printing and archiving, full resolution. A long edge of 2048 pixels is a social size, not a delivery size.
• JPEG quality. The quality slider matters far more than most photographers think below 80. Between 85 and 100 the differences are subtle and the files grow fast, which is why many working photographers settle in that range for client work.
• Format. JPEG at high quality is still the interoperable choice. HEIC is efficient but not universally readable on the receiving end, and a recipient who cannot open a file will run it through a converter of unknown quality. If HEIC is what you have, convert it yourself with something that does it cleanly, like a HEIC to JPG converter that runs in your browser.

Export once, correctly, and keep that master. Every copy you send should descend from it, not from an earlier send.

Send the file, not a rendering of it

For one or two images to someone nearby, AirDrop or an email attachment does the job. The interesting case is a real delivery: dozens or hundreds of files, someone far away, possibly not technical. That is what transfer links are for.

1. Open Kepla File Transfer in a browser. No account, no installer.
2. Drag the exported folder in. The files are packed into a single ZIP while they upload, and ZIP is lossless: it repacks bytes without touching the image data. Up to 10 GB fits in one transfer.
3. Set the expiry, 1 hour to 3 days, and send the link, or address it to up to 10 people so each gets their own link and you get receipts showing who downloaded.

The recipient clicks, unzips, and holds files identical to your exports. Photo recipients even get a gallery view to browse before downloading, which heads off the person who would otherwise screenshot the preview and call it done.

Prove nothing changed

Quality anxiety ends when you stop guessing. Two checks, one crude and one exact.

The crude check is file size. If you sent 8.4 MB and the recipient holds 8.4 MB, the image almost certainly made it untouched. If they hold 1.1 MB, something along the way re-encoded it, and you know to ask how they saved it.

The exact check is a checksum. On a Mac, Terminal, then shasum -a 256 file.jpg on both copies. On Windows, certutil -hashfile file.jpg SHA256. Matching output means the files are identical to the last bit, which is a sentence you can say to a client with total confidence.

Run the exact check once on each route you rely on, confirm the route is clean, and then stop worrying about it. From there, the only quality conversations left are about what happens after delivery, when the client uploads your work to a social platform. That one you cannot prevent, only soften, by including a folder of social sized copies so the originals never get fed to the compressor.

FAQ