What Discord actually does to your images

Send a detailed image to a Discord channel and two versions come into existence. Discord stores the file you attached, but what everyone sees in chat is a preview: resized to fit the message column, recompressed for fast scrolling, and noticeably softer on fine detail. Line art grows fuzzy edges, text in screenshots smears, and subtle gradients pick up banding. Recipients can click through to the original, but almost nobody does, so the preview is your image as far as the room is concerned.

For casual conversation none of this matters. It starts to matter the moment images are the point of the channel: art servers critiquing linework, photography communities comparing edits, design teams reviewing mockups, sellers showing products. In those rooms, the gap between what you exported and what the channel displays is the difference between useful feedback and people squinting at mush.

Then there is the size gate. Free accounts can only attach small files, with a cap that has hovered around 10 MB and has shifted several times over the years, while larger limits are reserved for Nitro subscribers. A high-resolution painting, a phone photo at full quality, a long scrolling screenshot or a chunky animated GIF will simply bounce with an upload error. Compression solves some of it, and the guide to compressing images without visible quality loss shows how far you can shrink before it shows, but past a point you are trading away exactly the detail you wanted to share.

The quieter problem: attachment links expire

For years, people treated Discord as a free image host: attach a file, copy its CDN link, paste that link into forums and profiles. That door is closed. Discord now signs attachment URLs with expiry parameters, and links refresh only while they are viewed inside the app. Copy one elsewhere and it dies within roughly a day, leaving a broken image wherever you pasted it.

The consequence is simple: Discord attachments are for Discord. Anything you might want to reference next week, embed in a forum thread or send across platforms belongs on a real image host with stable URLs.

Host first, then paste the link

The fix for both problems is to reverse the order of operations. Upload the original to HotIMG first, then paste the direct link into Discord. The app unfurls the link into an embed preview automatically, so the channel still sees a picture rather than bare text. The difference is what sits behind it: one click opens the untouched original at full resolution, hosted at a stable URL that works in every other app too.

The practical limits are friendlier as well. Uploads run to 32 MB per file across JPG, PNG, GIF, WebP, BMP, TIFF and SVG, which covers artwork, scans and screenshots that the free attachment cap rejects outright. Display copies are served as WebP so previews load fast, a format worth understanding via the WebP guide, while the original file stays available for download. Anonymous uploads expire on a timer of up to 30 days; a free account adds 25 GB of storage and a never-expire option for anything that should outlive the conversation.

Regulars in art and photography servers get extra mileage from an account. Albums collect a whole project or commission batch behind a single link, which beats pasting fifteen separate URLs into a thread, and a public profile gives your work a permanent home that a scrolling channel never will. When someone asks to see more, you hand over one link instead of scrolling back through months of chat history.

Attachment or link: pick per situation

MethodQuality in chatLifespanBest for
Native attachmentCompressed preview, original behind a clickLives with the messageCasual shots, memes, quick reactions
Hosted direct linkEmbed preview, full original one click awayAs long as your hosting lastsArt, portfolios, references, anything reused
Hosted viewer linkEmbed card with page contextAs long as your hosting lastsSharing with extra context or an album
Reused Discord CDN linkWorks briefly, then breaksRoughly a day outside DiscordNothing, avoid it

Controlling how embeds behave

Discord gives you a little syntax to steer link previews, and it is worth learning all three tricks:

  • Suppress an embed by wrapping the URL in angle brackets. The link stays clickable but no preview card appears, which keeps reference dumps compact.
  • Spoiler an embed by wrapping the URL in double pipes. Viewers must click to reveal the preview, the right move for plot spoilers and surprise reveals.
  • Batch your links. Several image links in one message render as grouped previews, tidier than five consecutive messages each with its own card.

One asymmetry is worth knowing: deleting your message removes the preview from chat, but a hosted file stays live for anyone who saved the link, and a native attachment disappears with the message. Choose accordingly when you post something you might want to retract, and use short expiry timers for anything sensitive from the start.

Tip: if a pasted link refuses to unfurl, the channel may have embed permissions switched off. Ask a moderator whether Embed Links is enabled for your role before assuming the link is broken.

Formats that behave well in servers

A few format habits prevent most Discord image complaints. Screenshots and UI captures travel best as PNG, which keeps text crisp. Photos are happiest as JPG or WebP at sensible quality settings. Animated GIFs autoplay in chat but balloon in size quickly; the GIF hosting guide covers when a short video clip serves better. If a file arrives in an awkward format, the free image converter switches it in the browser before you upload.

Artists sharing work-in-progress get one extra warning: never let the compressed chat preview be the only surviving copy of a piece. Post the hosted link, keep the original in your own storage, and the preview becomes a doorway instead of a destination. The same discipline applies to reference boards and resource channels: a pinned message full of stable hosted links stays useful for years, while one built on attachments decays as messages get pruned.

A server-friendly sharing routine

  1. Decide whether the image matters beyond the current scroll of chat. Throwaway reaction? Attach it natively and move on.
  2. For anything with lasting value, upload the original to HotIMG, choosing never-expire if it should stay reachable.
  3. Paste the direct link, alone or grouped with related links, and let Discord build the preview.
  4. Wrap in angle brackets or spoiler pipes when the channel calls for restraint.

The same hosted links work everywhere your community lives. A link that embeds cleanly in Discord also expands on Reddit and drops into forum BBCode unchanged, and the guide to hosting images for Reddit shows the second half of that story. One upload, every platform, full quality: that is the whole trick.