Choose a GIF
Add a non-empty .gif file of 100 MB or less that host FFmpeg can read.
Free online GIF to animated WEBP
Fileverses uses server-side FFmpeg to take a qualifying GIF’s first video stream and write a new animated WebP at the route’s fixed quality setting.
Processed by our self-hosted conversion engine
Supported files
The output is a newly encoded looping WebP animation, not a static image or a renamed GIF. Audio is not part of either conversion output.
How it works
Add a non-empty .gif file of 100 MB or less that host FFmpeg can read.
The sequential server queue maps the first GIF video stream and encodes it with the animated WebP profile.
Review the completed animation where browser support allows and download the separately named .webp file.
Animation processing facts
The profile uses libwebp_anim at quality 75 with infinite looping. Metadata and chapters are removed, and no animation-editing controls are offered.
Make animated WebPThe route accepts non-empty .gif uploads up to 100 MB, subject to host FFmpeg being able to read the source.
The profile writes animated WebP with libwebp_anim at quality 75 and loop count zero, meaning continuous looping.
Only the first video stream is mapped. Audio is excluded, and metadata, chapters, alternate streams, subtitles, and attachments are not retained.
There are no trim, crop, resize, frame-rate, palette, quality, or loop-behavior controls. File size and appearance are not guaranteed.
GIF to WebP FAQ
A successful conversion produces animated WebP from the first GIF video stream; it is not a static WebP export.
Yes. The fixed profile uses loop count zero, which denotes continuous looping.
The profile uses FFmpeg’s libwebp_anim encoder at quality setting 75. There is no control to change it.
No. This route produces an image animation only and excludes audio.
No. The route has no trim, crop, resize, frame-rate, palette, quality, or loop controls.
No. Only the first video stream is used; source metadata, chapters, subtitles, attachments, and alternate streams are not retained.
There is no size guarantee. It is a new encode, so size and visual output should be checked before publishing.