Slack Keeps Your Photo, Compresses the Preview
No, not the file itself. Slack stores the photo you upload at its original size and hands back that same file when someone clicks download. What looks smaller is the preview shown inline in the channel, which Slack renders as a separate, lighter copy so the conversation loads quickly. The two are not the same thing, and mixing them up is the whole confusion around this question.
Does Slack compress photos?
Not the uploaded file. When you drag a photo into a Slack channel or DM, Slack stores it and serves it back unchanged through the download button, at the same resolution and file size you sent. The one limit on the file itself is size, not quality: Slack's own help center states files can be up to 1 GB, on every plan from Free to Enterprise+.
What you see inline in the message, though, is not that file. It is a preview, and Slack's help documentation is explicit that a preview only renders inline if the image is smaller than 25,000 pixels on its longest side and under 45 million pixels in total, past which Slack shows the file as a plain attachment instead of a full preview. Below that ceiling, the thumbnail shown in the thread is a separate, resized rendition built for fast loading, not the stored file. A public bug report against Slack's own SDK illustrates the split directly: calling the API for a file's metadata returns the original dimensions, while the URL used to render it inline points at a smaller, recompressed version.
The distinction matters because it settles the question people are actually asking, which is whether the copy their teammate downloads is degraded. It is not. It is only the inline thumbnail that is lighter, and clicking through to the full file or hitting download gets you back what was uploaded.
What actually changes between upload and preview
Two different things happen to a photo the moment it lands in a channel, and only one of them touches quality.
The stored file is untouched. Slack keeps what you uploaded, at its original resolution and file size, up to the 1 GB per-file limit. There is no re-encoding step on the way in, and no separate export or 'send as document' step is needed the way it is on WhatsApp or Instagram, because the normal upload already is the original.
The inline preview is a separate rendition. To keep a busy channel scrolling smoothly, Slack generates a lighter thumbnail for display in the message itself, and that is the copy most people actually look at day to day. The 45-million-pixel and 25,000-pixel documented ceilings above simply describe when Slack stops trying to build an inline preview at all and falls back to a plain file attachment.
Retention is the part that actually loses photos. On the Free plan, Slack's own pricing and help pages describe a 90-day access window for message and file history, with content older than a year permanently deleted. Paid plans (Pro, Business+, Enterprise+) carry unlimited message and file history. So a photo shared in a Free workspace does not get smaller over time, but it can disappear entirely once it ages out, which is a different failure mode from compression and a more permanent one.
Why people think Slack compresses their photos
Slack was built for conversation and file handoff inside a team, not for photo galleries, so nothing in the product highlights that the thumbnail and the stored file are different things. A photo that looks slightly soft or small in the channel is showing you the preview, not the archive copy, and there is no in-app label that says so.
Screenshots and diagrams are the other common trigger. Fine text or thin lines in a resized JPEG preview can look blurry at the size Slack renders it in a thread, which reads as compression even when the underlying file, once downloaded, is sharp. Uploading a screenshot as PNG rather than JPEG avoids most of that, since PNG is lossless and the preview renderer has less to soften.
Slack against the apps people actually compare it to
Slack is not competing with WhatsApp or Instagram for how people share photos, but it gets pulled into the same question because teams paste photos into channels the way they would text them. Here is where it actually sits.
| App | Compresses the stored file | Original recoverable | Built for browsing an album |
|---|---|---|---|
| Slack | No | Yes, via download | No |
| Yes | Only via send as document | No | |
| Yes | No | Yes, but not the original | |
| Dropbox | No | Yes | Only as a file list |
| Viallo | No | Yes, via download | Yes |
The pattern that separates Slack and Dropbox from WhatsApp and Instagram is what each was designed to do. Slack and Dropbox move files between people who already know what they are looking at; WhatsApp and Instagram are built to get an image on screen fast, and cutting pixels is how they do that. Neither Slack nor Dropbox needed to solve the compression problem, because neither one applies compression to begin with. See what WhatsApp does to a photo and how Instagram's pipeline works for the contrast in full.
Why Slack is still the wrong tool for a photo album
Not compressing a photo is not the same as being a good place to keep one. Slack has no gallery view, no lightbox, no way to browse a set of photos as anything other than separate messages in a scrolling thread. Finding a specific photo from three months ago means scrolling or searching a channel, not opening an album. And on the Free plan, that photo is only guaranteed to be there for 90 days before it becomes inaccessible, then permanently deleted after a year.
For sharing a screenshot or a document photo with a colleague, none of that matters. For an actual set of photos someone should be able to look through, a workspace channel is a worse fit than a tool built for that job, whatever the compression story looks like.
Sharing a real album instead of a channel thread
Viallo is built for the case Slack is not: a set of photos someone should be able to open, browse and download without digging through a chat history. Photos are stored at the resolution and file size they were uploaded at, with nothing resized or re-encoded on the way in.
- No compression on upload: a JPEG, PNG or WebP is kept at the resolution and file size you uploaded. Nothing is resized or re-encoded.
- HEIC is the one exception: iPhone HEIC and HEIF photos are converted to JPEG at quality 92, at full pixel dimensions. The HEIC file itself is not kept.
- A link, not a channel invite: recipients open a real gallery in their browser, with the original behind the download button on every photo, and no account required to view it.
The free plan starts at 2 albums, 200 photos and 10 GB of full-resolution storage, no credit card required.
Frequently Asked Questions
Does Slack reduce photo quality when you upload it?
No. The file Slack stores is the one you uploaded, at the same resolution and size, and the download button returns exactly that file. Slack's help center caps file uploads at 1 GB per file on every plan, but does not describe any quality reduction of the stored file itself.
Why does a photo look blurry inside a Slack channel?
You are looking at the inline preview, not the stored file. Slack builds a separate, lighter thumbnail to render inside the message thread, documented to render inline only under roughly 25,000 pixels on the longest side and 45 million pixels total. Downloading the file or opening it in full gets you the original.
How long does Slack keep the photos I share?
It depends on the plan, not the photo. On the Free plan, Slack's own pages describe 90-day access to message and file history, with anything older than a year permanently deleted. Pro, Business+ and Enterprise+ plans carry unlimited history, so nothing ages out on its own.
Is Slack a good place to share a photo album?
Not really, even though it does not compress the files. Slack has no gallery or lightbox view, so a set of photos is just a run of separate messages in a thread, and on the Free plan it is subject to the 90-day and one-year retention limits above. A platform built around albums, like Viallo, or a storage tool like Dropbox, is a better fit for photos meant to be kept and browsed.