Convert video to animated WebP

Turn a short video clip into an animated WebP, smaller than GIF, with real color and transparency, in your browser.

Drop your files here

.mp4, .mov, .mkv, .webm, .avi, .m4v · up to 200 MB

Choose files

How to Convert to WebP

1
Add your video
MP4, MOV, MKV, WebM or AVI, up to 200 MB; the clip itself is capped at 20 seconds.
2
Pick the clip, size and frame rate
Choose the start point and length, then a frame rate and output size that fit what you need.
3
Click Convert and download
The result is a silent, looping animated WebP sized for the settings you picked.

Why animated WebP beats GIF

GIF is stuck with a palette of at most 256 colors and no alpha channel beyond a single fully-transparent or fully-opaque pixel. Every frame gets quantized down to that palette before it is even compressed, which is why gradients band and photographic footage looks muddy. WebP encodes each frame with real 24-bit color and, when the source needs it, a genuine alpha channel with smooth partial transparency. Combined with a more modern per-frame compression scheme, the same clip at the same visual quality typically comes out a fraction of the size of the equivalent GIF, often 30-50% smaller and sometimes much more on footage with smooth gradients or soft edges where GIF's palette shows its age fastest.

Why there is no sound

Animated WebP is, like GIF, an image format at heart: its container has no audio track defined at all, so there is nothing to carry a soundtrack even if the source video has one. This is not a setting to switch on; it is a property of the format itself, and the same limitation applies to every animated-WebP or GIF tool anywhere.

Why clips are capped at 20 seconds

Every frame in an animated WebP is a small independent image, so file size grows in a straightforward way with duration and frame rate: a 20-second clip at 480p and 15 fps can already reach several tens of megabytes, and pushing that further at full resolution risks a file that takes a long time to build in the browser and is awkward to share afterward. The cap keeps this tool focused on short previews, reaction clips and product loops. For anything longer, trim the part that matters first, or export a compressed video file instead, which is built for exactly that.

Frame rate, size and looping

10 fps is a practical default for most short clips: motion reads as smooth enough without inflating the file, and going up to 20-30 fps roughly doubles or triples the size for the same duration. The size options scale the width down proportionally, and dropping to 480px or 320px is usually the biggest single lever on final file size, well ahead of frame rate or quality. Looping is set to repeat forever by default, matching how animated images are used everywhere; a fixed loop count plays the clip that many times and then stops on its last frame.

Every WebP frame is made on your device

Decoding the clip and encoding each frame of the animated WebP both happen in this tab, which is why the clip is capped at 20 seconds: your own processor does all the work. There is no upload, no account and no queue, and closing the tab clears everything that was loaded.

Frequently asked questions

Is animated WebP actually better than GIF?

For most footage, yes: true 24-bit color instead of a 256-color palette, smoother transparency, and noticeably smaller files at the same visual quality. The one trade-off is compatibility. GIF is supported everywhere images can appear, while a handful of older tools and some email clients still don't render animated WebP.

Why doesn't the result have sound?

Animated WebP has no audio track in its container at all, exactly like GIF. This is a property of the format, not something this tool could add by encoding harder.

What is the maximum length of a clip I can convert?

20 seconds. That keeps the resulting file size predictable and the browser-side encoding fast; longer source videos work fine, you just pick which 20-second (or shorter) window to convert.

Why not support longer clips like a real video?

Every frame of an animated WebP is stored as its own image, so file size scales with duration in a way real video codecs avoid by compressing motion between frames. Beyond a few tens of seconds, the file stops being practical to build in a browser tab or to share afterward, and a compressed video file is the better tool at that length.

What does the frame rate setting control?

It sets how many separate WebP frames are captured per second of the clip, independent of the source video's own frame rate. Lower values make smaller, choppier files; higher values look smoother but grow the file close to proportionally.

Does animated WebP open everywhere?

All current major browsers play it natively, and most modern chat apps, design tools and operating systems preview it correctly. A few older or niche viewers still expect GIF specifically; if you need playback everywhere, converting to GIF afterward is one click away.