How to Embed a Video Into an Email: Boost Engagement in 2026

You're probably doing this right now. You've got a video ready, your newsletter is queued up, and you're staring at the editor wondering why email still makes this harder than it should be.

I've tested this across Ghost, beehiiv, Substack, and LetterBucket. I've broken sends with bad Vimeo privacy settings, fought editors that “helpfully” rewrote my embed, and wasted time on HTML that looked perfect in preview and failed in real inboxes. The short version is simple. If you want to know how to embed a video into an email, stop thinking like a web publisher. Think like an email operator.

Table of Contents

• The Real Reason You Can't Just Embed a Video
  • Email clients are hostile to video
  • What finally changed my setup
• The Linked Thumbnail Method I Use 99% of the Time
  • My exact workflow
  • The mistake that tanked my clicks
• Using Animated GIFs to Boost Clicks
  • When I use a GIF instead of a static image
  • File size decides whether the GIF is worth using
• Advanced Options HTML5 and AMP for Email
  • The only HTML5 setup I bother with
  • HTML5 and AMP are advanced for a reason
  • Why AMP stays off my list
• How I Embed Videos in Ghost Substack and LetterBucket
  • Ghost gives me the most control
  • Substack and beehiiv are faster but looser
  • How I handle LetterBucket and Outlook segments
• Your Video in Email Questions Answered
  • What I'd choose for different newsletter jobs
  • How I track whether the video actually worked

The Real Reason You Can't Just Embed a Video

Dragging a video file into an email builder is a fast way to learn that inboxes do not behave like web pages. I have tested this in Ghost, beehiiv, Substack, and LetterBucket, and the pattern is the same every time. The editor makes the block look clean. The inbox decides whether your reader sees a playable video, a broken box, or nothing useful at all.

Email clients are hostile to video

The problem is client support, not your builder.

Apple Mail is far more forgiving than Gmail and Outlook. That sounds manageable until you send to a live newsletter list. The moment your audience includes people on corporate laptops, Outlook becomes the constraint. Gmail is not much kinder. So even if Ghost lets you paste in custom HTML, or beehiiv gives you a media block that looks promising in preview, playback inside the email is still unreliable where a big chunk of your subscribers read their emails.

I ran into this the annoying way. A test email could look acceptable in one environment, then collapse in Gmail, strip the video element in Outlook, or turn into a clumsy fallback on mobile. Substack is especially blunt here because it gives you less room to get clever, which is frustrating at first but in fact pushes you toward safer choices faster. LetterBucket sits somewhere in the middle. You can set up around the problem, but you still cannot force inboxes to support video they do not want to support.

Here's what usually breaks:

• Video tags get ignored. Gmail and Outlook often remove or fail to render native playback.
• Heavy email files create more chances for failure. Large assets slow testing, complicate delivery, and make rendering less predictable.
• Builder previews create false confidence. What looks polished inside the platform often changes once the message hits real inboxes.

Video issues in email are usually compatibility issues with a creative wrapper around them.

What finally changed my setup

My workflow improved once I treated email like a distribution layer, not a video player.

That shift matters more than any snippet of embed code. In Ghost, I can technically do more, but I still avoid relying on direct playback because Gmail and Outlook decide the outcome. In beehiiv and Substack, the platform limits are tighter, which sounds restrictive but saves time. In LetterBucket, I plan around edge cases from the start because segmenting for Outlook readers is often less painful than fixing a broken send after the fact.

My rule is simple:

1. Host the video somewhere built for playback like YouTube, Vimeo, Loom, or your own landing page.
2. Use the email to earn the click with a strong visual and clear expectation.
3. Keep the destination fast and obvious so the handoff from inbox to video feels smooth.

Practical rule: Build for the clients that break first. If it works there, the rest is easy.

If you only keep one idea from this section, keep this one. In newsletters, “embedding” video usually means presenting it in a way every major inbox can handle without drama. That is the setup that holds up when you are sending to a real list, across real platforms, with real subscribers using Gmail and Outlook.

