Embedding a tweet in an email is different from embedding one on a website or in a blog post. Websites support JavaScript. Email clients do not. That single constraint changes everything about how you approach this.
When someone says "embed a tweet in email," what they usually mean is: show the tweet content in the email in a way that looks credible and is clearly attributable to the original author. The live Twitter widget you see on websites is not possible in email. What is possible — and often more effective — are a few specific methods that work with how email clients actually render content.
Why You Cannot Use Twitter's Native Embed Code in Email
Twitter's "Embed post" dialog gives you a <blockquote> tag and a <script> tag:
<blockquote class="twitter-tweet">
<p>Tweet text here</p>
— Name (@handle) <a href="...">Date</a>
</blockquote>
<script async src="https://platform.twitter.com/widgets.js"></script>
This works on websites because browsers execute JavaScript. Email clients strip or block JavaScript entirely — it is a security requirement, not a quirk. The result in an email is either:
- A plain, unstyled blockquote with no formatting (just the raw text in angle brackets)
- Nothing at all, if the client strips the blockquote tag too
This is why copying the embed code from X and pasting it into your email editor will not work, regardless of which email client or platform you are using.
Method 1 — Screenshot Image with Link (Works Everywhere)
The most reliable method across all email clients and platforms is to screenshot the tweet, upload it as an image, and link the image to the original tweet URL.
How to do it in Gmail
- Screenshot the tweet on x.com (Windows:
Win + Shift + S, Mac:Cmd + Shift + 4) - Compose your email in Gmail
- Click the image icon in the compose toolbar (or use the attachment button)
- Upload your screenshot
- Click the inserted image
- Click the link icon and paste the tweet URL
- The image is now a clickable link to the original tweet
How to do it in Mailchimp
- Screenshot the tweet
- In your Mailchimp campaign editor, add an Image content block
- Upload the screenshot to your Mailchimp content manager
- In the image block settings, set the link URL to the tweet URL
- Set alt text to something like "Tweet from @username: [tweet text]" for accessibility
Why this works well
- Renders correctly in every email client including Gmail, Outlook, Apple Mail, Yahoo
- The tweet looks exactly as it does on X — profile photo, name, handle, text, date
- Clicking the image takes recipients to the original tweet for verification
- No JavaScript, no iframes, no external scripts required
The one limitation
Screenshots are static. If the tweet is deleted or edited after you send the email, you cannot update the image in the already-sent email — but that is inherent to email, not specific to this method.
Method 2 — Styled HTML Quote Block
Instead of a screenshot, recreate the tweet as an HTML element using your email editor's styling tools. This is more work but produces a result that scales cleanly at any size and does not depend on an external image file.
What this looks like in Mailchimp
Mailchimp's drag-and-drop editor does not directly support custom HTML tweet cards, but you can approximate one using:
- A Text block styled with a left border or background color to indicate a quote
- Bold text for the display name
- Regular text for the tweet content
- Small italic text for the handle and date
- A "View on X" link at the bottom
This is more work to design than a screenshot, but it renders perfectly at any font size and respects email client zoom settings better than an image.
For HTML email builders
If you are building HTML emails directly (transactional emails, custom templates), you can create a tweet card using a simple table structure:
<table cellpadding="0" cellspacing="0" border="0" style="border:1px solid #e1e8ed; border-radius:12px; padding:16px; max-width:500px; font-family:sans-serif;">
<tr>
<td style="padding-bottom:12px;">
<strong>Display Name</strong>
<span style="color:#657786; margin-left:4px;">@handle</span>
</td>
</tr>
<tr>
<td style="font-size:16px; padding-bottom:12px;">
Tweet text goes here.
</td>
</tr>
<tr>
<td style="color:#657786; font-size:13px;">
Date · <a href="https://x.com/..." style="color:#1da1f2;">View on X</a>
</td>
</tr>
</table>
This table-based layout renders consistently across Outlook, Gmail, and Apple Mail — the three clients with the most divergent HTML rendering engines.
Method 3 — Mailchimp's Social Card Block
Mailchimp has a built-in "Social" content block designed for sharing social media posts. After the Twitter-to-X transition, this block has had intermittent reliability, but when it works it provides a clean, standardized tweet card without requiring a screenshot.
How to use it
- In the Mailchimp campaign editor, drag a Social block into your email layout
- Select "Twitter / X" as the platform
- Enter the tweet URL
- Mailchimp attempts to pull the tweet metadata (author, text, profile image)
Current limitations
Since X deprecated its free API tier and changed authentication requirements, Mailchimp's ability to fetch tweet metadata has been inconsistent. Some accounts see it working reliably; others see it pulling no data or pulling outdated information.
Check the Mailchimp knowledge base for the current status before building a campaign around this feature. If it fails to pull the tweet data in preview, fall back to the screenshot method.
For Embedding Tweet Testimonials in Email Campaigns
The methods above cover embedding individual tweets in emails you compose manually. If you are running email marketing campaigns that need to show tweet-based social proof consistently — for example, an onboarding sequence that includes customer tweets, a launch announcement that features reactions, or a newsletter that regularly quotes reader feedback — there are some additional considerations.
Screenshots do not scale well. If you use tweet testimonials regularly in email campaigns, you will spend a lot of time screenshotting, uploading, and inserting images. This is manageable for occasional use but tedious at scale.
Linking to a social proof wall is often more effective. Rather than trying to fit multiple tweets into an email, a common pattern is to include a single strong tweet in the email (screenshot method) and link to a page on your website that shows a full curated carousel of tweet testimonials. The email draws attention; the landing page closes the conversion.
This is where LaunchWall fits: you build the curated tweet wall on your website, then the email simply links to it. The tweet in the email is a sample; the full wall on the landing page is the full proof.
Which Method Should You Use?
Single tweet in a Gmail or Outlook email: Screenshot with a linked URL. Works in every client, takes 2 minutes, looks exactly like the original tweet.
Single tweet in a Mailchimp campaign: Screenshot image block with the tweet URL as the link. Most reliable approach.
Multiple tweets in a campaign: One screenshot in the email + a link to a curated LaunchWall page. Cleaner than stacking screenshots.
Custom HTML transactional email: Styled table-based tweet card. More work, but renders consistently without depending on image loading.
Common Questions
Can you embed a live tweet widget in email?
No. All major email clients block JavaScript, which is required for Twitter's widget. Any "live" tweet in email is actually a static representation — a screenshot, an HTML card, or a Mailchimp-rendered card.
Why does the Twitter embed code not work in email?
Twitter's embed code includes a <script> tag that loads platform.twitter.com/widgets.js. Email clients strip script tags for security. Without the script, all you get is an unstyled blockquote.
Does Substack handle this differently?
Yes. Substack renders tweet embeds server-side using its own styled card, which means tweets embedded in Substack posts appear correctly in email. This is unique to Substack — other email platforms do not have equivalent functionality. See how to embed a tweet in Substack for details.
Does tweet embed code work in Outlook?
No. Outlook is one of the most restrictive email clients for HTML and JavaScript. Use a screenshot image with a linked URL for Outlook compatibility.