GIF to WebP Converter

This is the conversion that makes a GIF worth keeping

A GIF is an unusually inefficient animated format. It stores every frame as a palette of up to 256 colours, it has no partial transparency, it has no audio, and the compression between frames is very limited. An animated WebP or AVIF achieves the same motion in a small fraction of the space, with full colour and smooth transparency. Converting to animated WebP is therefore the one conversion of a GIF that is a clear improvement rather than a compromise, which is why it is the recommended route for any animation that is still in use.

NoteAnimated WebP keeps the motion in a fraction of the space. This is the one GIF conversion that improves the file.

What the conversion can and cannot repair

Converting fixes the format, and it fixes it completely, but it does not repair an animation that was badly made at the source. A GIF with visible dithering has that dithering baked into its pixels, and it survives the conversion. A GIF that loops too quickly keeps that timing, because the timing is carried over rather than reinterpreted. A GIF that was authored at a small size stays small. If the original was low quality, the output is a better file containing the same imperfect animation.

• Dithering and palette banding in the source are preserved.
• Frame timing is carried over, not reinterpreted.
• A small source stays small. Resize the source first if that is a problem.
• The output is a better file holding the same imperfect animation.

NoteThe conversion fixes the format, not the source. A poor GIF becomes a better file of the same animation.

Frame count and canvas size drive the file

Animation length is the single biggest factor in the output, because every frame is stored rather than calculated as a difference from the one before. A GIF that plays once and then holds still can often be trimmed, and the saving is proportional. A smaller canvas also reduces the file, so reducing the dimensions helps twice over. If a GIF is unexpectedly large after conversion, the frame count and the canvas are the two things to check, not the format.

• Every frame is stored, so frame count drives the file size.
• Trim a one-time animation rather than converting a long loop.
• A smaller canvas reduces the file as well.
• If the output is still large, check frames and dimensions, not format.

When a single still frame is what you want

Sometimes the animation is incidental and the file is only being converted because something rejected the GIF format. That is a legitimate reason to export one frame instead, and a PNG is usually the better output for a static result, since it is universally supported and cheap. The distinction is whether the motion is part of the content or an artefact of how it was stored. A loading spinner needs the motion. A banner that happens to have been a GIF does not.

• The motion is the content: keep it with animated WebP or AVIF.
• The motion is incidental: export one frame.
• For a still result, PNG is usually a better output than WebP.
• A loading indicator must stay animated. A static banner need not.