MetaPurge

Email and cloud photo metadata: attachments versus shared links

Email and cloud drives are file transport. They move the bytes you gave them, so the EXIF goes with them. Photo services are something else: they store a photo and hand out rendered copies.

By Rajat Malik Updated 6 min read

A photo can reach another person in two structurally different ways. Either a file is copied and delivered, or a service holds the photo and shows it to them. The first keeps everything. The second usually builds a new, smaller copy for display, which changes the metadata without anyone deciding to.

Most confusion about "the cloud" comes from mixing those two. A Drive link and a Google Photos share link look similar in a chat, and behave very differently underneath.

Two things people call sending a photo

RouteWhat arrives at the other endMetadata
Email attachment The file you attached, unless the provider rejects or rewrites it Intact
Drive link to a file (Drive, Dropbox, OneDrive, iCloud Drive) The stored file, downloaded as stored Intact
Google Photos share link A rendered copy at viewing size, not the original upload Capture date usually kept; GPS usually not
Google Photos download Can be the original or a re-encoded copy depending on the path Verify rather than assume
iCloud Photos shared album A reduced-size copy delivered to album viewers Most camera tags absent
iCloud Photos original on a signed-in device The original file, synced Intact

Email attachments pass the file through

An attachment is bytes in a message. Gmail, Outlook and the rest encode it for transport and decode it at the other end, but the file that lands in the recipient's downloads is the file you attached. Nothing in that process decodes your JPEG and re-encodes it, so the EXIF block arrives as it left.

There are exceptions worth knowing. Providers scan attachments, may block certain types, and impose size limits. Some corporate gateways rewrite or strip attachments. None of that is a privacy feature you can rely on; it is policy and plumbing that varies by organisation.

Email also adds a second layer of metadata outside the file: the message headers. From, To, timestamps and the routing chain are recorded on every message, and they say more about when and how you sent something than your photo ever will. Cleaning the image does not clean the envelope.

Cloud drives store the file

Drive, Dropbox, OneDrive and iCloud Drive are synchronisation products. Their job is to keep an identical file in several places, which means they cannot quietly rebuild your JPEG — a re-encode would break the promise that the file is the same everywhere.

So the original survives: GPS, serials, timestamps, edit history. So do the previews, which are generated separately for the web interface and are not what you download. A shared folder inherits the metadata state of every file inside it, including files other people added.

A share link is a permission, not a transformation Sharing a Drive folder changes who can reach the file. It does not change the file. If the folder contains an uncleaned photo, the new viewer can download it in full.

Photo services are not drives

Google Photos and iCloud Photos are built around a library view: a timeline, albums, faces, places. They store your upload and serve it at whatever size a screen needs. That makes them more like a social platform than a folder, and their share paths behave accordingly.

As of writing, a Google Photos share link typically serves a rendered copy rather than your original file, and iCloud shared albums deliver reduced-size copies to viewers. In both cases the capture date tends to survive, because the timeline and album ordering depend on it. GPS and camera details are the parts most likely to be dropped.

The original remains in your library. That is the important asymmetry: the service has a copy with everything, and the person you shared with has a copy with less. Downloading your own upload is a separate path again, and can return either the original or an edited copy depending on how you ask for it. Test the specific route you use rather than trusting a general rule.

This is the distinction that resolves most of the confusion. A synced file is the same object on two devices. A shared link is a URL that renders an object for someone who does not have it. The first preserves metadata because preservation is the point. The second can resize, strip and re-encode because display is the point.

Practically: if the recipient downloads a file, assume the metadata travelled. If the recipient opens a page and looks at a picture, assume the platform decided what to include — and assume the original is still whole wherever it is stored.

Neither case is a reason to relax. A rendered copy still shows the scene, and a downloaded file can be forwarded anywhere. The platform's choice to drop a field is not your control over it.

Why the attachment is the leak path

The attachment is the route where nothing gets removed by accident. That is what makes it useful and what makes it dangerous. A photo of a document, a room, a child, a parked car, sent to a client or a buyer, arrives with the coordinates of where it was taken and the device that took it.

The same file usually exists in a synced folder or a cloud backup, so the leak is duplicated before anyone opens it. And because email is forwarded, the recipient's copy becomes the sender's problem in a way that a rendered link is not.

Keep the convenience, drop the fields

Clean the file once, at the point it leaves your camera roll, and every route downstream inherits the clean version: attachments, drive sync, shared folders, backups. Keep Orientation and the ICC profile so the image still displays correctly, and remove the location, device and history fields.

If a platform offers a share link and you only need the picture to be seen, either path is fine once the source is clean. If you need the file itself, send the cleaned original. Both choices become simple when the metadata is not there to begin with.

See what your photos are carrying

Drop an image in. MetaPurge lists every tag, then rewrites the file without touching a pixel.

Open the metadata remover

Where to go next

Rajat Malik Frontend architect and the author of MetaPurge. Builds browser tools that keep files on the device, and writes about the parts of the web that leak by default. rajatmalik.dev