Does Discord Remove Metadata? | What Your Upload Keeps

You drop a photo into Discord, hit send, and assume the platform will “clean” it. Sometimes it does. Sometimes your upload path skips the cleanup you expected. That gap is why this question keeps coming up.

This article breaks down what Discord removes, what can stay, and how to check your own downloads.

Does Discord Remove Metadata? What Gets Stripped On Upload

Discord doesn’t treat every upload the same way. When Discord processes an image for display (the usual “posted image” look in chat), it re-encodes the file and strips common camera metadata, including EXIF fields that can hold GPS coordinates, camera model, and capture settings.

That said, Discord can still deliver your original file in some cases, like when you upload as a plain attachment or send a non-image file type. In those paths, any metadata inside the file can travel with it.

Discord has described its image pipeline and the way it strips EXIF while handling newer image formats. The details are in Discord’s engineering write-up on modern image formats. Modern image formats at Discord explains how EXIF removal fits into that processing.

What “Metadata” Means In Discord Sharing

People say “metadata” as one bucket, yet there are a few different buckets that matter in Discord chats:

• EXIF: Camera tags stored in many JPEGs and some other formats. GPS location, capture time, device model, lens details, orientation, and more can sit here.
• XMP and IPTC: Text blocks often added by editing apps. Captions, creator name, rights notes, and editing history can live here.
• Container and file tags: Video and audio formats can store creation time, device info, track data, and other fields.
• Filename and visible context: A file name like “passport_scan_2026-02-10.jpg” can leak as much as a hidden tag.

Discord can strip some embedded tags, yet it can’t strip what’s visible in the pixels. A street sign in the frame, a reflection in a window, or a badge on a desk still tells a story.

How Discord Processes Images In Chats

Most of the time, Discord doesn’t store and serve the exact byte-for-byte image you uploaded. It runs the image through a processing path that can resize, recompress, and sometimes convert formats for faster viewing.

Discord’s patch notes show this pipeline gets tuned over time. A September 2025 update mentions a fix for an image processing bug related to empty EXIF metadata being added during uploads. Discord patch notes (September 3, 2025) is a handy point of reference for how much work happens between “upload” and “what others download.”

When Metadata Can Still Travel With Your File

If you want a simple mental model, start here: if Discord transforms the media for display, you usually lose most camera-style tags. If Discord keeps the file as-is, your tags can stay.

Situations where tags can stay include:

• Upload as a file attachment: Sending a file as an attachment can preserve more of the original data than sending it as an “image post,” depending on client and file type.
• Non-image formats: PDFs, Office files, archives, and many other formats can carry author fields, edit history, or embedded IDs. Discord isn’t an editor for those formats.
• Videos: Video files have their own tag systems. Discord’s behavior has changed over time, and your safest move is to assume a raw video can contain device and creation fields unless you strip them yourself.
• Editing-app leftovers: Even when EXIF is gone, some formats can carry other text blocks unless the pipeline removes them.

If your goal is “no hidden tags at all,” treat Discord as a transport layer, not a sanitizer.

How To Check What Discord Kept

You don’t need guesswork. Test with a file you control:

1. Pick a photo from your phone that you know has location tagging turned on.
2. Send it in a private DM to a second account you own, once as an image post and once as a file attachment.
3. Download both copies from Discord.
4. Inspect each downloaded file with a metadata viewer.

If you’re comfortable with a command line tool, ExifTool is the common pick. Run it on the original file and the downloaded file and compare the output.

exiftool -a -G1 -s original.jpg
exiftool -a -G1 -s from_discord.jpg

When Discord has re-encoded the image, you’ll often see a near-empty metadata listing. When the original file passed through, you may see camera make/model, timestamps, and GPS fields.

