B2B lists carry the oldest inboxes
HubSpot handles the mechanics: a GIF goes into an image module and ships with animation intact. But HubSpot lists lean B2B, and B2B addresses terminate at corporate desktops where classic Outlook (roughly the 2007 to 2019 releases, rendered by Word's engine) hangs on for years. Those installs display a GIF's first frame and nothing after it.
The rest of the field animates as of this writing: Gmail, Apple Mail, and every current Outlook (new desktop, web, mobile), so most readers do get the motion. The design job is serving both groups from one file: animation for the many, a competent still for the Word-engine minority you can neither detect nor exclude. Neither audience forgives; they just fail differently.
Decide the numbers before the export exists
Set targets first and make the GIF conform; retrofitting weight out of a finished export wastes an afternoon. All figures approximate, because platforms shift them:
- Around 1MB, treated as generous. ESP guidance, HubSpot's included, hovers near a megabyte per image, and heavy sends erode deliverability at the margin.
- Roughly 600 to 640px of width, matching the standard email column. Beyond that, the template scales down pixels you paid weight for.
- 10 to 12 fps. Demo motion stays readable, frame count stays sane.
- 64 to 128 colors. Screen recordings compress into a small palette remarkably well.
- 2 to 4 seconds, looping. One point, made repeatedly.
- Gmail footnote: message HTML past roughly 102KB gets clipped. The GIF's bytes don't count toward it, but module-heavy templates do.
The first frame is the version of record
For the frozen-Outlook contingent, frame one is the entire campaign. Treat it like a static banner that happens to move for everyone else: headline legible, product identifiable, reason to click intact at second zero. Animations that build to a reveal punish exactly the readers B2B senders most want to reach. A fair test: screenshot the GIF's opening frame and ask whether you'd approve it as a static banner. If not, recut.
Overlays keep this honest. Up to three text captions fit on a GIF, clean type in any picked color or meme style if your list would smile at it, and a caption without timing occupies the whole loop, frame one included. Use timed reveals only for lines you can afford the freeze crowd to miss.
Produce it locally, which legal will appreciate
Feature demos headed for a customer list are usually recorded before launch. Bring the screen capture to the converter (mp4, mov, webm; if the browser can decode it, it loads) and the processing happens on your machine. There's no account to sign up for, the export ships without a watermark, and, more to the point, no third-party server ever holds a copy of an unannounced feature.
Trim to the tightest loop that demonstrates the point; the arrow keys nudge either end of the trim a frame per keystroke. Crop 16:9 for a hero module or 1:1 beside text, downscale toward the 600px column, then work fps, colors, and dithering while the forecasted file size tracks each dial. A short workflow can become a mini tour: up to ten clips can join end to end in a single GIF, hard-cut at each seam, each keeping independent trim and crop. Still heavy? The small-GIF playbook ranks the remaining levers.
Test like the send matters, because it does
In HubSpot's editor, insert the GIF as a normal image and give it real alt text, one sentence that survives total image blocking. Expect infinite looping in most clients, so choose motion that tolerates repetition.
Then run the paranoid checklist: a test to Gmail (its proxy serves your image from Google's cache), one to Outlook.com, and if anyone in the company still runs classic desktop Outlook, that machine is your best QA rig. Confirm frame one sells unaided and the animation doesn't strobe. The Outlook guide is worth ten minutes before a large send. It sounds like overkill until the first time a VP forwards your frozen GIF back with a question mark.