Cookies for analytics and advertising
We use cookies for analytics and advertising, both sent to Google. Refusing changes nothing you can see.Read the privacy page
Converting GIF to WebP replaces a compression scheme from 1987 with a modern one and gives you a real alpha channel instead of GIF’s hard one-bit edges — often less than half the size on a detailed image. Note before you start: this produces a still, so an animated GIF keeps only its first frame.
Up to 100 files at once. Mixed formats are fine.
They convert one after another and download together as a ZIP.
GIF to WebP






Said plainly and first, because it is the one thing that would otherwise be discovered after the download. This conversion produces a still picture from the first frame. Everything after it is dropped.
For a moving GIF the right target is video. Converting GIF to MP4 keeps every frame, plays on every device, and usually comes out at a fraction of the size — a video codec describes what changed between frames, where GIF stores each one almost from scratch. A three-megabyte GIF routinely becomes a two-hundred-kilobyte MP4 that looks better. If you came here with an animation, go there instead.
Nobody chooses GIF for a static image today, and yet sites are full of them: spacers and bullets from a decade-old theme, diagrams exported by software that offered nothing else, screenshots from an era when GIF was the safe choice, logos that have been copied from one redesign to the next since 2009.
They are the images a performance audit finds and nobody has ever looked at. Converting them is uncontroversial precisely because nothing about them is deliberate — the format was an accident of when the file was made.
GIF compresses with LZW, a general-purpose scheme from the 1980s that knows nothing about pictures. WebP was designed for images specifically, twenty-three years later, and applies techniques borrowed from video compression to a single frame.
On a detailed still GIF the result is dramatic — half the size or less is normal, and a photograph that was mistakenly saved as a GIF can lose far more than that. The exception is the very small flat graphic: a two-colour bullet is already close to the floor, and there is nothing left for a better codec to take away.
This is the quality improvement that people notice. GIF transparency is a single bit: each pixel is either completely transparent or completely opaque, with nothing in between. That is why a cut-out GIF logo has stair-stepped edges and a faint fringe of whatever colour it was designed against.
WebP carries a real alpha channel with 256 levels, so edges can fade properly and a mark can sit on any background. The conversion cannot invent smoothness the GIF never had, but it removes the ceiling — and if you re-export the artwork from the original at some point, the WebP will be ready to hold it.
A GIF holds at most 256 colours, chosen when it was created. WebP holds millions, so every one of them fits with room to spare and the conversion has nothing to discard.
What it cannot do is undo the original reduction. If a photograph was flattened to 256 colours in 2011, the banding across the sky is part of the picture now and the WebP will reproduce it faithfully. Converting changes the container and the compression, not the history of the file.
For anything served on a web page, WebP: smaller, better transparency, and supported by every current browser including Safari.
PNG when the file leaves the browser. Email attachments, files handed to a client, images going into other software or an archive — PNG is the one everything opens. Both are lossless enough for this kind of image that the choice is about the audience rather than the quality.
Old GIFs come in bulk or not at all. Drop the entire folder: each converts in turn on your own machine with its own progress, keeps its name with the extension swapped, and everything returns as a single ZIP.
Keep the originals somewhere until the site has been through a round of testing. Sites of this vintage occasionally reference a GIF from somewhere nobody remembers — an email template, a stylesheet, a cached theme file — and the missing image will not be obvious until somebody looks at the right page.
The conversion runs inside the browser tab on your own processor. Nothing is uploaded, so there is no queue and no daily count, and the ceiling is the free tier’s 100 MB per file — which is what makes dropping a hundred legacy images at once practical rather than an afternoon of waiting.
Watching the network tab while a batch runs is the honest way to confirm it: no request carrying a file leaves the machine.
| GIF | WebP | |
|---|---|---|
| Full name | Graphics Interchange Format | WebP Image |
| File extension | .gif | .webp |
| Media type | image/gif | image/webp |
| Compression | Lossless — nothing is discarded | Either, depending on the setting |
| First published | 1987 | 2010 |
| Published by | CompuServe | |
| Specification | GIF89a | RFC 9649 |
| Licensing | Open standard | Open standard |
| Standing today | Legacy, still read everywhere | Current |
| Bit depth | 8 | 8 |
| Colour it can describe | indexed palette | RGB, YCbCr |
| Largest image | 65,535 px per side | 16,383 px per side |
| Opens in a browser | Every browser | Every browser |
| Considered instead | MP4 | AVIF, JPG, PNG |
Transparency survives. Both GIF and WebP store an alpha channel, so a cut-out stays cut out and nothing is filled in behind it.
Animation survives. GIF and WebP both hold multiple frames, so the result moves rather than freezing on the first one.
GIF dates from 1987 and is largely superseded. WebP is what current software writes, so the conversion is as much about staying readable as about the file itself.
GIMP and Adobe Photoshop read both GIF and WebP, so there is a way to check the result against the original without a second tool.
GIF is CompuServe's format, published in 1987. It records 8 bits per channel.
WebP comes from Google and dates from 2010, specified as RFC 9649. Adobe Photoshop, GIMP and Squoosh all read it.
GIF was published in 1987 and WebP in 2010. The older one is generally the safer file to hand to somebody; the newer one usually does the job in fewer bytes.
No. This conversion runs entirely inside your browser, so the file never leaves your device. You can confirm it yourself: open the network tab of your browser's developer tools and convert something. You will see the page load, plus the analytics and advertising the site is paid for with — and nothing carrying your file. The engine behind this particular pair is jSquash, WebAssembly builds of the reference image codecs; your browser fetches it once and caches it.
No. This conversion takes the first frame and produces a still image. WebP does have an animated mode, but it is not what runs here — if the motion is the point, convert the GIF to MP4 instead, which keeps every frame and is usually far smaller than either.
Yes, and it improves. GIF transparency is one bit: a pixel is either fully see-through or fully solid, which is why cut-out GIFs have those hard jagged edges. WebP has a real alpha channel, so the edge can be soft — though it can only be as good as what the GIF already held.
It depends what is in the file, and the comparison above this text is measured rather than claimed. A detailed or photographic GIF commonly comes out at half the size or less. A small flat graphic — a bullet, a spacer, a two-colour icon — is already about as compact as it can be, and the WebP can come out slightly larger.
They cannot get worse. A GIF holds at most 256 colours and WebP holds millions, so every colour in the original fits comfortably. What conversion does not do is restore colours that GIF discarded when the file was made — the banding in an old GIF sky is baked in.
WebP for anything served on a web page: smaller, with better transparency. PNG when the file has to be opened by other software, emailed, or handed to someone whose tools might not know WebP.
Yes. Drop up to 100 at once — each converts on your own machine with its own progress, keeps its filename with the extension swapped, and the batch comes back as one ZIP. Nothing is uploaded and there is no daily limit.
The claims this page makes about GIF and WebP are checkable, and these are the documents that settle them.