GIF → WebP
Converting locally — nothing is uploaded
The same still, decades lighter — free, and finished on your machine.
Drop your GIFs in the drum
or — nothing leaves this tab
READS JPG · PNG · WEBP · GIF · BMP · SVG · AVIF
CYCLE →
WASH TEMP
OUT OF ORDER — JAM REPORT
The GIF → WebP cycle
The quiet migration path: pull a still from a legacy GIF and ship it as WebP. Same picture, modern weight, transparency handled.
WebP keeps transparency; GIF had none to give. Expect the folded copy noticeably lighter than the load. Either way, re-encoding through the canvas collects EXIF like lint — camera model, GPS coordinates and timestamps are stripped from the folded copy.
Need the other direction? WebP → GIF · Other routes into JPG → WebP, PNG → WebP, BMP → WebP.
Questions at the counter
Why convert GIF to WebP at all?
Weight and colour depth together: the WebP still typically lands far smaller than the source GIF, and escapes the 256-colour ceiling entirely if you re-source richer artwork.
First frame only?
Correct — stated up front rather than discovered later. This is a stills machine; animated WebP output is deliberately out of scope.
Is transparency kept?
Hard-edged GIF transparency converts to true alpha. Soft edges the GIF dithered against white carry that white history with them — the wash cannot unmix paint.
Is the conversion really private?
Yes — architecturally. This page is static files; there is no server to receive an upload. Your GIF is decoded and re-encoded inside this tab by your own machine, and you can watch the absence of network traffic in your browser’s developer tools.