Does Gmail Remove EXIF Data? What Photo Attachments Keep

Treat Gmail photo attachments as capable of carrying EXIF, including GPS, camera details, capture time and author fields. Google’s attachment help does not promise metadata removal. Inspect and clean the file before sending when those details should stay private.

A downloadable attachment can expose fields that a small email preview never shows. That matters when a recipient needs an original photograph: you should decide which embedded information is intended to travel with it.

The sending route still matters. A photo added with the paperclip is not quite the same workflow as an image pasted into the message, shared from Google Photos, or replaced with a Drive link. Check the exact file you plan to send instead of trusting the Gmail preview.

Does Gmail remove EXIF from photo attachments?

Google’s attachment documentation explains file attachments and the switch to Drive links above the size limit. It does not provide an EXIF-cleaning promise. This guide therefore recommends treating the supplied file’s metadata as potentially available to the recipient, rather than claiming a universal byte-for-byte delivery guarantee.

Check two files to answer for your route: the exact file supplied to the composer and the attachment saved by the recipient. This is an inspection procedure, not a claim that we sent a test email or measured every Gmail client.

Sending route	What the recipient gets	Metadata expectation
Paperclip file attachment	A downloadable image file	Treat existing EXIF as potentially available; inspect the saved copy
Image pasted into the message	An inline image whose bytes depend on the source and compose route	Placement does not prove cleanup; inspect the saved file
Photo shared through another app or Google Photos	A copy or link prepared by that service	Depends on the route chosen before Gmail opens
File over Gmail’s attachment limit	A Google Drive link	The hosted file follows Drive sharing behavior

Does pasting a photo into Gmail change the answer?

Inline placement alone does not answer the metadata question. A pasted image may originate from a different copy, especially when another app prepares it first.

Gmail can display an image inside the message body while still storing it as a MIME attachment. The visual placement does not prove the file was cleaned. Copy and paste, a mobile share sheet, or an image editor may create a new file before Gmail receives it, and that new file can have different metadata.

If privacy matters, do not infer anything from how the compose window looks. Send a harmless test image through the same app and route, download it from the receiving account, and inspect the result. The WhatsApp EXIF guide explains why a route that creates a new photo copy can behave differently from sending an original file.

Why does a downloaded photo show a new created date?

The new date usually records when the recipient saved the attachment, not when the camera took the picture.

Compare the file contents separately from the operating system’s creation date. If the source and received copy have matching SHA-256 hashes, they contain the same bytes even when their local file-system dates differ. This is a check you can perform, not a result measured for this article.

Look for DateTimeOriginal, CreateDate, or other EXIF fields inside the image. Those can still show the old capture time. File Explorer or Finder may show today’s date because today’s copy is new on that device. Both dates can be correct descriptions of different events.

Can a Gmail recipient recover the original date or GPS?

Yes. If the attachment contains EXIF dates or coordinates, the recipient can read them after downloading the image.

Search the downloaded image for capture-time and GPS fields. If they are present, a recipient can read them; if they are absent, a metadata viewer cannot recreate the missing values from the email preview.

The recipient does not need access to your Gmail account or a specialist lab. Common photo apps and metadata readers can expose GPS, camera details, and capture dates. A missing field also proves very little: the camera may never have written it, or another app may have removed it before Gmail received the file.

What happens when someone forwards the email?

The metadata can travel again if the forwarded message carries the same attachment.

Forwarding does not turn the photo into a social media preview. The next recipient may receive the attached bytes that were already in the message. Downloading, renaming, and attaching the file to a fresh email also leaves EXIF alone unless an editor or cleanup tool rewrites it.

A workplace photo may pass through several inboxes. Cleaning the outgoing file first reduces the embedded information available in copies sent onward. Review the filename and the message text separately.

What happens to photos larger than 25 MB?

Personal Gmail accounts use a Google Drive link when the total attachment size exceeds 25 MB, so the message no longer contains a normal attachment.

Google’s Gmail attachment help documents the 25 MB personal-account limit and says larger files are replaced with a Drive link. Work and school limits can be set by an administrator.

A Drive link changes access and storage, not the metadata inside the hosted image. The recipient may still download the original file from Drive. Check the sharing permissions as well as the photo itself, since anyone granted access can potentially retrieve the embedded EXIF.

How do you check the file a Gmail recipient gets?

Download the attachment from a receiving account and compare that copy with the file you sent.

Open both in the Image Metadata Viewer and compare the SHA-256 value, file size, dimensions, MIME type, and metadata fields. Matching hashes mean the bytes match. Different hashes mean some step changed the file, so inspect the differences rather than assuming the change improved privacy.

The Image Privacy Checker gives a shorter view of GPS, names, device IDs, editing history, and embedded previews. Use an ordinary test photo for route testing. Sending a genuinely sensitive original to yourself still gives Gmail that original.

Attachment privacy and message privacy are separate

The attachment contains one set of records; the email contains another. Clearing image GPS or an author tag does not change the sender address, recipients, subject, message time or quoted conversation. Review both before sending a sensitive attachment.

In the compose window, confirm that the attachment is the cleaned filename you intended. A thumbnail is insufficient because the original and cleaned image can look the same. When using a Drive link, check access permissions as well as the hosted file. Neither an inline preview nor a new download date proves that embedded fields were removed. Google documents attachment handling, not a permanent field-by-field metadata-retention or removal guarantee.

Should you remove metadata before attaching a photo?

Yes, when the recipient does not need the capture details or the image could expose a person or place.

Use the Image Metadata Remover to create a separate cleaned copy and verify it before you compose the email. Keep the original in your own archive. Attach only the cleaned copy.

Do not stop at EXIF if the stakes are high. A filename can contain a client name or address, and the pixels can show mail labels, house numbers, reflections, faces, or a computer screen. Gmail cannot decide whether those visible details are safe for you.