Barely, on the path most people use. Does Discord compress images? I uploaded a 4.13 MB iPhone photo and a 1.78 MB transparent PNG from my computer on 2026-07-18. The PNG came back byte identical, and the JPEG lost 0.3%; what Discord does compress is previews, mobile uploads, and emoji.
| My test, 2026-07-18 | Uploaded | Came back | Verdict |
|---|---|---|---|
| iPhone photo, JPEG, 4032x3024 | 4.13 MB | 497 KB at 4032x3024 | 0.3% smaller, resolution kept |
| Transparent PNG, 1240x930 | 1.78 MB | 1.78 MB, same sha256 | untouched, bit for bit |
That verdict has scope: two files, one day, one upload path, a standard attachment sent from a computer. The rest of this page covers where Discord really does compress, why images still look soft in the channel, and how to keep full quality when a file will not fit.
Does Discord Compress Images? What My Test Showed
Inside the upload cap, sent as a normal attachment from a computer, Discord stored my test files without re-encoding them. That is the measured answer, and it contradicts most of what ranks on page one for this question.
The two reference files
I test every platform in this series with the same two files. REF-A is a real iPhone photo: 4,332,705 bytes, 4032x3024, JPEG, with its EXIF metadata still inside. REF-B is a photographic cutout with real transparency: 1,863,465 bytes, 1240x930, PNG with an alpha channel. Those two cover what people actually send, a camera photo and a graphic with transparency, and platforms treat them very differently.
What came back, byte for byte
REF-A came back at 497 KB, 0.3% smaller, about 13 KB off a 4.13 MB file, still 4032x3024. A change that small is not a visible re-encode, but it is a change, so I am not calling the JPEG untouched.
REF-B is the cleaner result: the downloaded file hashed to the same sha256 as the file I uploaded. Identical bytes, identical transparency. Discord did not re-encode it at all.
One test is one test. A different path through the same product, the mobile app instead of a computer, can behave differently. The sections below cover the paths I did not measure using third party reports, labeled as exactly that.
Why Do Discord Images Look Compressed?
Because what you see in a channel is usually not the stored file. Discord runs every upload through a media proxy that generates smaller preview variants, and a preview is what loads in the feed first.
The media proxy, in plain English
Discord's engineering team wrote this up themselves: their image proxy was resizing over 150 million images a day back in 2017, and its successor, the media proxy, exists to serve scaled variants of your upload so a channel full of photos does not pull gigabytes (how Discord resizes 150 million images a day). The stored attachment and the preview are different objects. My test measured the stored attachment, the thing you get when you click download. The preview is smaller by design, and that mismatch is where most complaints about ruined art actually come from. It also explains a familiar moment: an image loads blurry, sharpens when you tap it, and only the downloaded file shows what was really stored. Clients fetch whichever sized variant fits the view asking for it, so the first thing your eyes meet is almost never the original.
This page is one measurement in a series. I am running the same two files through every major platform for the hub on which apps compress your images, and the pattern repeats: apps rarely touch your original, but they almost never show it either.
Previews by surface, originals by download
Discord does not document any difference between DMs and server channels, and my single measured path cannot settle it. What clearly changes by surface is the preview size, which scales to the window asking for it. Avatars and emoji are the real exception: Discord resizes those into fixed small slots every time, which is why saving a Discord emoji as a PNG always hands you a tiny file no matter what was uploaded.
Discord Image Size Limits: Free, Nitro, and Boosted Servers
Free accounts upload files up to 10 MB each. Nitro Basic raises that to 50 MB, full Nitro to 500 MB, and server boosts lift everyone in that server to 50 or 100 MB. The compression question starts at the cap, because the cap decides what Discord will even accept as an image.
| Tier | Cap per file |
|---|---|
| Free | 10 MB |
| Nitro Basic | 50 MB |
| Nitro | 500 MB |
| Server boost, level 2 | 50 MB for all members |
| Server boost, level 3 | 100 MB for all members |
Discord's own File Attachments FAQ spells out what happens above the cap: the file is shared as a download instead of shown inline. It does not get squeezed to fit. It just stops being a picture in the chat.
The 25 MB number you keep reading is stale
Older guides still say 25 MB. The free cap was lowered to 10 MB in late 2024, and third party trackers document both the change and the current tier table (Discord file size limits, tracked by Carly). One more wrinkle from the same source: a Nitro user in a boosted server gets whichever cap is higher. The two never stack.
What to do when a photo will not fit
A modern phone photo runs 4 to 6 MB, so single shots usually clear 10 MB with room to spare. Scans, panoramas, and full quality exports are what break the cap. When one does, compress it below the 10 MB cap before you upload. At quality 80 a camera photo typically lands 60 to 80% smaller with nothing visible lost, and my test shows Discord then stores what you sent, byte for byte.
Does Discord Compress Photos From Your Phone?
On mobile, yes, Discord can compress your photos before they even finish uploading. The computer path left my files alone, but the phone app ships a data saving setting that compresses photos before they upload, and mobile is where nearly every credible complaint I can find comes from.
Low Quality Image Mode
The setting has shipped under the label Low Quality Image Mode in the app's Text and Images settings, and Discord's FAQ describes the same behavior as sending lower quality images to save data on cellular. With it on, the app shrinks the photo on your phone, before Discord's servers ever see the file. Turn it off, and upload on Wi-Fi when quality matters.
What users measure on mobile
The reports are consistent and ugly: a 12 MB phone photo landing around 2 MB, an 80 to 90% cut, in the long running thread asking for a compression toggle (the disable image compression request). Android users in the same thread describe the app recompressing images that were already compressed. I could not reproduce any of that from a computer, which is the point: the phone app is a different pipeline.
So does Discord compress images more aggressively on mobile? The evidence says the phone app can, the computer attachment path did not in my test, and the setting above is the part you control.
What Happens to EXIF Data on Discord Uploads?
Metadata testing by Metaclean found Discord strips GPS coordinates from JPEG uploads, while PNG files keep more of their metadata, such as text chunks (does Discord remove EXIF data). My own test compared bytes and dimensions, not individual fields, so here is what the sizes suggest.
What my byte counts say about metadata
My JPEG came back about 13 KB lighter with identical pixel dimensions, which is the size of a metadata edit, not a re-encode. That lines up with Metaclean's finding, though I will not claim my test proves which fields were touched. The PNG's identical hash means every byte survived, metadata included, which also matches their PNG result.
Strip EXIF before you upload
If the GPS point where you took a photo matters, do not outsource the cleanup to a chat platform. Remove the metadata yourself before upload. Our compressor strips EXIF by default, the hidden data block carrying GPS coordinates, camera model, and the exact timestamp of the shot, on every file that passes through.
How Does Discord Compare to Other Apps?
Discord is one of the gentlest platforms I have measured. The same 4.13 MB photo that lost 0.3% here lost 86.3% on Facebook, lost 35.1% in Google Photos' Storage saver mode, and came back 10.9% larger from Slack.
Same source photo, same method every time: upload through the platform's standard path, download the stored copy, compare bytes. Results recorded in my July 2026 test series.
| App | Same photo came back | Change | Dimensions |
|---|---|---|---|
| Slack | 4.58 MB | 10.9% larger | kept 4032x3024 |
| Discord | 497 KB | 0.3% smaller | kept 4032x3024 |
| 3.91 MB | 5.4% smaller | kept 4032x3024 | |
| X, stored copy | 3.78 MB | 8.5% smaller | kept 4032x3024 |
| Google Photos, Storage saver | 2.68 MB | 35.1% smaller | kept 4032x3024 |
| 0.57 MB | 86.3% smaller | resized to 2048x1536 |
Two caveats worth carrying out of that chart. X keeps a full resolution stored copy but serves a 2048x1536 timeline version of about 0.77 MB, so what followers see is roughly 81% smaller than what was posted. And Slack growing a JPEG is not a typo; its stored copy really did come back 10.9% heavier than the original. Every app in this cluster gets its own measured page in the hub.
How to Send High Quality Images on Discord
Send the file as a normal attachment from a computer, keep it under your cap, and have the receiver download it instead of judging the preview. That preserves the exact bytes on the path I measured, and it costs nothing.
Step 1: get the file under the cap
Anything under 10 MB rides free on a free account. If your file is over, resize it to the resolution it will actually be viewed at, or compress it. The per-destination size targets, Discord included, are laid out in the guide to compressing images for email, web, docs, and uploads.
Pick the format before you upload
Both of my formats survived storage untouched, so choose by content, not by platform folklore. Photos belong in JPEG, which is already compressed the way cameras intend. Graphics, screenshots with text, and anything carrying transparency belong in PNG; my alpha channel came through bit for bit. Converting after upload is too late, since whoever downloads the file gets whatever you fed the pipeline.
Step 2: prefer a computer when quality matters
The phone app is the risky path, per the mobile section above. When the phone is the only option, turn Low Quality Image Mode off first and send on Wi-Fi. From a computer, my measured answer applies: the stored attachment matched what I sent.
Step 3: share a link when only the original will do
For a file over your cap, or a delivery where bit for bit fidelity is the whole point, host the image on cloud storage and drop the link in chat. The receiver gets the original file, no cap, no proxy, no preview standing in for it. The broader technique, shrinking a file while keeping it visually identical, lives in the main guide on how to compress images.
Common Myths About Discord Image Compression
Most Discord image compression advice online is stale, unmeasured, or both. These are the claims I keep running into, checked against the current caps and my own numbers.
Nitro does not turn compression off
Nitro buys a bigger cap, 50 or 500 MB, not a different image pipeline. Previews still get generated, and the mobile data saving setting still applies. If images look soft on a Nitro account, the preview or the phone path is the culprit, exactly as on a free account.
There is no hidden no-compression toggle
The long running support thread I quoted above is a feature request, and it remains a request, not a setting. Nothing in the desktop or mobile client disables the preview system. The honest workarounds are the three steps in the section above, not a buried switch.
Renaming .jpg to .png does nothing you can rely on
The rename trick circulates because Android builds have historically compressed harder. Nobody has documented a mechanism behind it, and on the computer path there is nothing to bypass, since files are stored as sent. Fix the mobile setting instead of the file extension.
Spoiler tags do not protect quality
No measurement supports the spoiler trick. Guides repeating it never show numbers, and Discord documents nothing of the sort. A spoiler changes the blur overlay on the preview, not how the file is stored. Treat it as noise.