How You Send It	What Discord Usually Does	What That Means For Metadata
Paste or upload a JPEG as an image post	Processes and re-encodes for chat display	EXIF is commonly stripped; other tags may be reduced too
Upload the same JPEG as a file attachment	May store closer to the original file	More embedded tags can remain
Upload a PNG screenshot	Often treated as an image post and processed	EXIF is uncommon in PNG; text chunks can still exist
Upload WebP (static)	Can be converted or re-wrapped during processing	Camera-style tags are commonly removed when processed
Upload animated WebP or GIF	May be transcoded for playback	Playback conversions can drop embedded tag blocks
Upload a phone video (MP4/MOV)	May transcode for streaming and previews	Creation tags can persist unless you strip them first
Upload a PDF or Office document	Stores and serves the file	Author and edit history fields can remain
Upload a ZIP archive	Stores and serves the file	All internal files keep their own metadata
Share a link to an external host	Discord unfurls a preview when allowed	Metadata rules follow the external host, not Discord

Why People Still Get Surprised After EXIF Is Gone

Stripping EXIF solves one risk: hidden camera tags. It doesn’t solve everything people mean when they say “metadata leak.” A few common surprises still show up:

• The picture content itself: A photo of your desk can show mail, a school logo, a delivery label, or a street view out the window.
• Screen captures can include UI clues: Status bars, battery level, carrier name, and open tabs can reveal more than you meant to share.
• File names travel: If you upload as a file, Discord can show the file name to others.
• Edits can leave traces: Some export workflows carry creator text blocks even when camera EXIF is gone.

So the better question is: did you clean the file before you sent it?

Practical Ways To Share Cleaner Media On Discord

If you want fewer surprises, these habits work well:

Turn Off Location Tagging At The Source

Phone cameras can embed GPS coordinates automatically. If you don’t want location in your photo file, disable location tagging for the camera app. That stops the tag from being written in the first place.

Export A “Share Copy” Instead Of The Original

Most photo editors have an export option that produces a fresh file. Use an export preset that removes metadata, then send that exported copy to Discord.

Use A Screenshot For Sensitive Photos

A screenshot is a new image. It often drops camera EXIF by default, and it also breaks the chain of “original photo from camera roll.” That makes it a decent last-resort move when you need to send a quick proof shot.

Check the screenshot before you send it, since your screen can show app names, tabs, and notifications.

Send As An Image Post When Your Goal Is Tag Stripping

If you want Discord’s image pipeline to do its usual processing, send the picture so it displays inline as an image. Sending it as a file attachment can preserve more of the original file, which can preserve tags.

Strip Metadata Yourself When Stakes Are High

If it’s a legal ID scan, a photo of your home, or anything you wouldn’t want reshared, clean it yourself before upload. Tools like ExifTool can remove EXIF and many other tag blocks, and most modern photo editors can export without metadata too.

Risk You’re Managing	What To Do Before Posting	Why It Helps
GPS location inside photo tags	Disable camera location tagging; export without metadata	Stops location fields from existing in the shared file
Device model and serial-style tags	Export a share copy from an editor	Many export paths drop camera maker/model fields
File name reveals sensitive text	Rename files before uploading as attachments	Prevents the file label from giving away context
Hidden text blocks from editing apps	Use a “remove metadata” toggle on export	Drops extra tag blocks beyond standard EXIF
Video creation fields	Strip metadata with a tool before upload	Reduces device and timestamp tags in the container
Visible clues in the picture content	Crop, blur, or cover identifying areas	Tags aren’t the only leak; pixels matter
Accidental app UI capture in screenshots	Trim status bars and notification banners	Removes on-screen identifiers that viewers can read
Resharing risk after you post	Post in channels with tight access controls	Limits who can view and save the media
Long-lived copies outside your control	Assume anything sent can be saved elsewhere	Keeps expectations realistic and guides safer choices

What To Do Next If You’re Posting Sensitive Files

If the file is sensitive, treat the send like a one-way door. Clean the file first, then pick the send method that matches your goal. Inline image posts tend to get more processing. Attachments tend to preserve more of the original bytes.

If you need a record that can be trusted later, like a photo log for work, attachments may be the right path, since stripping tags can remove capture times and device details you actually want to keep. In that case, share only in places with strict access controls.

If you just want a simple rule that works most days: clean your media before posting, and don’t rely on Discord to do it for you.