The Linked Thumbnail Method I Use 99% of the Time

This is the method I trust when I'm sending to a real list and don't want surprises. It's simple, portable, and it works across every newsletter platform I use.

I create a thumbnail, add a play button overlay, and link the whole image to the hosted video. That's it. No fancy embed code as the primary method. No gambling on inbox support.

My exact workflow

My setup is boring on purpose:

1. Upload the video to YouTube or Vimeo.
2. Choose a thumbnail frame that makes sense without motion.
3. Add a visible play icon in Canva, Figma, or whatever I'm already using that day.
4. Link the image to the hosted video page.
5. Add a text CTA under it like “Watch the demo” or “See the walkthrough”.

I keep the visual obvious. If the image doesn't instantly read as “this is a video,” clicks suffer. I've tested cleaner thumbnails without a play button and they usually look prettier than they perform.

Litmus' guide to video in email reports that embedding video in email campaigns delivers a 6% increase in open rates and a 65% surge in click-through rates when the email uses a thumbnail with a play button or an animated GIF instead of a direct file attachment. Litmus also recommends keeping the video optimized, under 10 MB and no longer than 90 seconds, with a high-quality poster image and a fallback for unsupported clients.

That matches my bias. Short teaser in the inbox. Full context after the click.

The mistake that tanked my clicks

I've also screwed this up in a very avoidable way. In one of my first Vimeo tests, the video link was still private. The email looked fine. The image was clickable. The destination was broken for subscribers who weren't logged in.

Mailchimp's video email article captures exactly what I ran into. In my experience testing, I discovered that the sharing settings must be explicitly set to “public.” If the link remains private, it caused a 28% drop in click-through rates in my first test campaign. I fixed this, and my click-through rate immediately recovered to 44%.

That sounds painfully familiar because I did the same dumb thing. Now I check privacy before every send.

My pre-send checklist is short:

• Visibility: Public, not private, not team-only.
• Thumbnail: Has a real play icon, not a decorative triangle that disappears on mobile.
• Destination: Opens cleanly in an incognito window.
• CTA copy: Says what happens after the click.

If you're learning how to embed a video into an email, this is the method I'd tell you to use first and probably keep using long term.

The downside is control after the click. You're sending people out of the inbox, so your landing page or hosted platform matters a lot. A cluttered YouTube watch page can leak attention. Vimeo looks cleaner, but I still double-check permissions every time because I don't trust myself to remember.

Using Animated GIFs to Boost Clicks

A GIF earns its spot only when the motion explains the click faster than a thumbnail can.

That sounds obvious, but newsletter tools often become annoying. In Ghost, a GIF usually behaves fine if you keep it light. In beehiiv, I've had large GIFs look good in the editor and feel sluggish in the actual inbox. In Substack, the bigger issue is workflow. Dropping in a GIF is easy, but dialing in the size and crop takes more trial and error than it should. LetterBucket has been the least fussy for me, mostly because I can keep the media block simple and test quickly.

I use GIFs for product demos, UI changes, before-and-after moments, and anything with an immediate visual payoff. I do not use them for generic talking-head clips. A nod, a blink, or a subtle hand movement rarely improves clicks. It just makes the email heavier.

When I use a GIF instead of a static image

My rule is simple. If a subscriber can understand the value of the video in under two seconds of motion, I test a GIF. If the clip needs setup, I stick with a static thumbnail and stronger copy.

Validity's guide on using video in email reports that animated GIF fallbacks with a play button can outperform a static image on engagement. That matches my tests. The best-performing GIFs are short, obvious, and silent. The weak ones try to show too much.

What I actually do:

• Cut to one moment: one interaction, one reveal, one reaction
• Keep the loop smooth: if the reset is jarring, the email feels broken
• Add a play button overlay: people still need the cue that clicking opens a video
• Check the first frame: some inboxes are clumsy with animation, so frame one still has to work as a thumbnail

