The rare email client that just plays the thing
Apple Mail, on macOS, iPhone, and iPad, treats an animated GIF exactly how you'd hope: it loads, it loops, no play button, no frozen still. If you've spent time fighting classic desktop Outlook, which shows only the first frame, this feels like a vacation. And by most counts Apple Mail handles a very large share of all email opens, so a GIF in Apple Mail isn't an edge case, it's the main event.
One caveat before you celebrate: the same email lands in other inboxes too, so keep frame one able to carry the whole message on its own. That discipline costs you nothing in Apple Mail and saves you everywhere else. With playback handled, the real work is making the GIF look like it belongs on an Apple screen, and that comes down to three things: pixel density, dark mode, and weight.
Retina math: export at 2x, let the width settle
Nearly every screen Apple Mail runs on is a 2x or 3x display. If you export a GIF at 600 pixels wide and display it at 600 points in your email, each image pixel gets stretched across four device pixels, and the whole thing goes soft. It's subtle on b-roll and brutal on anything with text or UI in it.
The fix is old-school retina practice: export at twice the width you'll display, then set the HTML width attribute (or your email builder's width field) to the display size and let the pixels settle into place. A GIF meant to sit 300 pixels wide gets exported at 600. The catch is cost: doubling the width roughly quadruples the pixel count, so a full-width 600-pixel slot means a 1200-pixel export, and the file balloons. Spend the 2x where sharpness is actually visible, which means captions, product UI, and screen recordings. Soft lifestyle footage forgives 1x, and 1.5x is a legitimate compromise when the budget is tight.
This matters double if you're putting text on the GIF. A caption rendered into a 1x export smears on a retina screen. Rendered at 2x and displayed at half width, it snaps into focus like native type.
Dark mode doesn't change your pixels, and that's the problem
When a recipient reads in dark mode, Apple Mail flips the message chrome to near black, and depending on the build it may adjust background colors in your HTML too. Your GIF gets none of that treatment. It's baked pixels. A clip with a white background that looked native on a white email now floats on the dark canvas as a bright glowing slab.
There's a second, sneakier failure: GIF transparency is one bit. A pixel is either fully opaque or fully gone, so any anti-aliased edge keeps a fringe of whatever color it was rendered against, and that halo lights up against a dark background. The practical rules:
- Skip transparency entirely. Bake a deliberate background into the GIF so it reads as an intentional card in both light and dark mode.
- Crop tight. A GIF that fills its own frame with footage has no edges to betray it. The ratio-locked crop (16:9 for a wide slot, 1:1 for a card) gets you there.
- Caption in the classic style. White fill with a black outline reads on any background, which is exactly why meme text has looked that way for twenty years. It's dark-mode-proof by accident.
Cellular is the size cap Apple never wrote down
Apple Mail won't clip your message the way Gmail trims HTML over roughly 102KB (and that limit is markup, not image bytes, anyway). There's no posted GIF ceiling either. The real cap is human: a huge chunk of Apple Mail opens happen on an iPhone, and plenty of those are on cellular. A 6MB GIF that loads instantly on your office fiber is a spinning placeholder on LTE.
So hold the usual email line: keep the GIF roughly 1MB or under, and the further under you land, the kinder you are to the reader on two bars. Total email weight also plays into deliverability, so the GIF budget isn't just about patience. The levers, in order of power: trim the loop to 2 to 4 seconds, drop the frame rate to 10 to 14 fps, and pull the palette down to 64 or 128 colors with dithering to cover the gradients. The live estimated output size updates as you pull each one, so you're never exporting blind. Remember to double-check after the retina export bump, since 2x is where good budgets go to die.
The whole build happens in your browser
Open What the GIF and drop in your source video. If the footage came off an iPhone, the .mov drops straight in, no conversion detour. Everything runs client-side in the tab, so nothing uploads: your clip never touches a server, and a 400MB 4K screen recording doesn't crawl through an uploader before you can start trimming.
From there it's the drill from above: trim frame-accurately (arrow keys nudge a single frame at a time, so the loop point lands exactly), crop to a locked ratio, do the 2x scale math, tune fps and colors until the estimate behaves. If you're teasing something with multiple beats, you can sequence up to three clips into one GIF with hard cuts, and the output size follows the first clip. Three quick product angles in a single four-second loop beats three separate images stacked in a template. Two last habits: write alt text, because some recipients block remote images, and assume infinite loop, so pick a cut that's still charming on the tenth pass.