LaunchWall
Back to blog
Tutorial

Discord Twitter Embed Not Working? Here's Every Fix (2026)

Tamim
April 15, 2026
8 min read

You pasted an X link into Discord and got nothing. No preview card, no image, just a plain URL sitting in the chat. Or maybe you got the generic X logo with a title but no actual tweet text. No author, no media, nothing useful.

This has been happening since late 2023, and it is still inconsistent in 2026. Some tweets preview fine. Others show nothing. The same URL might work in one server and fail in another.

This guide covers every fix that actually works right now — from quick URL swaps to Discord bots that handle it automatically.

Why Discord Twitter Embeds Break

The short version: Discord uses Open Graph (OG) metadata to generate URL previews. When you paste any link, Discord's backend fetches the page and reads its og:title, og:description, and og:image tags to build the preview card.

X changed how it serves that metadata. Specifically:

  • X blocks or rate-limits many automated requests to its pages
  • The OG metadata structure has changed multiple times since the Twitter-to-X transition
  • Some tweets return valid OG data, others return generic fallback data or nothing at all
  • X requires authentication for certain content that used to be publicly accessible

This is not a Discord bug. Discord's preview system works fine for every other platform. The issue is X restricting what external services can access.

For a deeper breakdown, see why X/Twitter embeds stopped working.

Fix 1: Use FixTweet (fxTwitter)

This is the most reliable fix and the one most people use.

Replace x.com or twitter.com in the tweet URL with fxtwitter.com or fixupx.com. That is it.

Original:  https://x.com/username/status/123456789
FixTweet:  https://fxtwitter.com/username/status/123456789
Alt URL:   https://fixupx.com/username/status/123456789

When you paste the FixTweet URL into Discord, Discord fetches OG data from FixTweet's servers instead of x.com. FixTweet is specifically designed to serve clean, Discord-compatible previews, so the embed loads every time.

What FixTweet supports

  • Text tweets with full content (no truncation)
  • Images, including multi-image tweets
  • Videos, embedded directly in Discord
  • Polls with vote counts
  • Quote tweets

FixTweet variants

FixTweet also offers specialized URLs for different embed styles:

  • g.fxtwitter.com — gallery mode, minimal text, focuses on media
  • t.fxtwitter.com — text-only mode, no media previews
  • d.fxtwitter.com — direct media link (returns the image or video file directly)

Why it works

FixTweet runs its own servers that fetch tweet data through X's API and serve properly formatted OG metadata. Discord's crawler hits FixTweet, gets clean metadata, and renders the preview. The original tweet link is preserved — FixTweet redirects clicks to the real tweet on x.com.

For more detail on how this compares to alternatives, see FixTweet vs vxTwitter vs native X embeds.

Fix 2: Use vxTwitter

vxTwitter is an alternative to FixTweet that works the same way. Replace x.com or twitter.com with vxtwitter.com or fixvx.com.

Original:    https://x.com/username/status/123456789
vxTwitter:   https://vxtwitter.com/username/status/123456789
Alt URL:     https://fixvx.com/username/status/123456789

How vxTwitter differs from FixTweet

The core functionality is the same — both serve proper OG metadata for tweets. The differences are in rendering:

  • vxTwitter shows multi-image tweets side-by-side rather than stacked
  • Video handling is slightly different — vxTwitter tends to embed videos at higher quality in some cases
  • Text formatting and truncation behavior varies marginally

Both are reliable. Most people pick one and stick with it. If one is down or slow, try the other.

Fix 3: Install a Discord Bot

If you manage a Discord server and want tweet embeds to work automatically for everyone, a bot is the cleanest solution. Nobody has to remember to swap URLs.

FixEmbed

FixEmbed is the most popular option. It monitors messages for x.com and twitter.com links and automatically replaces them with FixTweet previews.

What it handles:

  • X/Twitter links
  • Instagram links
  • Reddit links
  • Threads links
  • TikTok links

To add it to your server:

  1. Visit the FixEmbed invite page on top.gg or its GitHub repo
  2. Click "Add to Server" and select your server
  3. Grant the required permissions — it needs "Read Messages" and "Send Messages" at minimum
  4. The bot works immediately. No configuration required for default behavior.

BetterTwitFix

BetterTwitFix is a more specialized bot focused on Twitter video embeds specifically. If your server shares a lot of video tweets, this handles them more consistently than the default Discord preview.

Setup is the same — invite via its listing page and grant message permissions.

Which bot to pick

FixEmbed if you want a general-purpose fix that handles multiple platforms. BetterTwitFix if your primary issue is video tweet embeds specifically. For most servers, FixEmbed covers everything.

Fix 4: Use a Browser Extension

If you want to fix tweet embeds before you share them — without relying on a bot — a browser extension can auto-convert URLs as you paste them.

FxTwitter Embeds Fixer (Chrome)

This Chrome extension detects when you are about to share an x.com or twitter.com URL and converts it to a fxtwitter.com URL automatically. You copy a tweet link normally, paste it into Discord, and the extension rewrites it before it sends.

The limitation: this only affects your own links. Other members in the server still see broken embeds for their own links unless they also install the extension or the server has a bot.

For a server-wide solution, the bot approach from Fix 3 is better. The extension is useful if you share tweets in multiple servers where you do not have admin access.

