Why Slack Previews Matter More Than People Think
Someone finds your product, copies the URL, and drops it into a team channel with a short message: 'Could this solve our reporting problem?' You are not in that channel. You cannot explain the positioning, point out the relevant feature, or correct the impression your homepage gives. Your link preview is doing that introduction for you.
Now imagine the card says 'Home' and shows an oversized logo. Or it describes last year's product. The person sharing the link has supplied a reason to care, but the preview contributes almost nothing. Everyone else has to open the page to work out what is being recommended.
That is why Slack previews deserve attention beyond a quick check that an image appears. They can become the compact version of your page that people use while deciding whether to read, discuss, or pass it along. The value is practical: a useful card makes the next person's job easier.
The Audience Can Change After the First Share
A public post usually arrives with the explanation its author wrote. A link moving through a workplace can take a different route. A marketer shares a case study with sales. A salesperson forwards it to an account team. Someone brings it into a discussion about a customer with a similar problem.
Each message might include less context than the one before it. 'Useful example' becomes 'See this.' A descriptive preview gives the next reader something concrete to work with even when the surrounding message is brief.
Consider a hypothetical case study. 'Customer Stories | Acme' identifies the section of the website. 'How a Support Team Cut Its Reporting Process from Six Steps to Two' identifies the problem and the result. The second title gives a colleague a reason to forward it to someone who owns reporting. Use that kind of specificity only when the page actually supports the claim.
A Useful Preview Helps People Decide What to Open
In a working conversation, the reader often has a task already underway. They might be comparing tools, finding evidence for a proposal, or checking whether a launch is ready. A preview earns its space when it helps them judge whether the destination is relevant to that task.
Write the title so it names the resource. Use the description to explain its scope. If the image adds information, let it show the product, the result, or the subject of the page. A screenshot that makes a workflow recognizable can be more useful here than an abstract campaign graphic with tiny text.
This is an editorial judgment, not a claim that better cards produce a particular conversion lift. A preview cannot tell you whether a buying committee approved a tool. What you can assess directly is whether someone seeing the card can identify what the link contains without opening it.
Slack Has More Than One Kind of Preview
Slack calls expanded link previews unfurls. Its developer guide distinguishes classic unfurls, which Slack builds by fetching a URL, from previews supplied by Slack apps. It also describes Work Objects, which can expose richer app data and interactions alongside a conversation.
For a public article, landing page, or product page using classic unfurling, your website metadata is the relevant starting point. For a document or task with an installed integration, the app may supply the preview instead. Changing your Open Graph tags does not necessarily change an app-generated card. First identify which system is providing what you see.
How Slackbot-LinkExpanding Fetches Your Page
A page looking correct in your browser does not establish that Slack can read its metadata. Slack's robot documentation says Slackbot-LinkExpanding requests part of a page using HTTP Range headers and looks for oEmbed, Twitter Card, and Open Graph metadata. Slack also uses an image proxy to fetch and cache images.
For a public page you own, put the preview tags in the HTML returned by the server and make the referenced image accessible without signing in. Check both the page and the image when diagnosing a missing card. A firewall exception for one request does not prove that the other succeeds. Our missing-preview troubleshooting guide walks through those checks.
Why the Title Shows but the Image Doesn't
The HTML and the image are separate resources. Slack-ImgProxy is Slack's image-fetching client, so an image can fail even when the page metadata is readable. Inspect the exact image URL declared in your tags. A login requirement, expired signed URL, or hotlink restriction is a possible cause. Confirm the response is an image rather than an HTML error page, and check server logs for the image request before changing the title or description.
The Thirty-Minute Cache and the Reposting Trap
Slack documents a roughly thirty-minute cache shared across its service. A recent metadata edit may therefore take time to appear. Reposting immediately, even in a different workspace, is not a dependable refresh method. For a launch, test early enough to leave room for corrections; use the platform cache guide when a card stays stale.
Deleting a message removes that message; it does not establish that Slack has discarded its cached response for the URL. Reposting may appear to fix a card when enough time has elapsed or a separate display condition has changed. Treat that as a result to verify, rather than a reliable cache-clearing procedure. The documented cache duration also is not a promise that previously posted cards will update on schedule.
Why a Link Can Work on LinkedIn but Fail in Slack
A successful card on another platform proves that platform received usable information. It does not prove Slack received the same response. Fetchers have different request behavior, caches, and access rules, and an installed Slack app may supply a different kind of card altogether. If Slack alone fails, compare the requests in your server logs and check the conversation's preview settings before redesigning the image.
A Missing Card Can Be a Setting
Slack's sharing help page explains that people can remove previews and change their display preferences. It also lists reasons a preview might not expand, including password-protected pages, missing preview data, and a link recently shared in the same conversation. A missing card is not sufficient evidence that your tags are broken.
Workspace administrators can also restrict previews for websites. That places a real limit on what a website owner or preview editor can promise. You can improve the metadata you supply; you cannot require every recipient to display it.
The same distinction matters for private content. Public preview metadata should contain only information you are comfortable exposing publicly. Keep sensitive customer details, internal project names, and unreleased plans behind the appropriate access controls. A custom card does not make a private destination accessible to its recipient.
What to Check Before Sharing in a Workspace
More visual space is not automatically better. A large image that repeats a logo can make a thread harder to scan without helping anyone understand the link. Before an important share, evaluate the card as part of the conversation rather than as a standalone graphic.
- Title: name the specific page or resource, rather than the company alone.
- Description: explain what the reader will find, with concrete scope instead of a generic slogan.
- Image: choose something recognizable at a small size and avoid relying on tiny labels.
- Destination: check that the link opens the resource the card describes and that recipients have access.
- Message: state why you are sharing it and what response or decision you need.
For a classic website preview, start with Open Graph tags: a specific og:title, an accurate og:description, and an absolute HTTPS og:image URL. Keep important content legible when the image is reduced. The image-sizing guide covers a reusable starting format, but the actual Slack card is the final check for layout and cropping.
For example, a launch announcement could pair a card titled 'Bulk Invoice Export: Release Notes' with a message saying, 'Please review the limitations before tomorrow's customer calls.' The card identifies the resource; the message supplies the action. Neither needs to do all the work alone.
Use the Open Graph checker to inspect the metadata the public page supplies. That helps catch missing fields and wrong image URLs, but it is not a Slack cache inspector and cannot reproduce workspace policies or installed app behavior. Then share the exact URL in an appropriate test conversation in Slack and check both the rendered card and the destination.
How Prelinq Gives You an Editable Preview Source
A partner's article, a merchant's listing, or an external case study may have metadata you cannot change. You can still explain the link in your message, but correcting the original page requires its owner. That is the same ownership problem that affects previews on other platforms.
Prelinq lets you create a shareable link with your own preview title, description, and image, while sending visitors to the original destination. For a classic Slack unfurl, that gives Slack a separate page from which to read metadata. Keep the card accurate about the destination and make its source clear, especially when you are sharing someone else's work.
The preview remains subject to Slack's caching and display settings. Editing it does not guarantee that an existing message will immediately show the new version. Test the actual link in Slack before an important announcement, and include enough context in the message for it to remain useful when no card is shown.
Your next introduction may happen in a conversation you will never see. Give the person sharing your link a card that explains what is on the other side, and give the next reader enough information to decide whether it belongs in their work.