How to Make a Discord Image Link Not Download (And Preview Instead)
When you paste an image link into Discord, the behavior you get — whether it previews inline or triggers a download — depends on more than just the URL itself. Understanding why this happens puts you in control of how your images appear in any server or DM.
Why Discord Downloads Some Images Instead of Previewing Them
Discord's image preview system works by reading the content type of the URL you share. When a link points directly to an image file hosted on a server that returns the correct HTTP headers — specifically Content-Type: image/jpeg, image/png, image/gif, or image/webp — Discord renders it as an embedded preview automatically.
The download behavior kicks in when one of the following is true:
- The server hosting the image returns a
Content-Disposition: attachmentheader, which instructs browsers and apps to treat the file as a download - The URL uses a non-standard file extension or no extension at all
- The hosting platform requires authentication or redirects before delivering the file
- The link points to a file storage endpoint rather than a direct image URL
This is entirely a server-side behavior — Discord is responding to what the hosting server tells it to do.
The Difference Between a Direct Image Link and a Page Link
This is where most confusion happens. There are two types of image-adjacent URLs:
| URL Type | What It Points To | Discord Behavior |
|---|---|---|
| Direct image URL | The raw image file itself | Inline preview (usually) |
| Page URL with an image | A webpage that contains the image | No preview, link only |
| CDN URL with attachment header | Image file with forced-download header | Download prompt |
| Discord CDN URL | Discord-hosted image | Inline preview |
A direct image URL typically ends in .jpg, .png, .gif, or .webp and goes straight to the file. A page URL — like a Google Photos share link or a Dropbox page — leads to a webpage that displays the image, not the image itself.
How to Get an Image Link That Previews Instead of Downloads 🖼️
Use a Hosting Service That Serves Direct Links
The most reliable fix is choosing an image host that delivers true direct URLs. Services like Imgur, Catbox, or Postimages are commonly used for Discord sharing because their direct links return the image file with the right content type headers — no authentication wall, no redirect, no forced download.
When using these platforms, look for the option labeled "Direct Link" or "Direct URL" rather than the share page link. The direct link usually ends in an image file extension.
Check Whether Your URL Actually Points to the Image
Copy your image URL and paste it into your browser's address bar. If it opens the image file directly — filling the tab with just the image — Discord will likely preview it. If it opens a webpage around the image, Discord won't embed it.
Avoid Cloud Storage Default Share Links
Google Drive, Dropbox, and OneDrive default share links are page URLs, not direct image URLs. They also often require the viewer to be signed in, which breaks Discord's ability to fetch the image entirely. These platforms are not designed for raw image delivery to third-party apps.
Some users work around this with modified Google Drive URLs that swap /file/d/FILE_ID/view for /uc?export=view&id=FILE_ID, which attempts to serve the file directly — but this method is unreliable and frequently breaks depending on sharing permissions and Google's own policy changes.
Check the File Extension in the URL
Discord's preview engine is more likely to render an image when the URL path ends in a recognizable extension. If your URL looks like https://example.com/image?id=12345 with no file extension, Discord may not recognize it as an image at all, even if the server is technically serving one. A URL structured as https://example.com/images/photo.png gives Discord a cleaner signal.
Variables That Affect Your Specific Situation 🔧
Several factors determine whether any given image link previews or downloads in Discord:
- Where the image is hosted — the hosting provider's server configuration is the primary variable
- How the link was generated — direct link vs. share page link vs. CDN URL
- Your Discord client — desktop, browser, and mobile clients occasionally handle embeds slightly differently
- Server embed settings — Discord server owners can disable link previews entirely for their server, which would suppress image embeds regardless of URL type
- User-level embed settings — individual Discord accounts can also disable link previews in their own settings under Text & Images, which affects what you see, not what others see
When the Problem Is on the Receiving End
If someone else can't see your previewed image, the issue might not be your link at all. They may have link previews disabled in their own Discord settings, or the server itself may have embeds turned off. Asking them to check User Settings → Text & Images → Show image link previews can rule that out quickly.
The behavior you get from any given image link is the combined result of the hosting server's configuration, the structure of the URL, and the Discord environment it's being shared into. Each of those layers can behave differently depending on your setup.