TL;DR: No — and unlike Slack and Microsoft Teams, Zoom has never announced any metadata scrubbing for shared images. As of July 2026 there is no Zoom feature, setting or release note describing EXIF removal in Team Chat or in-meeting chat. Zoom's file sharing is a literal file transfer: recipients download the file you attached, byte-for-byte, which means GPS coordinates, camera Make and Model, DateTimeOriginal timestamps, XMP/IPTC packets and PNG text chunks all arrive intact. The cloud-storage integrations (Drive, OneDrive, SharePoint, Dropbox, Box) hand out links to your stored original, which is worse, not better. On top of that, Zoom generates plenty of metadata of its own — recordings, transcripts, participant logs. The only reliable fix is stripping the file before Zoom ever touches it.
Does Zoom remove photo metadata?
No. We have found no Zoom documentation, release note or support article describing an EXIF-stripping feature for images shared through Zoom Team Chat or the in-meeting chat — and that absence matters, because when platforms do add this protection, they say so. Slack announced its GPS scrub in May 2020 after journalists showed activist locations could be read off shared photos. Microsoft published a roadmap entry, a message-center notice and a rollout schedule when Teams began auto-removing EXIF in 2026. Zoom has published nothing of the kind, and its privacy statement describes collecting and processing meeting content rather than sanitizing it.
That silence lines up with how Zoom's sharing actually works. Zoom chat is not a photo-sharing pipeline the way Instagram is, where every image gets decoded, recompressed and re-encoded on the company's servers. It is a file-transfer system. You attach IMG_4023.jpg, Zoom stores and forwards IMG_4023.jpg, and the person on the other end downloads IMG_4023.jpg. There is no recompression step where metadata would incidentally fall away, and no announced scrubbing step where it would deliberately be removed. Whatever your camera wrote into that file — the GPS IFD with latitude and longitude to five decimal places, the Make and Model fields, the exact second the shutter fired — travels with it.
How Zoom file sharing actually works
Zoom gives you several ways to hand someone a photo, and it is worth walking through each one, because none of them helps you.
Direct upload in Team Chat. This is the everyday case: you drag an image into a 1:1 chat or a channel. Zoom uploads the file to its cloud, shows a preview thumbnail inline, and lets anyone in the conversation download the original. The preview you see in the chat window is cosmetic; the download button fetches the file as sent. A JPEG from a phone keeps its full EXIF block, including location if location tagging was on. A PNG screenshot keeps its tEXt, iTXt and zTXt chunks, which on some systems record the source application or even window titles.
In-meeting chat. File transfer during a live meeting works the same way — it is a direct hand-off, subject only to the file-type and size limits an admin sets. Nothing in the in-meeting path inspects image internals. If you drop a photo into the meeting chat so a colleague can grab it, the colleague grabs everything the photo carries.
Cloud-storage integrations. Zoom lets you share from Google Drive, Microsoft OneDrive, SharePoint, Dropbox and Box instead of uploading directly. This path is the most misleading of the three, because it feels more corporate and therefore safer. It is the opposite: the recipient follows a link to the file stored in your cloud drive, which is your untouched original. We saw the same trap in Teams, where Microsoft explicitly documents link-sharing as the way to preserve EXIF while direct uploads get scrubbed. In Zoom neither path scrubs — but the link path also keeps exposing the original for as long as the link lives.
Photo by RDNE Stock project on Pexels
How Zoom compares with Slack and Teams
The three big workplace platforms have quietly diverged on this question, and Zoom now sits at the unprotected end of the spectrum.
Slack has stripped GPS coordinates from uploaded images since May 2020. The scrub is narrow — camera model, timestamps and XMP data can survive, and researchers have recovered EXIF through certain upload paths — but the most dangerous field, location, is at least targeted. We covered the details in Does Slack Remove Photo Metadata?
Microsoft Teams went further in 2026, rolling out automatic EXIF removal for images shared in chats and channels: GPS, camera make and model, on by default, no admin off-switch. It has real gaps — videos are untouched, and OneDrive links bypass it entirely — and we walked through them in Does Microsoft Teams Remove Photo Metadata?
Zoom has taken no equivalent step. There is no partial scrub as on Slack, no default scrub as on Teams, and no setting an admin could even choose to enable. Anyone modeling their Zoom habits on how Slack or Teams behaves is assuming a protection that does not exist. The pattern matches what we found on Discord, which also forwards attachments untouched: platforms built around file transfer tend to leave your files alone — for better and, metadata-wise, for worse.
The metadata Zoom creates on its own
Shared photos are only half of the Zoom metadata story. The platform is also a prolific producer of metadata about you, and it is worth knowing what accumulates.
Recordings. A cloud or local recording is an MP4, and like every MP4 it carries container metadata in its moov and udta atoms — creation timestamps, encoder strings, duration. Cloud recordings additionally live alongside Zoom's own records of who attended, when they joined and left, and from what device.
Chat transcripts and files. Team Chat history, in-meeting chat logs and every file passed through them are retained under your organization's retention policy. A photo you shared in a meeting chat in March may still be sitting in an archive in December, original EXIF intact, discoverable by an admin or a legal hold.
Participant and telemetry data. Zoom's privacy statement describes collecting device information, approximate location, IP addresses and usage telemetry as part of operating the service. None of this is hidden — it is standard for the category — but it means the platform already knows a great deal about where and how you connect. The EFF's guide to why metadata matters makes the broader point well: the record around a communication often reveals more than the content itself.
Profile pictures. The image you upload as an avatar is processed and resized for display, but the original goes to Zoom's servers. Anything embedded in it — a home GPS tag from a selfie, a phone model — is data you have handed over, whatever ultimately gets served back to viewers.
Photo by Mizuno K on Pexels
Two edge cases people ask about
Screenshots of shared screens. If someone screenshots your shared photo instead of downloading it, the screenshot carries fresh metadata from their machine — not your camera's EXIF. Your GPS data does not survive a screen capture. But do not lean on this as protection: the downloadable original is still sitting in the chat, and a screenshot's PNG chunks can leak details about the capturing system instead.
Virtual background images. Custom virtual backgrounds are uploaded image files like any other. Zoom renders them behind you in the video stream, and the stream itself does not carry your image's EXIF. The uploaded file, however, is stored with your account. A photo of your actual living room, tagged with your actual coordinates, is an odd thing to keep on a third-party server. Strip it first.
The dependable fix: strip before you share
Every path through Zoom delivers your file as-is, so the only place you control the outcome is before the upload. Run the photo or video through Metadata Cleaner first. The tool rewrites images, video and audio files without their EXIF blocks, GPS IFDs, XMP and IPTC packets, PNG text chunks, embedded thumbnails and container atoms — and it does the work entirely in your browser, so the file never leaves your machine on the way to being cleaned. Then share the clean copy in Zoom, store the clean copy in the cloud drive you link from, and upload the clean copy as your background.
Once the file itself carries nothing, Zoom's behavior stops mattering. It cannot leak what was never there. This is also the habit that transfers across platforms: the same clean file is safe in Slack, safe in Teams, safe in Discord and safe in an email attachment, without you needing to remember which platform scrubs which field on which upload path this year.
Conclusion
Zoom does not remove photo metadata, has never said it does, and its file-transfer design gives metadata a clean ride from your camera roll to your colleague's downloads folder. Slack strips GPS; Teams now strips EXIF broadly; Zoom strips nothing. Its cloud-storage integrations extend the exposure by linking recipients straight to your stored originals, and the platform's own records — recordings, transcripts, retained files — keep everything around far longer than the meeting lasted. Treat Zoom like the courier it is: it delivers exactly what you hand it. Hand it a clean file.