Every embed goes still in the email, except one
Substack gives an article two ways to hold video, and both go still in the email. Paste a YouTube, TikTok, or Spotify link and subscribers get a static image that links out. Upload a clip through the video icon and they get a thumbnail; the click lands on the web post or the app. Substack documents both, and it never bets on inbox video support, because no set of mail clients has ever agreed on one.
A GIF is exempt because Substack files it under images. Drag it into the draft or pick it with the Image icon, same as a JPG (the accepted list is avif, gif, jpg, jpeg, png, webp), and it rides the email as a plain image tag. Wherever the reader's client animates GIFs, which is nearly everywhere, the loop plays before anyone taps a thing. That's the whole trade: a GIF is the only motion in the email, and it pays for the privilege in kilobytes.
The truncation warning is about markup, not your GIF
Write long enough and the editor warns that your post may be truncated in some email clients. That's Gmail's roughly 102KB ceiling on message HTML, and Substack says so plainly: no post length limit on their side, you can still publish, and clipped readers get a View entire message link. GIF bytes don't spend against that ceiling. Images are hosted and linked, not stuffed into the markup, so formatted text trips the warning and a 3 MB loop doesn't.
The loop's bytes decide something else: whether the post feels broken on a phone with one bar. Hold to roughly 1 MB, or 500 KB for anything above the fold. Substack's help center publishes no per-image cap (third-party spec sheets put it near 10 MB as of this writing), so the inbox is the real cap, and the inbox is a subscriber's data plan.
One more: classic desktop Outlook, 2007 through 2019, renders mail through Word and shows frame one only. Open on a frame that stands alone; the Outlook guide runs the audit.
Cutting the loop to newsletter weight
Bring the clip to the converter (on desktop, Record a Tab captures another tab or window when the footage is a screen), then:
- Two to four seconds. Cuts are frame-exact; open on the motion, stop before lap three drags. Subscribers see the loop run forever.
- Crop for the column. 16:9 or 4:3 fills the width; 1:1 sits beside prose. Never taller than square, since Substack auto-crops full-width images to 1:1 and a 9:16 loop loses its top and bottom.
- Scale to 600 to 700 px wide. Community measurements put the web column near 730 and the emailed one narrower, roughly 680; Substack publishes neither number. Extra pixels cost on every frame and never get seen.
- 10 or 12 fps, 64 to 128 colors. Product footage moves at 12; interface captures hold at 10.
- Watch the estimate. If it's stubborn, Extra Compression at Medium usually cuts the file by a third to a half for a little grain.
Captions bake into the pixels, so a headline rides the frozen frame too; leave both timing fields empty and the caption holds for every frame. There's a Substack-specific bonus. Emails go out in email-safe fonts, per Substack's own note on test sends, so a custom web font falls back to a system face in the inbox. Type baked into a GIF keeps the typeface you chose. Skip MP4 and APNG for this job; the inbox wants a GIF.
When Substack's own video is the better call
Substack's video tools are good, and a GIF beats none of them at their own jobs:
- The clip is the content. A ten-minute walkthrough belongs in a video post, with its transcript, podcast feed, in-app player, and free preview for paid subscribers. Substack will take a 20 GB upload; a GIF that long would be a crime.
- You said something. GIF carries no audio. Narration, music, an interview: video.
- It sits beside 2,000 words. A loop can't be paused; beside long reading it's a fidget in the margin.
- The pixels must stay perfect. Gradients and skin band at 256 colors. A sharp still beats a muddy loop.
The GIF wins one narrow case: a two-second reveal inside the email, no click. Worth winning. Not every case.
The paywall starts on your hard drive
A draft is unpublished by definition, and a paid post's clip is what subscribers pay for. Upload it to a converter and it sits on a stranger's server before your first paying reader sees it.
This converter reads the file off your disk, runs it through your processor, and writes the GIF to your Downloads folder. No server appears in that sentence because none is in the pipeline; the embargo holds until you press send. Same custody for a Gmail-bound loop, different dials.