Initializing... drag & drop files here
Supports: APNG, PNG
If your animated PNG has grown to several megabytes, you are weighing an image against a video. The short answer: keep APNG when the transparent background is the point and the loop is short; convert to WebM when the clip is long, heavy, or headed for a page where it can live in a <video> element. WebM re-encodes the animation with a VP-family codec and typically collapses the file size — at the cost of the alpha channel, which is composited onto a solid Background Color during the encode.
| Property | APNG (input) | WebM (output) |
|---|---|---|
| Type | Animated image | Video container (Matroska-based, royalty-free) |
| Steward | W3C — PNG Specification (Third Edition), a Recommendation since June 2025 | The WebM Project, backed by Google |
| Compression | Lossless DEFLATE only, every frame | VP8, VP9, or AV1 — lossy, motion-compensated |
| Transparency | Full 8-bit alpha channel | Not carried by this conversion — transparent pixels are filled with the Background Color |
| Audio | None — it is an image format | Vorbis or Opus supported by the container; an APNG source produces a silent file |
| Typical size for a 5-second loop | Megabytes | Often an order of magnitude smaller |
| Sits in HTML as | <img src="loop.apng"> |
<video src="loop.webm" muted loop autoplay playsinline> |
| Autoplay behaviour | Always plays; no user-gesture rules | Autoplays only when muted — which a silent conversion satisfies |
| Frame-accurate seeking | No | Yes |
| Browser support | ~96% of users: Chrome 59+, Firefox 3+, Safari 8+, Edge 79+ | ~96% of users: Chrome 25+, Firefox 28+, Edge 79+, Safari 16+ (12.1–15.6 partial) |
| Best for | Short transparent loops, stickers, UI micro-animation | Long loops, background video, anything where bytes matter |
<img> tag, a CSS background, an avatar upload field, a chat client that accepts PNG.<video> element.| Codec | Compression | Encode cost | Choose it when |
|---|---|---|---|
| VP8 | Good | Lowest | You want the fastest turnaround and the widest reach among older WebM decoders |
| VP9 | Better — noticeably smaller at the same quality | Higher | The usual pick for modern web delivery; supported by every current browser |
| AV1 | Best at low bitrates | Highest | Bandwidth is the binding constraint and your audience is on current browsers |
.apng onto the page or click "Add Files"; animated .png files work too, and each upload becomes its own WebM..webm. Uploads travel over an encrypted connection, run on our servers, and are deleted automatically after a few hours — no sign-up, no watermark.Not from this converter. The encode produces ordinary opaque video, and every transparent pixel is composited onto the Background Color — white unless you change it — before the frames are compressed. If the alpha channel is the reason the animation exists, stay in an image format: APNG to GIF keeps every frame plus a single transparent index, and APNG to WebP keeps a full 8-bit alpha channel on the first frame as a still image.
Some, by design. APNG is lossless — every pixel of every frame is stored exactly — while VP8, VP9, and AV1 are lossy codecs that discard detail your eye is unlikely to catch. At the Very High preset the difference is hard to see at normal playback speed, and it buys an enormous size reduction. If you need a pixel-exact archive, keep the original APNG as your master and treat the WebM as a delivery copy.
Yes. An animated PNG is detected as a frame sequence and decoded like a video source, so all frames are re-encoded with the delays stored in the file. You do not get a per-image duration control on this page because the animation already carries its own timing.
Because the source is. An APNG has no audio track, so the converter writes a video-only WebM. That turns out to be convenient on the web: browsers only autoplay video that is muted, so a silent file plays inline without a user gesture as long as you add muted, loop, autoplay, and playsinline to the <video> tag.
WebM if you control the page: it is royalty-free, its VP9 encoder tends to beat H.264 on flat animated content, and support now sits near 96% of users. MP4 if the file has to travel — messaging apps, social uploads, editors, and older Safari installs all handle H.264 in MP4 more predictably. APNG to MP4 is one click away, and serving both from a single <video> element with two <source> tags is a common belt-and-braces approach.
Usually dramatically smaller, because you are swapping lossless per-frame storage for motion-compensated video: WebM only encodes what changed between frames, which is exactly what an APNG cannot do. The savings are biggest on long loops and on animation with large static areas, and smallest on very short clips where container overhead dominates. Content with heavy per-frame noise compresses least well in both formats.
Chrome from version 25, Firefox from 28, Edge from 79, and Safari from 16 handle WebM natively — roughly 96% of global browser usage, with Safari 12.1 to 15.6 offering only partial support. That is effectively the same reach as APNG itself, so the choice between them is about transparency and file size rather than compatibility.
It is uploaded over an encrypted (TLS) connection, converted on our servers, and deleted automatically after a few hours. There is no sign-up, no watermark, and files are never shared or made public. If you later want to go the other way, WebM to GIF turns a clip back into a looping image.