Paste a link into Slack, Discord, Telegram, iMessage or Teams and the app fetches your page, reads its og: tags and shows a card. When the card has no image — or never appears — the cause is usually one of the general ones (a relative og:image, tags added by JavaScript, a blocked crawler; see og:image not showing), plus one rule specific to the app. This page goes app by app: what the app's own documentation says, and what we reproduced.
What we did and did not test. On 2026-11-21 we served test pages from a local Node.js server and fetched them with curl 8 as Slackbot-LinkExpanding 1.0 (+https://api.slack.com/robots), Discordbot/2.0 and TelegramBot (like TwitterBot), and ran test images through the platform checks of our OG checker. We did not paste the test pages into the apps — they were not public — so how each app displays a page comes from its documentation. Apple and Microsoft do not document the user agents of their preview fetchers, so we did not imitate them.
One test that explains a lot
We put a page behind a rule that returns 403 to any user agent containing "bot" — a one-line rule of the kind a firewall, a security plugin or an .htaccess file can hold:
| User agent | Status |
|---|---|
Slackbot-LinkExpanding 1.0 |
403 |
Discordbot/2.0 |
403 |
TelegramBot (like TwitterBot) |
403 |
facebookexternalhit/1.1 |
200 |
WhatsApp/2.22.20.72 A |
200 |
If a link previews on Facebook and WhatsApp but not in Slack, Discord or Telegram, look for a rule on "bot" first. Test with the app's user agent:
curl -s -A "Discordbot/2.0" -o /dev/null -w "%{http_code}\n" https://example.com/post
For the tags and the image, each app has a free preview page of ours that shows the card and checks the image against the limits that app documents: Slack, Discord, Telegram and iMessage.
Slack
From Slack's robots page: Slackbot-LinkExpanding "fetches as little of the page as it can (using HTTP Range headers) to extract meta tags", looking for "oEmbed and Twitter Card / Open Graph tags", and "If a page's tags refer to an image, video, or audio file, we will fetch that file as well to check validity". Responses are "cached globally across the service for around 30 minutes."
Two Slack-specific facts:
- robots.txt does not matter. "We do not currently honor robots.txt files." A preview missing in Slack is never a
robots.txtproblem; one missing everywhere except Slack often is. - A workspace can block your site. Anyone removing a preview can tick Also block previews from this website in the future; after that, no link to your site unfurls in that workspace until an admin removes it under Workspace settings → Attachments → Blocked previews (Slack Help). If previews fail in one workspace only, check there.
Slack's own help lists one more reason a link does not expand: "No attachment will expand if that link was shared in the same conversation within the past hour" (Slack Help). When you test a fix, post the link in a different channel, or post a changed URL.
Because Slack asks for a byte range, keep the og: tags near the top of <head>: a server that honours the Range header returns only the first part of the page.
Discord
Discord has the most complete documentation of any platform (Discord link previews). A preview appears only if:
- the page is HTML served over HTTP or HTTPS, with a 2xx response and
text/html(not a download); - the tags are in the server's HTML — "No code is executed";
- there are "At most 5 redirects" and "At most 50 MB of data returned";
- "The whole fetch, including measuring your images and video, must finish within 10 seconds."
The image: "Supported formats are .png, .gif, .jpg, .jpeg, .webp, and .avif." Give og:image:width and og:image:height, or Discord downloads the image to measure it, inside the same 10 seconds. For the large image under the text, set twitter:card to summary_large_image; without it Discord shows "text with a small image". Two or more og:image tags make a gallery of up to four.
Discord "caches previews for about 30 minutes"; to see a change at once, share the URL with ?v=2. The Embed Debugger shows which tags Discord picked up. (If you are building a bot that sends images rather than previewing links, see a Discord bot that makes images.)
Telegram
Telegram publishes no documentation for link previews: no crawler user agent, no image limits, no cache duration. What exists is @WebpageBot, Telegram's bot for refreshing previews: send it the URL, then share the link again. We did not test it. In our bot-rule test, the user agent TelegramBot (like TwitterBot) was blocked like the others; that is the string we tested with, not one Telegram documents.
iMessage (Messages on iPhone and Mac)
Apple's TN3156: Create rich previews for Messages is the reference. Without usable metadata, Messages shows "gray bubbles with the page title, domain, and small icon". To get an image:
- "Images should be at least 900 pixels in width." "Images less than 150 pixels in width may be ignored or presented as icons."
- "The main resource located at the previewed link is limited to 1 MB. The total size of associated resources (icons, images, and videos, etc) is limited to 10 MB."
- "Link previews do not follow
metaredirects, nor run JavaScript … Server-side redirects are followed". - Serve the same metadata to mobile and desktop: "Clients shouldn't have to change the
User-Agentheader to receive useful metadata." - Pages behind a login should still return metadata for the page, not for the login form.
Apple adds: "These recommendations are guidelines only. Limits may change in the future." Our checker flags images under 900 px for iMessage; our 400×209 test image was flagged.
Microsoft Teams and Outlook
Teams reads og:title, og:description and og:image (or the plain HTML title and description), per Microsoft's Share to Teams documentation. Two things that are specific to it:
- Previews can be switched off by the organisation. The Teams messaging policy has a URL previews setting, "On" by default, which "Controls automatic URL previewing in messages" (Teams settings reference). If no link shows a preview for anyone in a tenant, ask the Teams admin.
- No refresh tool. In a Microsoft Q&A thread about a stale thumbnail, a Microsoft moderator confirmed that sharing the URL with
?v=2"seems to work as a temporary workaround".
Outlook shows "a rich preview that includes a link title, thumbnail image, and description" for URLs in mail, and each user can turn it off with Preview links in email (Microsoft Support). Microsoft documents no image limits for either.
The one image that satisfies all of them
| App | Documented image rule |
|---|---|
| Slack | none published |
| Discord | PNG, GIF, JPG, WebP or AVIF; within the 10-second fetch |
| Telegram | none published |
| iMessage | at least 900 px wide; 10 MB of resources in total |
| Teams, Outlook | none published |
A 1200×630 JPEG or PNG under 600 KB, at an absolute HTTPS URL, with og:image:width and og:image:height set, meets all of these, and WhatsApp's stricter 600 KB as well (WhatsApp link preview not showing). Format details for every platform are on the og:image formats page; how to clear each app's cache is on refresh a link preview.
Shareglint renders that image from an HTML template for every page — through the API or a signed image URL in the og:image tag — so a new title means a new image URL and no app holds a stale file. The free plan covers 100 images a month.