Fix 5: Screenshot + URL Combo

Sometimes you do not want to use a proxy service. Maybe you are sharing a sensitive tweet and want to control exactly how it appears, or you just need a quick one-off solution.

  1. Open the tweet on x.com
  2. Screenshot it (Windows: Win + Shift + S, Mac: Cmd + Shift + 4)
  3. Upload the screenshot to Discord
  4. Paste the original tweet URL in the same message

Discord renders the uploaded image inline. The URL gives people a clickable link to the original. Together, they provide both the visual content and the source — no third-party service needed.

This is the most manual approach, but it is also the most reliable. A screenshot never fails to render.

Fix 6: Try Adding a Query Parameter

This is the least reliable fix, but it is worth trying when nothing else is available.

Append ?s=1 or any query parameter to the end of the tweet URL:

Original:  https://x.com/username/status/123456789
Modified:  https://x.com/username/status/123456789?s=1

This creates a technically different URL from Discord's perspective. Discord may have cached a failed OG fetch result for the original URL. The modified URL forces Discord to make a fresh request, which sometimes returns valid data.

It does not always work. If X's servers are returning bad OG data for that tweet in general, a fresh request will fail the same way. But if the issue was a temporary fetch failure that got cached, this clears it.

For Server Admins and Community Managers

If you run a Discord server where tweet sharing is a regular part of the conversation — a product community, a marketing team server, a support channel — here is the practical setup:

Install FixEmbed. It handles tweet embeds automatically for all members. Five minutes of setup eliminates the problem permanently.

Pin a message explaining the workaround. Not everyone knows about fxtwitter.com. A pinned message in your general or links channel saves repeat questions. Something like: "If a tweet link does not preview, replace x.com with fxtwitter.com in the URL."

For a #testimonials or #wall-of-love channel: Discord channels scroll. Posts get buried. If you are collecting tweet testimonials from customers, a Discord channel works for internal tracking, but it is not a great place to show them off. Consider curating your best tweets into a LaunchWall carousel for your website instead — it is permanent, always visible, and does not depend on Discord or X's embed systems working correctly.

For more on collecting and displaying tweet testimonials, see how to use Twitter testimonials on your website.

FAQ

Why are Twitter embeds not working in Discord?

X (formerly Twitter) changed how it serves Open Graph metadata — the data Discord uses to generate URL previews. X now blocks or rate-limits many automated requests, which means Discord's crawler often cannot fetch the information it needs to build a preview card. This is an X-side issue, not a Discord bug. See why X/Twitter embeds stopped working for the full technical explanation.

How do I fix X links not showing previews in Discord?

The most reliable fix: replace x.com in the URL with fxtwitter.com before pasting it into Discord. This routes the preview through FixTweet's servers, which serve proper OG metadata that Discord can render. For a server-wide fix, install the FixEmbed bot so all tweet links are handled automatically. See the full guide on how to embed a tweet in Discord.

Is there a Discord bot that fixes Twitter embeds?

Yes. FixEmbed is the most popular — it auto-detects x.com and twitter.com links and replaces them with working previews. It also handles Instagram, Reddit, Threads, and TikTok links. BetterTwitFix is another option focused specifically on Twitter video embeds. Both are free and take a few minutes to set up.

What is FixTweet and is it safe?

FixTweet (fxtwitter.com) is an open-source service that serves Discord-compatible previews for tweet URLs. It fetches tweet data from X's API and returns properly formatted OG metadata so Discord can render the preview. The project is open-source on GitHub, widely used in the Discord community, and does not require you to log in or provide any credentials. It redirects clicks to the original tweet on x.com.

Why do some Twitter links preview in Discord but not others?

X's OG metadata endpoint is inconsistent. Some tweets return valid data, others return generic fallback data or nothing. Factors that affect this include: whether the account is public or restricted, how recently the tweet was posted, whether X's servers are under load, and whether Discord has a cached (possibly failed) result for that specific URL. There is no way to predict which tweets will preview correctly.

Can I fix Discord Twitter embeds on mobile?

Yes, but your options are more limited. You cannot install browser extensions on mobile, so the URL swap method is your best bet. When sharing a tweet from the X app, copy the link and manually edit x.com to fxtwitter.com before pasting it into Discord. If your server has FixEmbed or a similar bot installed, you do not need to do anything — the bot handles it automatically regardless of what device you are on.

Will Discord ever fix Twitter embeds?

Discord's preview system is not broken — it works correctly for every other major platform. The issue is on X's side. Discord would need X to serve consistent, accessible OG metadata for tweet URLs, and X has shown no indication of changing its current approach. The third-party workarounds (FixTweet, vxTwitter, bots) exist specifically because this is unlikely to change. See X embed alternatives for long-term options.

What is the difference between FixTweet and vxTwitter?

Both serve the same purpose: providing Discord-compatible OG metadata for tweet URLs. The differences are minor. FixTweet offers more URL variants (gallery mode, text-only mode, direct media links). vxTwitter handles multi-image tweets with side-by-side rendering. Both are open-source, both are reliable, and both redirect clicks to the original tweet. Most people pick whichever one they tried first and stick with it. For a detailed comparison, see FixTweet vs vxTwitter vs native X embeds.

Want tweet testimonials on your website, not just Discord? Build a carousel →

Back to all posts