Threads does not generate link previews for every URL you paste. Some links show only the raw text or a blank card. This happens because Threads relies on a specific set of Open Graph metadata from the linked page. If the page is missing that data, uses a blocked domain, or has a slow server, the preview fails. This article explains why certain URLs fail and gives you clear steps to fix the issue on your end and on your website.
Key Takeaways: Threads Link Preview Fixes
- Open Graph tags (og:title, og:image, og:description): Threads requires all three to generate a preview card.
- Threads app cache clear: Android: Settings > Apps > Threads > Storage > Clear cache. iOS: Offload and reinstall the app.
- URL debugger tools: Use Facebook Sharing Debugger or Twitter Card Validator to test your link and see missing tags.
Why Threads Fails to Generate a Link Preview for Some URLs
Threads uses the same link preview engine as Instagram and Facebook. When you paste a URL, the app fetches the page and reads the HTML head section for Open Graph meta tags. It specifically looks for og:title, og:image, and og:description. If any of these tags are missing, empty, or blocked, Threads shows no preview.
Common Technical Causes
The linked page may be using a Content Security Policy that blocks Threads from fetching the page. The server might return a 403 or 404 status code. The image URL inside the og:image tag may be too large or use an unsupported format. The domain could be on a blocklist maintained by Meta for spam or policy violations. Slow server response time (over five seconds) also causes Threads to give up on generating the preview.
What Threads Shows When Preview Fails
When a preview cannot be generated, Threads displays the raw URL as plain text. It does not show a broken image placeholder or an error message. The user sees only the link address with no clickable card. This behavior is identical across the Threads mobile app and the web version.
Steps to Fix Threads Link Previews Not Generating
Follow these steps in order. Start with the quickest fix on your device, then check the link itself, and finally adjust your website if you are the site owner.
Method 1: Clear Threads App Cache
- Open your device Settings
On Android, go to Settings > Apps > Threads > Storage. Tap Clear cache. Do not tap Clear data unless you want to sign in again. - On iOS, offload the Threads app
Go to Settings > General > iPhone Storage > Threads. Tap Offload App. This removes the app but keeps your documents and data. Then reinstall Threads from the App Store. - Restart the Threads app
Force close Threads and reopen it. Paste the URL again and wait three to five seconds for the preview to appear.
Method 2: Test the URL with a Debugger Tool
- Copy the failing URL
Open the link in a browser on your computer. Copy the full URL from the address bar. - Go to the Facebook Sharing Debugger
Visit developers.facebook.com/tools/debug. Paste the URL and click Debug. The tool shows you exactly which Open Graph tags are missing or malformed. - Check for redirects or blocked resources
If the debugger shows a 302 or 301 redirect, Threads may follow the redirect but stop if the final page has no OG tags. If the tool shows a warning about a blocked image, the image domain may be disallowed by a robots.txt file.
Method 3: Fix Open Graph Tags on Your Website
- Add the three required meta tags
In the<head>section of your HTML, add:<meta property="og:title" content="Your Title Here"><meta property="og:description" content="Your description here"><meta property="og:image" content="https://example.com/image.jpg"> - Set the og:image dimensions
Use an image that is at least 1200 by 630 pixels. Keep the file size under 5 MB. Use JPEG or PNG format. Avoid using SVG or WebP for og:image. - Add og:url and og:type
These two tags are optional but help Threads understand the page context:<meta property="og:url" content="https://example.com/page"><meta property="og:type" content="article"> - Verify the tags are not blocked by robots.txt
Make sure your robots.txt file does not block the Facebook crawler user-agent. Add this line if needed:User-agent: facebookexternalhitDisallow:
Method 4: Use a URL Shortener with Preview Support
- Shorten the URL with a service that generates OG tags
Services like Bitly or TinyURL do not add OG tags. Use a tool like Linktree or a custom short domain that has OG tags set in its page header. - Test the shortened URL in Threads
Paste the short link into a Threads post. The preview should now work because the short link page has the required meta tags.
If Threads Still Has Issues After the Main Fix
Threads shows a preview for one URL but not another on the same domain
This usually means the specific page is missing OG tags. Check each page individually using the Facebook Sharing Debugger. Some pages on the same domain may have tags while others do not.
Threads preview shows the wrong image or title
The server may be caching an older version of the page. Use the Facebook Sharing Debugger and click the Scrape Again button. This forces Meta to fetch the latest version of the page. Wait one minute and try the URL in Threads again.
Threads does not generate a preview for any URL from a specific domain
Meta may have blocked the domain due to spam reports or policy violations. Check if the domain is listed on Meta’s blocklist by submitting a review through the Facebook Business Help Center. If the domain is not blocked, check the server response time. A server that takes longer than five seconds will cause Threads to skip the preview.
Threads Link Preview Requirements vs Other Platforms
| Item | Threads | Twitter (X) |
|---|---|---|
| Required tags | og:title, og:image, og:description | twitter:card, twitter:title, twitter:image, twitter:description |
| Image format | JPEG or PNG, max 5 MB | JPEG, PNG, GIF, max 5 MB |
| Image size | Minimum 1200×630 pixels | Minimum 1200×675 pixels for summary_large_image |
| Server timeout | 5 seconds | 10 seconds |
| Blocklist | Meta spam blocklist | Twitter spam blocklist |
Threads is stricter than Twitter (X) about image size and server timeout. If your URL works on Twitter but not on Threads, the og:image size or the server response time is likely the problem. Add the required OG tags and ensure the image meets the 1200×630 pixel minimum. Use the Facebook Sharing Debugger to verify the tags are readable. After making changes, clear the Threads app cache and test the URL again. The preview should now appear within three seconds.