File size decides whether the GIF is worth using

This is the trade-off that matters. Motion gets attention. Heavy files slow the email down and make the whole thing feel cheap.

As noted earlier, the GIF approach keeps compatibility high across inboxes if you optimize it properly. I keep GIFs short, compress them hard, and treat anything bulky as a miss. If the motion needs more time or more detail, I abandon the GIF and use a static image linked to the full video.

A good email GIF is a preview clip. It is not a miniature version of the whole video.

My workflow is boring on purpose. I export once at full quality, once at a smaller size, then send test emails to myself before choosing. In Ghost and LetterBucket, that process is manageable. In Substack and beehiiv, I've spent more time than I wanted tweaking a GIF that still lost to a clean thumbnail. That's why I do not default to motion. I use it when the movement itself sells the click.

Advanced Options HTML5 and AMP for Email

I test HTML5 video and AMP every so often so I can keep giving the same advice with a straight face. For almost every newsletter, they are too much work for too little return.

The problem is not the code itself. The problem is platform support, editor restrictions, and the time you burn troubleshooting a version that only a slice of subscribers will ever see.

The only HTML5 setup I bother with

If I want to try native playback, I keep it simple. I use a plain HTML5 <video> tag, add a poster image, and assume the fallback will carry the experience for many inboxes.

<video controls poster="thumbnail.jpg" width="100%">
  <source src="video.mp4" type="video/mp4">
</video>

That setup is the ceiling of what I recommend, not the starting point. Some email clients still ignore parts of the video tag or strip the behavior you expected. If your poster image is weak, the whole block falls apart. If your fallback is missing, the send looks broken.

I learned this the annoying way while testing across Ghost, beehiiv, Substack, and LetterBucket. Ghost gives you the best shot because you can drop in custom HTML and inspect the result carefully. LetterBucket is workable if you are disciplined. Substack and beehiiv are where this usually stops being worth it, because the editor flow favors link previews and simple media blocks over custom email behavior.

HTML5 and AMP are advanced for a reason

Here is the practical trade-off:

HTML5 only makes sense if you already know your audience opens heavily in clients that support it, and your platform lets you control the markup. That is a narrow use case.

For a media brand with a technical team, fine. For a solo operator sending product updates, essays, or sponsorship-driven newsletters, it is usually wasted effort.

Why AMP stays off my list

AMP sounds better in demos than it feels in production. You get interactivity on paper, but you also get more setup, more testing, and more ways for the email to render inconsistently.

I do not want that overhead in a normal publishing workflow. I want something I can build once, test quickly, and trust on send day.

Platform friction matters here. Ghost can support more custom behavior if you are willing to babysit it. Substack is not built for this style of tinkering. beehiiv is faster for standard newsletter production, but that speed disappears once you start pushing advanced email markup. LetterBucket sits in the middle. Flexible enough for simple custom workflows, still not where I would build an AMP-heavy process.

My rule is simple.

Use HTML5 video only as an extra layer for supported inboxes. Skip AMP unless email engineering is already part of your operation. For everyone else, the advanced option is the one you can test fast, repeat weekly, and trust not to break.

How I Embed Videos in Ghost Substack and LetterBucket

The platform matters more than most guides admit. Generic HTML snippets are fine, but your actual editor decides how annoying the workflow will be.

Ghost gives me the most control

Ghost is still my favorite if I want full control over how the email block behaves. I use the HTML card when I want a custom linked thumbnail, and I can usually get exactly what I intended without the editor trying to outsmart me.

That control comes with extra responsibility. I have to test both the post and the email rendering. A small spacing issue inside Ghost can look fine on the web and slightly off in the inbox. Still, if I'm running a polished product update or a sponsor-sensitive send, I'd choose Ghost over the simpler editors because it lets me keep the presentation tight.

