How to share photos without losing quality

You send a set of photos, and what arrives is softer, smaller and somehow greyer than what left. Nothing was corrupted — something along the way decided the pictures were too big and helpfully fixed it for you.

Here is where quality actually goes, and how to hand over photographs that are the same file you started with.

Who is shrinking your photos

Almost every convenient channel re-encodes images on the way through, because it is cheaper for them and invisible to most users.

• Messaging apps are the worst offenders. Sending a photo through most chat apps re-compresses it hard — a 6 MB image can arrive at a few hundred kilobytes. Many offer a "send as file" or "original quality" option; without it you are sending a thumbnail with ambitions.
• Social platforms re-encode everything on upload, and downloading from them gives you their version, never yours.
• Some email clients offer to "reduce image size" when attaching, and the offer is easy to accept without reading.
• Screenshots and AirDrop-to-a-different-format quietly convert HEIC to JPEG, which is another generation of loss.

Each pass through a lossy codec throws away detail permanently. Two or three re-encodes is the difference between a print-worthy file and something that looks acceptable only on a phone.

The rule: transfer, do not process

The fix is not a clever setting. It is choosing a channel that treats your photograph as a file to move rather than an image to display.

Anything that shows a preview, generates thumbnails, or offers to optimise is in the business of processing images. A transfer service that moves bytes gives back the same bytes, checksum for checksum. That is the whole trick.

If a service can show your client a nice gallery of the photos, it has decoded and re-encoded them to do it.

Sending the originals

Send RAW when the recipient is editing. A retoucher, a colourist, or anyone grading needs the latitude that only the original sensor data has. RAW files are large — 25-50 MB each is normal, more on a high-resolution body — and that size is the point.

Send full-quality JPEG or HEIC when the recipient is using, not editing. A client picking selects, a designer placing images in a layout, a publication that will do its own export. Straight out of the camera or exported at maximum quality, with no resizing.

Keep the folder structure. For a shoot, send the folders as they are rather than flattening several hundred files into one directory. If you need one archive to preserve that structure, zip it — for organisation, not for size, since a zip of JPEGs saves very little.

Metadata: keep it or strip it, but decide

Photographs carry more than pixels. EXIF holds camera, lens, settings and often GPS coordinates; IPTC holds captions, copyright and credit.

For professional delivery, keep it — the copyright and credit fields are how authorship travels with the file, and the technical data is genuinely useful to whoever works on it next.

For anything personal being sent to someone you do not know well, consider stripping location. A photo taken at home carries the coordinates of your home, and most people have no idea it is there.

Note that re-encoding through a messaging app usually strips metadata as a side effect — so the same shortcut that destroys your quality also destroys your copyright fields.

Practicalities for a full shoot

• Do the size arithmetic. 800 RAW files at 40 MB is 32 GB. At a real 20 Mbps upload that is roughly three and a half hours. Start it when you do not need the connection.
• Use a wired connection for anything measured in hours.
• Use a transfer that resumes. With hundreds of files, a tool that restarts the whole batch on a dropped connection is unusable. Chunked uploads mean a blip costs a slice.
• Send selects first. A small transfer of the twenty best images gets the client working while the full set uploads behind it. It also catches "these are the wrong shots" before you have spent three hours.
• Match the expiry to the job — a month for a client working through a set at their own pace, a week for a quick approval.
• Name the transfer after the shoot, not the date. It is what your history will show you in six months.

When smaller is the right answer

Sending originals is not automatically correct. If the recipient is putting the image on a website, a 45 MB RAW is a burden and a 2500px JPEG is exactly what they need. If they are approving a composition, they do not need print resolution.

The mistake is not sending a smaller file. It is sending a smaller file by accident, because a chat app decided for you.

The short version

Pick a channel that moves files rather than displaying them, send the original when the recipient will edit it, export deliberately when they will not, and decide about metadata rather than letting a re-encode decide for you.

Related: how to send large files compares the methods, and why large uploads fail covers the practical side of moving a whole shoot.