Guide

The Complete Embed Tweets Guide

Every way to embed a tweet in 2026 — per platform, with troubleshooting and alternatives now that the native widget is unreliable.

Embedding tweets used to be trivial: copy the snippet, paste it into your HTML, done. In 2024 X started rate-limiting the public widget. In 2025 the breakage got worse — Discord previews died, widget.js began rendering blank for unauthenticated visitors, and the fallback CDNs (fxtwitter, vxtwitter) only solved part of the problem.

This hub maps every LaunchWall article on embedding to a use case. If your embeds are broken, troubleshootingis what you want. If you’re on a specific platform, jump to platform guides. If you’re building something new and want the overview, start with the master guide.

Frequently asked

Why have X/Twitter embeds stopped working?+
X has been quietly rate-limiting and sometimes breaking its public embed widget since mid-2023. The widget.js script still loads, but embeds frequently render blank for unauthenticated visitors, and scraped metadata is delayed or stripped. Alternative CDNs (fxtwitter, vxtwitter) solved the problem for Discord and Telegram previews but don't help on general websites. The most reliable fix today is either a self-hosted static embed or a server-rendered carousel like LaunchWall.
How do I embed a tweet without JavaScript?+
Three options. First, take a high-quality screenshot and link it to the original tweet — bulletproof but unverifiable. Second, use a server-rendered iframe (LaunchWall's approach) that loads the tweet content once, server-side, and serves clean HTML. Third, build a static HTML replica of the tweet and include a hyperlink to the original. The screenshot option is not recommended for landing pages because unverifiable proof actively reduces trust.
Can I embed multiple tweets as a carousel?+
Yes — but not with the native X widget, which renders each tweet as a standalone block. For a carousel or 'wall of tweets' layout, you need either a front-end library (Swiper, Keen, Embla) wrapping native embeds, or a purpose-built tool like LaunchWall that handles fetching, styling, and iframe embedding in one step.
Are tweet embeds bad for page speed?+
Yes, if you use the native X widget. widget.js is around 100 KB compressed and triggers multiple cross-origin requests per tweet; 10 embedded tweets can add 600–900 ms to your LCP. Server-rendered carousels sidestep this entirely because the HTML is baked into the page response. If you care about Core Web Vitals, avoid platform.twitter.com/widgets.js on critical landing pages.
Do tweet embeds work in email?+
No. Email clients block JavaScript, and the X widget requires it. The working approach for email is to screenshot the tweet, link the image to the original post URL, and rely on alt text for accessibility. Newsletters on Substack and Beehiiv render tweet URLs as inline embeds automatically — that's a rendering layer, not a true embed.

Skip the broken widgets. Try the iframe approach.

LaunchWall serves tweet carousels server-side — no widget.js, no rate limiting, no blank embeds. Paste a post URL, embed the iframe.

Try the free generator