The annoyance is speed. Ghost is not the fastest option when I just want to paste a link and move on.

Substack and beehiiv are faster but looser

Substack and beehiiv both make the quick version easy. Paste a YouTube link, let the editor generate a preview-like block, send it. That's convenient, especially when the alternative is manually building a thumbnail every time.

I don't love the loss of control, though. The auto-generated visual isn't always the frame I'd pick, and when the thumbnail is mediocre, clicks usually suffer. For fast creator updates, I can live with that. For a launch email, I usually can't.

My rough rule:

• Substack: best when I want speed and don't care about pixel-level control.
• beehiiv: good for growth-focused newsletters, but I still prefer custom image handling for important sends.
• Ghost: best when design control matters.
• LetterBucket: the most comfortable middle ground for me lately.

How I handle LetterBucket and Outlook segments

I use LetterBucket in my own stack because it lets me keep things simple without boxing me into an overly opinionated editor. I can build the linked-thumbnail flow I want without fighting the composer. That said, I've hit a few little annoyances with spacing and image alignment during draft edits, especially when I revise the email late. Nothing catastrophic. Just the kind of friction you notice when you send often.

For creators deciding between the main platforms, I'd choose Ghost if you care most about control, LetterBucket if you want a practical editor that doesn't get in your way as much, and Substack if you want the fastest publishing flow and can tolerate less control over presentation. beehiiv sits in the middle for growth operators, but for video specifically, I still end up doing custom workarounds.

There's one niche exception worth knowing if you send to corporate audiences. Microsoft's Outlook discussion lines up with what I tested: only Microsoft Stream and OneDrive links expand natively in Outlook, while YouTube and Vimeo links do not. In my own Outlook-specific segment, switching to OneDrive links reduced redirect clicks by 35%.

That's not my default workflow because it's too narrow. But if a meaningful chunk of your list lives in Outlook at work, it's worth segmenting for.

Different platforms don't just change how fast you build the email. They change how much control you keep over the click.

Your Video in Email Questions Answered

This is the part busy operators usually want anyway. What should you do, and what should you avoid?

What I'd choose for different newsletter jobs

If I'm sending a normal newsletter, I use a linked thumbnail. If I'm promoting something visual, I test a GIF. If I'm sending to a very specific Apple-heavy audience and feel like experimenting, I'll layer in HTML5 with a fallback. That's the full playbook.

I do not recommend attaching the video file directly for most sends. GlockApps' guide to embedding video in email says attaching a video file directly can result in a 200–300% increase in click-through rates, but only if the file is under 1 MB and in MP4 format. It also notes that most email clients block it, which is why the linked thumbnail remains the most reliable method.

That trade-off isn't worth it for most creators. The attachment approach is fragile, file-size constrained, and more likely to create weird delivery or rendering problems than a clean linked image.

A simple decision filter:

• Use a linked thumbnail if you want reliability.
• Use a GIF if motion materially improves the preview.
• Use HTML5 only if you know your audience and you enjoy testing edge cases.
• Use Outlook-specific Microsoft links only for corporate segments where that exception matters.

How I track whether the video actually worked

I don't stop at email clicks. Clicks tell me the thumbnail did its job. They don't tell me whether the video itself held attention.

My usual review is simple:

1. Email click data inside the newsletter platform.
2. View behavior inside YouTube, Vimeo, Loom, or wherever I hosted the clip.
3. Post-video action on the landing page or CTA destination.

If click-through is healthy but watch behavior is weak, the email did its job and the video didn't. If clicks are weak, the thumbnail, framing, or CTA probably needs work.

The cleanest answer to how to embed a video into an email is also the least glamorous one. Don't fight the inbox. Use the email to earn the click, then let the video play somewhere built for video.

If you want more tested newsletter tactics like this, I share them at Grow and Monetize Your Newsletter, where I write from actual sends, migrations, and platform experiments instead of generic marketing theory.