How to share a GIF or screen recording as a link

A ten-second GIF of a bug can easily be 12 MB. The same clip as a video is under 400 KB and looks better.

Sharing a short recording as a link means putting it on a page and sending the address, with a caption saying what to look at.

The first decision is the format, and it is not the one the filename suggests.

A looping screen recording on a page, with a caption beneath explaining what to watch.
A looping screen recording on a page, with a caption beneath explaining what to watch.

This guide covers why GIF is the wrong format, making a video behave like one, keeping the file small, and what to offer alongside.

GIF is expensive for exactly this case

The format dates from 1987. It stores each frame as an indexed image limited to 256 colours, with only minimal compression between frames.

A screen recording is mostly unchanging: a window, a page, a cursor moving. Modern video codecs are built to encode that almost for free, because they describe what changed rather than each whole frame. GIF cannot, so it pays full price for every frame.

Ten seconds of screen recording Typical size Colour
GIF, 15 fps 8-15 MB 256 colours, visible banding
MP4, H.264 200-500 KB Full colour
WebM 150-400 KB Full colour

The colour limit is the other cost. A GIF of a screen with gradients or antialiased text shows banding and dithering, which looks worse than the thing you recorded.

Make a video behave like a GIF

Four attributes and the viewer cannot tell the difference.

<video autoplay loop muted playsinline
       poster="/rec/bug-still.webp"
       width="960" height="600">
  <source src="/rec/bug.webm" type="video/webm">
  <source src="/rec/bug.mp4" type="video/mp4">
</video>

Muted is not optional. Browsers block autoplay with sound, so a video that is not muted simply does not start.

The playsinline attribute stops phones taking the video full screen, which would otherwise break the illusion entirely.

The poster image shows while the video loads and is what appears if it fails, so choose the frame that best shows the point.

More on the pattern in embedding video with autoplay and loop.

Record only what matters

The largest saving is not the codec. It is length.

Most shared recordings run four times longer than they need to, because the recording started before the relevant thing and stopped after it. Three seconds showing the failure is more useful than thirty seconds of navigating to it, and a fraction of the size.

Crop the frame too. A recording of one dialogue box does not need the whole desktop, the dock, and your other windows, which also avoids showing what you did not intend to show.

Caption it

A recording without a caption makes the viewer watch the loop three times trying to work out what they are meant to notice.

One line underneath: what to look at and what is wrong with it. "Watch the total on the right. It updates on the second click, not the first."

That sentence saves everyone the three loops, and it is searchable text where the recording is not.

The same recording offered as a still frame, showing the moment that matters.
The same recording offered as a still frame, showing the moment that matters.

Offer a still as well

Some people cannot use animation comfortably, and some are reading in a situation where a loop is unhelpful.

A still frame of the important moment covers both, and it is also what people want when they need to look at something properly rather than watch it pass.

Where motion matters but autoplay does not, respect the system setting for reduced motion.

@media (prefers-reduced-motion: reduce) {
  video { display: none; }
  .still { display: block; }
}

Chat clients cap attachment sizes, and a 12 MB animation often does not send at all. Those that accept it recompress, which for an animation of text is destructive.

A link is fetched once at the quality you saved. Fifteen recipients get fifteen identical viewings rather than fifteen recompressions, and the caption travels with it.

Related: screenshot link for the still-image case, and HTML animation to GIF if you specifically need the format.

Sending the file itself ✗ Often filtered by mail security rules ✗ May open as plain text on a phone ✗ Every fix means a new attachment ✗ No way to know who opened it ✗ Recipient needs the right app Sending a link ✓ Passes through mail and chat ✓ Renders in the phone browser ✓ Fix once, link stays the same ✓ The address is the single source ✓ Any browser is enough
Sending the file itself against sending an address: what each costs the reader.

When GIF is still right

Two cases, both narrow.

Somewhere that genuinely will not play video: a few email clients, some older systems, certain forum software. And very short animations of a handful of frames, where the format overhead is not worth avoiding.

Everywhere else, the video is smaller and looks better.

Put it at an address

Record only the part that matters, export as MP4, set it to autoplay muted and loop, caption what to watch, offer a still, and create a share link.

It loads instantly and arrives looking like what you recorded.

Questions people ask

Why are GIF files so large?

Because the format is from 1987 and stores frames as images with a 256-colour palette, with almost no compression between frames. A screen recording, which has large areas that do not change, is exactly the case a modern video codec handles well and GIF handles worst.

Should I use a video instead?

For anything longer than two or three seconds, yes. An MP4 that loops silently behaves like a GIF to the viewer and is typically twenty to forty times smaller with better colour. The only reason to keep GIF is somewhere that will not play video.

How do I make a video behave like a GIF?

Autoplay, loop, muted, and inline playback. Those four attributes together produce something the viewer reads as an animation rather than as a video, with no controls and no sound. Muted is required, as browsers block autoplay with sound.

Why send a link rather than the file?

Messaging apps recompress and often refuse large animations, and chat clients cap attachment sizes. A link is fetched once at the quality you saved, however many people open it, and the caption explaining what to look at can sit beside it.

Does it need a still image as well?

Yes, for anyone who cannot or does not want to see motion. Offer a still frame of the important moment. Some people have motion sensitivity, and some read in contexts where animation is unhelpful.

Keep reading