Discord and Twitter used to work together seamlessly. You pasted a tweet URL into a Discord channel, Discord fetched the Open Graph preview data, and the tweet rendered as a rich embed card — profile photo, tweet text, username, and all.
That behavior broke after X restructured its API and changed its authentication requirements. For a period, tweet URLs in Discord showed no preview at all. As of 2026, previews work inconsistently depending on the tweet, the account, and whether Discord's cache has the data.
This guide explains what currently works, why it sometimes fails, and what your options are.
How Discord Tweet Embeds Work (and Why They Break)
Discord does not have a Twitter integration in the traditional sense. When you paste any URL into Discord, Discord's backend fetches the page's Open Graph (OG) metadata — the same <meta> tags that give any URL a title, description, and image when shared on social platforms.
For tweets, this means Discord sends a request to x.com, reads the OG tags (og:title, og:description, og:image), and renders a preview card using that data.
The problem: X has increasingly blocked automated requests to its pages, requires authentication for many types of content, and has changed its OG metadata structure multiple times since the platform transition. Discord's preview system sometimes gets valid OG data from X; sometimes it gets nothing; sometimes it gets generic fallback data that produces an unhelpful preview.
Method 1 — Paste the Tweet URL (Native Discord Preview)
The default approach: paste the tweet URL directly into a Discord channel.
https://x.com/username/status/123456789
What you will see
In the best case: a preview card showing the tweet author's profile image, their display name, and the tweet text (truncated if long). This looks like a compact tweet card and is the closest thing Discord has to a native tweet embed.
In a partial failure: a preview card with the tweet URL as the title but no text content, or a generic X logo with no tweet-specific information.
In a full failure: a plain link with no preview — just the URL as clickable text.
Why the preview sometimes fails
- The tweet is from an account that has restricted its visibility
- X's OG metadata endpoint returned an error when Discord fetched the URL
- Discord's preview cache has an old or failed result for that URL
- The tweet was posted too recently for Discord's crawler to have fetched it yet
How to force a refresh
If a tweet URL is showing no preview or an outdated preview:
- Discord does not have a built-in "refresh preview" feature
- You can try adding a
?s=1or similar query parameter to the URL — this creates a technically different URL, which forces Discord to fetch fresh OG data - In servers where you have admin access, you can clear the embed cache using a bot command (if a bot with that capability is installed)
Method 2 — Screenshot with Context
When native previews fail or produce low-quality results, the most reliable fallback is a screenshot.
How to do it
- Screenshot the tweet on x.com (Windows:
Win + Shift + S, Mac:Cmd + Shift + 4) - Paste or upload the image directly into Discord
- Post the tweet URL as a separate message or in the same message
The screenshot shows the tweet content clearly; the URL lets people click through to the original. Together, they give readers both the content and the source.
Discord's image rendering
Discord renders uploaded images inline in the channel. A tweet screenshot typically looks clean at Discord's default image size. You can also send the image and URL in the same message — Discord will show the image, and if the URL preview also loads, you will get both.
Method 3 — Use a Bot for Reliable Embeds
Several Discord bots are designed specifically to handle tweet embeds more reliably than Discord's native URL preview. The most well-known is fxTwitter (also known as FixTweet).
How fxTwitter works
fxTwitter is a proxy service that provides its own OG metadata for tweet URLs. By replacing x.com or twitter.com in the URL with fxtwitter.com or vxtwitter.com, you get a version of the URL that Discord can reliably preview.
Example:
Original: https://x.com/username/status/123456789
fxTwitter: https://fxtwitter.com/username/status/123456789
When you paste the fxTwitter URL into Discord, Discord fetches OG data from fxTwitter's servers instead of x.com. Because fxTwitter is specifically designed to serve Discord-compatible previews, the embed loads reliably and includes the full tweet text, images, and author information.
How to use it
- Get the tweet URL from x.com
- Replace
x.com(ortwitter.com) withfxtwitter.com - Paste the modified URL into Discord
The result is a rich embed card with the tweet content, author, and optionally embedded media — without relying on X's inconsistent OG metadata.
Using it in Discord bots
Many Discord communities add a bot that automatically detects x.com URLs and converts them to fxTwitter previews. If you manage a Discord server and want reliable tweet embeds for all members, this is the most practical solution. Several open-source bots on GitHub handle this automatically.
For Builders and Community Managers
If you run a Discord community for a product and want to show tweet-based social proof — customer reactions, launch posts, review threads — the approaches above handle individual tweets. For curating a collection of tweets and displaying them somewhere visible:
- Discord channels are not designed for persistent visual content. Posts scroll out of view.
- Pinning tweet screenshots in a dedicated
#testimonialsor#wall-of-lovechannel is common practice — members can see what customers are saying without the content getting buried. - For your product's website or landing page, a LaunchWall carousel is more effective than Discord pins. It is permanent, always visible, and loads as a polished embed in your marketing page.
The Discord channel is for community discussion. The landing page is for conversion. Tweet testimonials belong on both, but in different forms.
Which Method Should You Use?
Sharing a tweet link casually in a channel: Paste the URL. If the preview loads, great. If not, paste the fxTwitter URL instead.
Previews are consistently broken in your server: Replace x.com with fxtwitter.com in tweet URLs before posting. This is the most reliable workaround in 2026.
You want to add a screenshot for context: Screenshot + URL in the same message gives readers both the content and a source link.
Managing a community where tweet embeds are important: Install a bot that auto-converts x.com URLs to fxTwitter previews.
Common Questions
Why can't I embed tweet code in Discord?
Discord channels are chat interfaces, not web pages. They do not execute HTML or JavaScript. The only way to show tweet content is via Discord's URL preview system (using OG metadata), an uploaded image, or a bot.
Why does discord embed tweet not appear?
The most common reasons: X's OG metadata endpoint failed when Discord fetched the URL, the tweet is from a restricted account, or Discord's cache has a failed result for that URL. Try the fxTwitter URL replacement as a fix.
Can I embed X videos in Discord?
fxTwitter handles video tweets as well. Replace x.com with fxtwitter.com for video tweet URLs, and Discord will embed the video directly in the channel preview.