Slack Link Preview Not Working? 6 Causes & Fixes
The launch post goes into #general. Your teammates see a clean card — title, description, image. Twenty minutes later a prospect in another workspace shares the same link and gets… plain text. Or worse: your brand-new React site never produces a card in any Slack, anywhere, while your old WordPress blog unfurls fine.
Slack breaks in its own ways. Two of its traps don’t exist on any other platform: it never executes JavaScript when reading your page (instant disqualification for most single-page apps), and links posted through a bot or integration don’t unfurl by default. After running more than 550 URLs through our OG Image Checker — which renders the exact Slack card — the failures sort into six repeatable causes. This guide covers all six, the two-tag-family quirk nobody documents, and the ?v=2 trick that replaces the debugger Slack no longer has.
Jump to: How to get a preview · How Slack unfurls your link · The rules nobody wrote down · The 6 causes · Refreshing the cache · Slack vs. a multi-platform checker · Disabling previews · The 30-second routine
How to get Slack to show a link preview
The positive version of this whole guide, in three steps:
- Serve the tags in the HTML. Whatever your server returns on the very first request must already contain
og:title,og:descriptionandog:image— server-rendered or pre-rendered, near the top of the document. - Use an absolute
https://image URL that Slackbot can fetch without a login or firewall challenge. - Paste the URL as plain text. Slack only expands raw URLs — links inside code blocks or quoted text don’t unfurl, the same rule that bites masked links on Discord.
Do all three and the card renders on the first paste. Everything below is for when one of them is silently failing.
How Slack unfurls your link
The mechanics, in order:
- You paste a URL. Slack’s fetcher — the
Slackbot-LinkExpandinguser agent — requests the page and reads the raw HTML your server returns. No JavaScript execution, no waiting for hydration, nothing. - It builds the card from your meta tags — and not just Open Graph. Slack’s own developer blog describes unfurls as built from “a mix of Twitter Card tags and Facebook Open Graph tags”, and some third-party checkers report Twitter Card tags can win out when the two conflict. Slack also reads oEmbed — the only major chat platform that does. We cover the full tag anatomy in our Twitter Cards guide.
- The unfurl is cached per workspace, per URL — a shared link can render one card in your workspace and refuse to render in another that cached it earlier (or fetched it while your tags were broken).
One more thing Slack doesn’t have: a debugger. The old api.slack.com/tools/unfurl tool is gone; today only third-party checkers fill that role. Everything below assumes you’re debugging blind — which is exactly why the six causes are worth memorizing.
The rules nobody wrote down
- Tags must be in the server-rendered HTML, near the top. Client-side injection fails, and there are documented cases — including a long-running Next.js issue — of server-rendered tags sitting too far down the page being missed anyway. Head first, always.
- 1200×630 is the practical target. No official minimum exists; Slack center-crops to fit, so keep logos and text away from the edges. The full per-platform table is in our og image size guide.
- Slackbot obeys robots.txt. Disallow it there and you’ve opted out of previews site-wide — accidentally or not.
Slack link preview not working: the 6 causes
Ordered by how often we see them. The first two are Slack-only.
1. Your meta tags are injected by JavaScript
The number one cause for modern sites. React, Vue, Svelte — if your og: tags only appear after the app mounts, Slack will never see them. The check takes ten seconds: view-source, not DevTools. DevTools shows the DOM after JavaScript has run — exactly what Slack can’t do. If curl https://yoursite.com doesn’t contain your og:image tag, that’s your answer. The fix is server-side rendering or pre-rendering, and tags near the top of the document. Our own site is statically generated for precisely this reason — see how your page’s tags compare with our meta tag checker.
2. You’re posting through a bot, and it didn’t ask for unfurls
If your link arrives via an integration — a deploy notification, an RSS bot, a Zapier zap — links posted through the API do not unfurl by default. The posting app has to pass unfurl_links: true (and unfurl_media: true for media). Slack’s own developer docs are explicit about this. If the same URL unfurls when you paste it but not when the bot posts it, this is the cause — fix it in the integration’s settings or the API call, not on your website.
3. Link previews are switched off
Slack has two layers of settings: your personal Preferences → Messages & media toggle (links stay clickable, previews vanish), and workspace-admin controls that can disable or restrict previews org-wide — including for Slack Connect conversations with other companies. If nobody in the workspace sees previews, check the admin side before touching your site.
4. og:image is missing — or relative
The standard failure, same as every platform:
<meta property="og:title" content="Your Page Title" />
<meta property="og:description" content="One clear sentence about the page." />
<meta property="og:image" content="https://yoursite.com/og.png" />
<meta name="twitter:card" content="summary_large_image" />
That last line matters on Slack more than most platforms — it reads both tag families, not just Open Graph. Need a compliant image fast? The OG image generator exports 1200×630 in your browser; the inspiration gallery shows 26 real cards worth copying.
5. Slackbot can’t reach the page
The fetcher identifies as Slackbot-LinkExpanding 1.0 and obeys robots.txt. Firewalls, Cloudflare bot rules, and hotlink protection routinely challenge it — while your site works perfectly in every browser. Check your firewall events log for that user agent, and make sure robots.txt isn’t disallowing it. While you’re auditing crawler access, our sitemap validator batch-checks that every URL still resolves cleanly for the crawlers you do want.
6. Slack cached an old unfurl
Per workspace, per URL. If the card worked once — or broke once — that cached version is what everyone in the workspace keeps seeing. There’s no Scrape Again button. There is a trick.
Refreshing Slack’s cache: the ?v=2 trick
Same class of workaround as Discord’s ?nocache=1:
- Fix your tags and deploy.
- Append
?v=2to the URL and paste it into Slack — a new URL is a new cache entry, so Slack fetches your current tags. Keep sharing that URL for now: the clean URL’s old cache is still live, so anyone re-sharing it sees the stale card. - Want the clean link back? Wait out the cache — third-party guides put the window around 30 minutes — then delete and re-paste the original URL. Or just keep the parameter; it’s harmless.
On Slack’s mobile apps the same fixes apply, with one wrinkle: previews take more of the screen and crop slightly harder on small displays, and editing a URL before sending is clumsier on a phone. The parameter still works — paste, edit the text, send.
Slack vs. a multi-platform checker
Slack’s official debugger is gone, so here’s the honest field:
| Slack’s tooling | OG Image Checker | |
|---|---|---|
| Official debugger | None — the old one is gone | — |
| Renders the exact Slack card | No first-party tool | Yes — no login, no workspace |
| Refresh the cache | Wait ~30 min or ?v=2 |
Documented above |
| Other platforms | — | X, Facebook, LinkedIn, WhatsApp, Discord, Telegram, Reddit — side by side |
| Tag + image audit | Manual view-source | Full audit: server-rendered tags, image dimensions, file weight |
The same links tend to travel: the card that works in Slack gets pasted into Discord, WhatsApp and Teams an hour later. Compare across all of them in one pass — and if you’re evaluating dedicated tools, our alternatives round-up keeps the honest comparison.
Working through the other chat platforms? Discord’s two unique traps, Facebook’s seven causes, WhatsApp’s 300 KB threshold and LinkedIn’s Post Inspector walkthrough are the sibling guides in this series.
How to disable (or remove) a Slack link preview
Sometimes the goal is the opposite: you want the link without the card. One boundary first: if the link opens but shows no card, that’s a preview problem — covered above. If the link doesn’t open at all, that’s a different problem (permissions, the network, or the URL itself) and no preview setting will fix it.
- For your own view: Preferences → Messages & media → uncheck the website preview option. Links stay clickable; previews disappear.
- Workspace-wide: admins can disable previews or restrict them for Slack Connect conversations — the right lever when a company links policy, not a personal preference.
- Before sharing: there’s no per-message preview toggle after sending, so if you want a clean link, flip the preference first (or accept the card — links with images get clicked more, which is rather the point of this whole site).
Before you post: the 30-second routine
- Raw HTML check —
curlor view-source, og: tags present near the top: meta tag checker. - Preview the card — OG Image Checker renders the Slack card alongside seven other platforms, and flags missing tags before Slackbot ever sees them.
- Mind the two Slack-only traps — server-rendered tags; bots need
unfurl_links: true. - If Slack cached a broken version —
?v=2, re-paste, done.
Slack gives you no error message, no debugger, no second chance at a first impression in the channel where your team — or your prospect’s team — is watching.
FAQ
Why is my link preview not showing in Slack?
The six causes that cover nearly every case: your meta tags are injected by JavaScript (Slack never runs it), link previews are switched off in preferences, og:image is missing or relative, the Slackbot crawler is blocked by your firewall or robots.txt, you are posting through a bot without unfurl_links enabled, or Slack is serving a cached unfurl. Audit all six with a free OG image checker — its Slack tab renders the exact card.
How do I disable or remove a link preview in Slack?
For yourself: Preferences → Messages & media → uncheck the website preview option — links stay clickable but render as plain text. Workspace admins can disable link previews org-wide or restrict them for Slack Connect conversations. There is no per-message preview toggle for messages you have already sent, so switch the setting off before sharing if you want a clean link.
Does Slack run JavaScript when it reads my page?
No. Slack’s crawler fetches your HTML and reads it as-is — any meta tag injected client-side by React, Vue or a script is invisible to it. Test with curl or your browser’s view-source (not DevTools): if the og: tags are not in the raw HTML, Slack will never see them. Keep them near the top of the document — tags far down the page can be missed too.
How do I force Slack to refresh a link preview?
Slack caches one unfurl per URL per workspace — third-party guides put the cache at around 30 minutes. To see your fix immediately, append a query parameter like ?v=2 to the URL and paste it again — the new URL is a new cache entry. Alternatively delete the message and re-share the link after the cache expires.
Does Slack use Open Graph or Twitter Card tags?
Both, and that’s unusual: Slack’s developer blog says unfurls are built from a mix of Twitter Card tags and Open Graph tags, and it also reads oEmbed — the only major chat platform that does. Some third-party checkers report Twitter Card tags can take precedence when the two conflict, so the safe setup is both: correct og:* tags plus twitter:card set to summary_large_image.
Check your OG image right now
Paste any URL and see how it renders on all 8 major platforms — with a full tag audit.
Open the free OG Image Checker →