TL;DR: Partly — and not reliably enough to lean on. When you drop a photo into a Discord chat the normal way, Discord routes it through a resizing proxy that re-encodes the preview and strips most of the EXIF block. Discord's own statement described removing "EXIF geocoding data mostly" and running images through their resizing player "to hide your IP." But that scrub is narrow. It targets JPEG GPS tags, while PNG text chunks (tEXt, iTXt, zTXt), XMP and IPTC records, and the metadata inside video files — MP4 and MOV carrying device model, timestamps and GPS — travel through untouched. Send the same image as a file attachment (the paperclip menu, "send as file," or dragging it from a file manager) and Discord stores it on its CDN byte-for-byte, EXIF and all. The only dependable fix is to strip the file before Discord ever sees it.
Does Discord remove photo metadata?
For the most common case — you pick a photo from your gallery and send it into a channel or DM — Discord does remove some of the metadata, but it is doing so as a side effect of a different job. Every image you post inline is fetched and re-served through Discord's media proxy on media.discordapp.net, the same mechanism that resizes pictures into thumbnails and previews so the app stays fast. Discord has publicly described this pipeline as stripping "EXIF geocoding data mostly" and proxying images "to hide your IP." The privacy motive there is real, but notice what it actually covers: the proxy's purpose is to resize and to keep the recipient from seeing where the file was hosted, and dropping the GPS tags is a convenient extra, not a guaranteed full clean.
That distinction matters because the original you uploaded does not stop existing. Discord also serves your file from its content delivery network at cdn.discordapp.com, and the attachment link there points at the file you actually sent. If that original was an untouched JPEG straight off a phone, the APP1 segment beginning with the bytes Exif\0\0 — the camera Make and Model, the DateTimeOriginal, and the nested GPS IFD holding your latitude and longitude — was part of what Discord ingested. The proxied preview your friends scroll past may be clean; that is not the same as the upload being clean. If these field names are unfamiliar, our primer on what EXIF data actually is walks through what a camera writes into every frame.
What does Discord strip, and what survives?
The honest version of the answer is that Discord's stripping is inconsistent by file type, and the gaps are exactly where people get caught out. The proxy is tuned for JPEG, which is what most phone cameras and screenshots produce, and on a JPEG it reliably drops the GPS geolocation. Step outside that narrow lane and the picture changes fast.
PNG files are the clearest exception. PNG does not use EXIF the way JPEG does; it stores text in dedicated tEXt, zTXt and iTXt chunks, and editing or AI tools love to write provenance, prompts, software names and even coordinates into them. Those chunks frequently survive the trip. XMP and IPTC blocks — the packets that hold captions, copyright, keywords and, on many cameras, a second copy of the location — are also not what an EXIF-geocoding scrub is looking for, so they can ride through on formats the proxy passes more gently. The result is a file that reads as "GPS removed" if you only check the EXIF GPS IFD, while a caption or an XMP location tag still names the place. We pull this thread further in what metadata scrubbing actually removes, because "stripped" is a verb that hides a lot of detail about which fields.
Photo by Plann on Pexels.
It is worth contrasting Discord with a platform that scrubs more thoroughly. Instagram re-encodes every single upload, and EXIF disappears as a byproduct of that mandatory pass — we documented exactly that in does Instagram actually remove EXIF data. Discord is softer: it proxies and resizes inline images but does not force every file through a destructive re-encode, and it leaves an untouched original reachable on its CDN. Neither behavior is something to depend on for privacy, but they fail in different directions, and Discord's leaves more behind.
Why does sending a photo "as a file" keep all of its metadata?
This is the trap that catches careful people. Discord treats inline images and file attachments as two different things, and only one of them passes through the proxy that strips geolocation. When you send a photo as a normal image, it gets the resize-and-proxy treatment. When you send the same photo as a file — using the paperclip menu, checking "send as file" on an oversized image, or dragging it in from your desktop file manager rather than picking it from a gallery — Discord treats it as an arbitrary attachment and stores it untouched. No re-encode, no geolocation scrub. The recipient downloads the exact bytes you uploaded, EXIF and GPS included.
The desktop habit makes this worse. On a computer, dragging an image into the message box or attaching it through the paperclip is the natural motion, and that is precisely the path that preserves everything. People who would never knowingly broadcast their home coordinates do it routinely by sharing a "quick screenshot" or an original photo as a file, assuming Discord cleans it the way the inline preview suggested. The GPS tag is the stubbornest field of the set, which is why we gave it its own explainer on how GPS coordinates get embedded in photos — it survives more handling paths than any other piece of EXIF.
Photo by Mikhail Nilov on Pexels.
Discord has never published a help article documenting any of this. Its support center covers attachments, file size limits and supported formats, but there is no page that tells you which upload paths strip metadata and which preserve it. The only on-record acknowledgment is the brief statement about EXIF geocoding and IP-hiding, which is why every confident "Discord removes metadata" claim you read is an inference from testing rather than a quote from documentation. When a behavior is undocumented, it can also change without notice — another reason not to build your privacy on it.
Does Discord strip metadata from videos and other files?
No, and this is the gap that surprises people most. Discord does not run video files through the EXIF-geocoding proxy, so an MP4 or MOV recorded on your phone keeps its container metadata: the moov/udta atoms that hold the recording timestamp, the device make and model, and — if location services were on when you filmed — the GPS coordinates baked in by the camera app. Upload that clip into a channel and all of it goes along for the ride. A phone video is often more revealing than a still, because it captures the same location data across a longer span of time.
The same logic extends to everything that is not an inline JPEG. Audio files keep their ID3 tags. Documents keep their author and revision fields. PDFs keep their creator and producer metadata. Discord is a general file host, and a general file host's default is to store what you give it. The proxy that tidies up your inline photo previews simply was not built to inspect a .mp4, an .mp3 or a .png for embedded identifiers — so it doesn't. If you care about the difference between formats that hide metadata well and ones that leak it, our breakdown of HEIC versus JPEG metadata shows how much the container itself decides.
What does upload-time stripping still not protect?
Even on the happy path — an inline JPEG whose GPS the proxy does remove — there are two limits worth stating plainly. The first is that "removed from the preview" is not "removed from Discord." The original file you uploaded sits on the CDN, and depending on how it was sent and how the link is constructed, the unmodified version can remain retrievable. Stripping that happens at display time protects the people scrolling the channel; it does not retroactively scrub the copy Discord ingested.
The second limit is subtler and applies to redaction, not just metadata. Re-encoded previews and generated thumbnails have, in documented cases, leaked information the uploader thought was gone — researchers have shown that blurred or cropped images shared through chat platforms can sometimes be partially reconstructed, because a downscaled copy is still derived from the full original. Metadata stripping is one field-level concern; the pixels carry their own. The broader point, which the EFF's work on privacy makes well, is that metadata is a category — GPS, timestamps, device serial numbers, captions, software fingerprints — and removing one member of that category while the rest survive is not anonymity. A photo with its GPS gone but its camera serial number and capture time intact still links back to a device and a moment.
That is the through-line of this whole question. Discord protecting your IP and dropping a JPEG's coordinates is a genuine courtesy, but it is a courtesy with edges: wrong file type, wrong upload path, wrong media format, and the protection evaporates. The reliable move is to make sure the file never carried anything you would not want shared in the first place.
How do you remove photo metadata before posting to Discord?
The dependable fix is to clean the file on your own machine, before it ever reaches Discord's servers, so none of the path-by-path inconsistencies above can matter. Metadata Cleaner does this in the browser: you drop in a photo or a video, and it rewrites the file without its EXIF block, GPS IFD, XMP and IPTC records, PNG text chunks and embedded thumbnail, then hands you back a clean copy. Because it handles video as well as images, it closes the exact gap Discord leaves open — the phone clip whose location data Discord would never have touched. The processing happens locally and the file is never uploaded to us.
Once you have the stripped copy, post that instead of the original, and it no longer matters whether you send it inline or as a file, because there is nothing left to expose either way. If you want the longer walkthrough across desktop and phone, our guide on how to strip EXIF data from a photo covers the platform-by-platform steps, and our piece on whether sharing a photo exposes your location shows why "the app probably handles it" is the assumption that gets people caught.
Discord removes some photo metadata, some of the time, on some file types. That is a fine description of a fast chat app and a terrible foundation for a privacy decision. Strip the file yourself and the question stops mattering. Try Metadata Cleaner free and send the clean copy.