Images to WebP
Combine multiple images into an animated WebP in upload order — far smaller than GIF at the same quality. All processing happens locally in your browser; files never leave your device.
$Drag in multiple images, or click to select
Supports JPG / PNG / WebP — images are combined in order into an animated WebP
Images are read into browser memory — nothing is uploaded
Frame rate, output width and quality
FFmpeg WASM assembles the animated WebP locally
Images to Animated WebP Converter Online Free
Local · No uploadsCombine multiple JPG, PNG, or WebP images into an animated WebP in upload order, with control over frame rate, output width, and libwebp quality. Animated WebP is far smaller than GIF at the same quality — great for memes, web assets, and lightweight sharing. Everything is processed in your browser; nothing is uploaded.
Quick Answers
- JPG, PNG, and WebP images become animated WebP frames in upload order; each image shows for 1/fps seconds, with 5–10 fps typical.
- Encoding uses libwebp with quality 0–100: 60 favors smaller files, 75 is balanced, 85+ leans toward visual fidelity.
- Animated WebP runs about 64% smaller than GIF on average for the same content (Google libwebp study), and every modern browser plays it natively.
- Mixed sizes are auto-cropped into one canvas: the tallest scaled image sets the height and the rest are letterboxed — no cropping or distortion.
- Conversion runs in your browser via FFmpeg WASM — free, no watermark, no sign-up, nothing uploaded.
How to Make an Animated WebP from Images
- 1
Upload multiple images in playback order — drag and drop works
- 2
Choose the frame rate, output width, and encoder quality
- 3
Click Create, then download the animated WebP
Common Uses
- Turn image sets into smaller meme animations
- Create lightweight animated assets for the web
- Assemble screenshot sequences into demo animations
Things to Keep in Mind
- At least 2 images are required; more images and larger sizes mean longer processing
- Some older apps and platforms do not accept animated WebP — use Images to GIF when compatibility matters
- Images shorter than the tallest frame are letterboxed in the center
How to Choose an Image-to-WebP Tool
- vs. Images to GIF: WebP keeps full color and compresses between frames, so files are much smaller
- vs. manual frame assembly: automatic canvas fitting and ordered combining, no specialized software
- vs. upload-based tools: nothing is uploaded — private and secure
Why Animated WebP Beats GIF on Size
- Each image becomes one input shown for 1/fps seconds; a concat filter chains the frames and libwebp encodes the animated WebP.
- concat requires identical frame sizes: canvas height comes from the tallest image scaled to the target width, and other aspect ratios are letterboxed.
- WebP uses VP8 intra/inter compression with full color and no 256-color cap, so animated files are usually far smaller than GIF.
- Size benchmark: animated WebP averages about 64% smaller than GIF for the same content (Google data); this page defaults to 5 fps, 480px wide, quality 75.
Images to WebP FAQ
Which image formats are supported?
JPG, PNG, and WebP — you can mix them in one upload; the animation follows upload order.
Can browsers preview animated WebP?
Yes. Chrome, Edge, Firefox, and Safari 14+ support animated WebP; the result plays right on the page.
What does frame rate mean here?
Each image displays for 1/fps seconds: 2 fps suits slow slideshows, 10+ fps feels smooth. Custom 1–30 is supported.
Can I mix different image sizes?
Yes. Canvas height follows the tallest image scaled to the target width; others are scaled and letterboxed without cropping.
Are my images uploaded anywhere?
No. The conversion runs locally in your browser via FFmpeg WASM — your images never leave your device.
How much smaller is WebP than GIF?
About 64% smaller on average for the same content (Google libwebp study); richer colors widen the gap.
How do I control how long each image shows?
Frame rate sets it: each image displays for 1/fps seconds — 2 fps means half a second per image, 10 fps means 0.1 seconds. Custom 1–30 is supported.
Does it support transparent backgrounds?
WebP itself supports transparency, but mixed-size inputs are letterboxed onto an opaque background — use same-size assets to keep alpha.