Discord doesn't publish how it currently handles photo metadata, so there's no official answer about what it removes today. Discord said publicly in 2018 that it strips some data from images, mostly EXIF location, and runs images through its resizing. Reports since then say a photo posted inline usually comes back without EXIF. Some reports say a file sent as a plain attachment, or a link to an image hosted somewhere else, can keep it. None of that is confirmed for today, so the reliable way to know is to test it yourself.
This page sets out what has been said publicly, what people report, and how to check your own uploads. It also covers what to do if your location needs to stay private or if the photo's date may need to hold up later.
What "metadata" means for a photo
When a phone or camera saves a photo, it writes extra information into the file alongside the image. This is called EXIF data. It commonly includes:
DateTimeOriginal, the time the device's own clock read when the photo was taken- the camera or phone make and model
- GPS coordinates, if location was switched on
Anyone who gets the file can read these fields with an EXIF viewer. That's why the question matters in two ways. You may want the location gone before strangers see it, or you may need the date to still be there later.
What Discord has said, and what people report
Here's the public record, kept separate from what has been reported:
What Discord said: In 2018, Discord said publicly that it strips some data from uploaded images, mostly EXIF location, and that images go through its resizing.
What's reported since: An image posted inline in a channel or DM usually comes back without EXIF. Some people report that a file sent as a plain attachment can keep its metadata. Some also report that a link to an image hosted elsewhere can keep it, because the file is served from that other host rather than processed by Discord.
Neither of these is a documented, current guarantee. A platform can change how it processes uploads without announcing it. Discord's mobile app, desktop app and browser version may not all behave the same way, and different upload paths may not either. A report from someone else describes what happened to their file on the day they tested it.
How to check it yourself
This test answers the question for the way you share photos.
1. Pick a photo with known EXIF. Use a photo straight from your phone or camera that you know has a date, a device name and, ideally, GPS location. Open it in an EXIF viewer first and note DateTimeOriginal, the make and model, and whether GPS fields are present. 2. Post it somewhere private. Use a private server with nobody else in it, or a DM to a second account you control. That keeps your location away from anyone else if the metadata does survive. 3. Try each way you normally share. If you sometimes drag a photo into the chat and sometimes attach it as a file, test both. If you share links to images hosted elsewhere, test that too. 4. Download each copy back. Save the image from Discord to your device as a file. 5. Compare in an EXIF viewer. Open the original and each downloaded copy. Check whether DateTimeOriginal, the device fields and the GPS fields are still there, changed or gone.
Also compare the file sizes and pixel dimensions. If the downloaded copy is smaller or has different dimensions, it was re-encoded, meaning Discord saved a new version of the image. Even if some metadata survived, the copy is a different file from your original.
Run the test again if it matters and some time has passed. Your result shows how Discord handled that upload path when you tested it, not how it will always behave.
If you want your location kept private
Don't rely on Discord to remove it. Even if your test shows that inline uploads lose GPS data, a different upload path, a different app version or a later change on Discord's side could behave differently. The dependable approach is to remove the metadata yourself before the photo leaves your device.
Look for a share or export option on your phone or computer that removes location, or use an EXIF tool to delete the GPS fields. Then open the cleaned file in an EXIF viewer before posting and confirm the location is really gone. That way it doesn't matter what any platform does.
If the photo's date might matter later
This is the case that catches people out. Say a photo might later be needed to show something existed or looked a certain way at a certain time, for a dispute, a claim or an argument over who had something first. In that case the copy on Discord isn't the file to rely on.
There are two reasons. First, the copy you or anyone else downloads back may have lost its EXIF, so the date the device recorded is gone from that copy. Second, a re-encoded copy is a different file, with different bytes. Even where some metadata survives, it's no longer the file your phone saved.
So keep the original file off the platform. Leave it on the device, or copy it to storage you control, as a file rather than through a chat app. Send copies on Discord if you like, but treat the original as the file of record.
Even the original's DateTimeOriginal has limits. It's whatever the device's clock said, and EXIF fields can be edited with ordinary tools. A date in EXIF is the device's claim, which is useful but not proof on its own. ProofLedger has a separate page on whether EXIF data proves when a photo was taken.
What a hash anchor records, and what it doesn't
If you want a record of an original that someone else can check later, one option is to anchor its hash.
A hash is a fingerprint of a file. SHA-256, the method ProofLedger uses, turns the file's bytes into a 256-bit value written as 64 hexadecimal characters. Change a single byte of the file and the fingerprint changes completely. Anchoring means writing that fingerprint into a public transaction on a blockchain, so the record has a time attached that nobody can quietly edit afterwards.
ProofLedger works this way. The file is hashed on your own machine and stays there. Only the hash is sent, and it's anchored on Polygon in its own public transaction. Each proof gets a public verify page. Anyone can also check a proof without ProofLedger: the open verify-proof package compares the file against the proof bundle locally, and the Polygon transaction can be looked up on any block explorer.
The limits are what make it useful or not here:
- It records that this exact file existed no later than the anchor. That's the whole claim.
- It doesn't prove when the photo was taken. A photo taken last month and anchored today shows only that it existed by today.
- It doesn't prove who took the photo.
- It doesn't survive re-encoding. If Discord recompresses your upload, the copy people download has a different hash and won't match the anchor. The anchor matches your original, which is another reason to keep the original.
- It can't be added after the fact. If the original was never anchored, nothing can create a record dated to a time that has passed. Its value lies in doing it when the file is created or collected, before anyone questions it.
If you want to record originals as you make them, ProofLedger's page for creators explains how it works.
The short version
Discord hasn't documented what it does with photo metadata today. Its 2018 statement and later reports point to EXIF location being stripped, with inline images usually coming back without EXIF. Attachments and externally hosted links are reported to sometimes keep it. Test your own sharing path with a photo whose EXIF you know. To keep your location private, remove it yourself before uploading. If the date may matter later, keep the original file somewhere you control, because the Discord copy is a different file.