There are three ways to get tweet content to show up outside of X. Each solves a different problem. Most people pick based on whatever they hear about first -- not based on what actually fits their use case.
This matters because the wrong choice wastes time. You will either end up with unreliable embeds on your website, a Discord workaround where you needed a professional embed, or a proxy link where you needed a testimonial carousel. Here is the honest breakdown.
What Each One Actually Is
Native X Embeds
This is X's official embed tool. You go to any tweet, click the three-dot menu, select "Embed post," and get a <blockquote> tag plus a <script> tag that loads X's widgets.js library. Paste both into your HTML and the tweet renders with the full X interface -- avatar, handle, text, engagement counts, and a Follow button.
It is the "official" way to put a tweet on a website. It is also the most fragile.
FixTweet (fxTwitter)
An open-source proxy running on Cloudflare Workers. You take any tweet URL and replace x.com (or twitter.com) with fxtwitter.com. When a platform like Discord fetches that URL, FixTweet intercepts the request, pulls the tweet data, and serves its own Open Graph metadata -- title, description, image -- so the receiving platform can render a clean preview card.
FixTweet does not embed tweets on websites. It generates preview metadata for chat platforms.
vxTwitter
A similar proxy service. Replace x.com with vxtwitter.com. Same fundamental approach as FixTweet with slightly different rendering choices and formatting. The two projects share a lineage -- vxTwitter came first, FixTweet (fxTwitter) forked from it and added features.
Both are community-maintained, open-source, and free.
How Each One Works Under the Hood
Understanding the technical differences matters because it explains why each one fails in specific situations.
Native X Embed: Your page loads X's widgets.js script. That script sends a request to X's servers, fetches the tweet data, and renders it inside an iframe on your page. The iframe contains the full X UI -- styled by X, branded by X, and dependent on X's servers being available and responsive. If X is slow, your embed is slow. If X is down, your embed is blank.
FixTweet: When you share a fxtwitter.com URL in Discord (or any platform that fetches OG metadata), the request goes to FixTweet's Cloudflare Workers instance. FixTweet fetches the original tweet data from X's backend, constructs custom og:title, og:description, and og:image tags, and returns an HTML page with those meta tags. Discord reads those tags and renders a preview card. The tweet content is never actually "embedded" -- it is metadata that the chat platform uses to build a preview.
vxTwitter: Functionally identical to FixTweet's approach. The request hits vxTwitter's servers, tweet data is fetched, OG metadata is generated, and the platform renders a preview. The differences are in how the preview looks -- formatting choices, how images are displayed, how threads are handled.
Side-by-Side Comparison
| Feature | Native X Embed | FixTweet | vxTwitter |
|---|---|---|---|
| Works in Discord | Inconsistent | Reliable | Reliable |
| Works on websites | Yes (when it loads) | No -- preview only | No -- preview only |
| Shows full tweet text | Yes | Yes | Yes |
| Supports video | Sometimes | Yes | Yes |
| Supports polls | No | Yes | Limited |
| Load performance | Slow (300-600ms script) | Fast (OG metadata only) | Fast (OG metadata only) |
| Requires script tag | Yes | No | No |
| Verifiable / clickable | Yes -- links to original | Link to proxy page | Link to proxy page |
| Professional for business | Unreliable | No -- meant for Discord | No -- meant for Discord |
| Multiple tweets at once | Slow (separate scripts) | N/A | N/A |
| Self-hosted option | No | Yes (open-source) | Yes (open-source) |
| Maintained by | X (Twitter) | Community / open-source | Community / open-source |
The table makes the core issue clear: FixTweet and vxTwitter solve the Discord preview problem. Native X embeds solve the website embed problem. None of them solve both well.
When to Use Each One
Use Native X Embeds When...
You are embedding a single tweet in a blog post or article where reliability is not critical. If the embed occasionally fails to load, the page still works. You are not depending on the tweet for conversion or social proof -- it is supplementary content.
Be aware of the trade-offs: X's widget script adds 300-600ms of load time per page, the iframe includes X branding and engagement buttons that pull attention away from your content, and if you embed multiple tweets, each one loads separately. For more on the reliability issues, see why X/Twitter embeds stopped working.
Use FixTweet When...
You are sharing tweets in Discord, Slack, Telegram, or any chat platform where you need reliable previews. FixTweet is the best tool for this specific job. Replace x.com with fxtwitter.com in the URL and paste it. The preview will load consistently, include full tweet text and media, and look clean in the chat window.
FixTweet also handles edge cases well -- video tweets, polls, quote tweets, and threads. If you manage a Discord server and want consistent tweet previews, some bots auto-convert x.com URLs to fxtwitter.com URLs. For a full walkthrough, see how to embed a tweet in Discord.
Use vxTwitter When...
Same use case as FixTweet. It is personal preference. Some people prefer vxTwitter's formatting, some prefer FixTweet's. Try both with the same tweet URL and see which preview you like better.
Use None of the Above When...
You need reliable, professional tweet content on a business website -- landing pages, pricing pages, signup flows, product pages. None of these three tools were designed for that.
Native X embeds are unreliable and slow. FixTweet and vxTwitter do not embed on websites at all -- they are preview generators for chat platforms. If you need testimonials from X on your website, you need a different category of tool entirely.
The Gap None of Them Fill
All three tools solve some version of the "show a tweet somewhere else" problem. None of them solve the "curate and display multiple tweet testimonials on a professional website" problem.
Here is what you actually need if you are building social proof from X replies:
- Curation. You posted a launch tweet and got 40 replies. You want 12 of them on your landing page. None of these tools let you pick which replies appear.
- Carousel display. A row of 12 native X embeds looks like a broken Twitter feed, not a testimonial section. FixTweet and vxTwitter do not display on websites at all.
- Update without redeploying. When you get new testimonials, you want to swap them in without touching your site code.
- Performance. 12 native X embeds means 12 separate script loads. That is not acceptable on a conversion-optimized landing page.
- Professional appearance. X's embed widget includes Follow buttons, retweet counts, and X branding. On a landing page, those elements compete with your call to action.
For more on the performance and reliability problems, see how to embed tweets on your website.
What Fills That Gap
Carousel embed tools built specifically for this use case. LaunchWall is one example -- it works like this:
- Paste the URL of your X post
- The tool fetches all public replies
- You pick which replies to include
- You get a single iframe embed code
- Paste it on your site -- one embed, one load, no X widget script
The result is a scrollable testimonial carousel with clean cards, no X branding cluttering the UI, and no dependency on X's embed infrastructure being available. You can update which testimonials appear from a dashboard without touching your site code.
To be clear about what this is: it is a different category of tool. FixTweet is for sharing tweet links in chat. Native X embeds are for putting individual tweets on web pages. A carousel tool like LaunchWall is for curating and displaying social proof on professional websites. They are not competitors -- they solve different problems.
If you are evaluating tools for testimonial display specifically, see best testimonial tools for SaaS for a broader comparison.
FAQ
Is FixTweet safe to use?
FixTweet is open-source and runs on Cloudflare Workers. The code is publicly auditable on GitHub. It does not store your data or require authentication. When you use a fxtwitter.com URL, FixTweet fetches the tweet data from X, generates preview metadata, and serves it to whatever platform requested it. It does not inject scripts on your site and does not track users.
That said, it is a community-maintained project. There is no SLA, no guaranteed uptime, and no support team. For casual use in Discord, this is fine. For anything business-critical, you should not depend on it.
Can I use FixTweet on my website?
Not in a meaningful way. FixTweet generates OG metadata for link previews -- it does not provide an embeddable widget or iframe. If you paste a fxtwitter.com URL on your website, visitors will see a plain link. There is no rendered tweet card, no visual embed, no interactive element.
FixTweet was designed for platforms that automatically render OG metadata as preview cards (Discord, Slack, Telegram, iMessage). Websites do not do this. If you want tweets displayed on your website, you need either X's native embed or a purpose-built embed tool.
What happens if FixTweet goes down?
Your fxtwitter.com URLs will stop generating previews. Links will either show no preview card or show a generic error. The original tweet on x.com is unaffected -- only the proxy preview breaks.
Because FixTweet runs on Cloudflare Workers, downtime is rare but not impossible. The project depends on volunteer maintainers. If the maintainer stops updating it or X changes its API in a way that breaks FixTweet's data fetching, previews will stop working until someone pushes a fix.
This is the trade-off with any free, community-maintained tool. It works well until it does not, and when it breaks, you wait for a volunteer to fix it.
Is there a paid version of FixTweet?
No. FixTweet is free and open-source. There is no premium tier, no paid plan, and no commercial entity behind it. You can self-host your own instance using the open-source code if you want more control over availability.
Some related projects offer paid services, but FixTweet itself is entirely community-funded and community-maintained.
What is the best way to embed tweets on a landing page?
Not with any of the three tools covered in this article.
Native X embeds are too slow and unreliable for landing pages. FixTweet and vxTwitter do not embed on websites at all. For landing pages, you want a tool that gives you a single lightweight embed with curated content, clean design, and no dependency on X's infrastructure.
The two practical options: build custom tweet cards in HTML/CSS (full control, significant development time, manual updates) or use a carousel embed tool that handles the curation and display for you. For a full breakdown of all embedding methods, see how to embed tweets on your website.
Build a tweet testimonial carousel that does not depend on X