Initializing... drag & drop files here
Supports: XVID
Xvid is an open-source MPEG-4 Part 2 (Advanced Simple Profile) video encoder from the DivX era — the codec behind a great many early-2000s rips and camcorder transfers. APNG is an animated still-image format that keeps full colour losslessly and degrades to a plain picture where it is not supported. Converting a short Xvid clip to APNG gives you a loop you can drop into a page, a wiki or a chat window with no player involved. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours — no sign-up, no watermark.
.xvid extension specifically; if your Xvid video is inside an ordinary .avi — which is where most Xvid content lives — use AVI to APNG instead, which is the same conversion for the more common container..apng. The animation is written with an infinite loop count and then recompressed with Zopfli before download.| Property | Result |
|---|---|
| Output | One animated .apng file |
| Loop count | Infinite |
| Frame delay | Exactly 1/N second, uniform across frames |
| Duration | Matches the source clip |
| Audio | None — APNG has no audio track, so the clip's audio is dropped |
| Per-frame quality | Lossless: whatever the Xvid stream decodes to is stored exactly |
| Measured size | A 2-second 480×270 clip at 10 FPS produced a 20-frame APNG of about 163 KB from a 57 KB source file in our own before/after check |
Anamorphic clips come out squashed. Plenty of Xvid files — especially DVD rips — store non-square pixels: 720×480 tagged for 16:9 display, for example. PNG has no concept of pixel aspect, so the frames are extracted at their storage size and the picture ends up horizontally compressed. We confirmed this on a 720×480 clip flagged 16:9: the extracted frames were 720×480, not the 854×480 the player shows. Selecting a width alone does not fix it either — the storage aspect is carried along. The fix is to enter an explicit Width × Height matching the display shape, for example 854 × 480.
Interlaced sources keep their combing. No deinterlacing is applied anywhere in this pipeline. If your Xvid came from interlaced video, the horizontal comb-tooth artifacts on moving edges are baked into every frame and will be preserved perfectly by APNG's lossless encoding. Deinterlace in a desktop editor first if the source is field-based.
| APNG | GIF | MP4 | |
|---|---|---|---|
| Colour per frame | Full colour, lossless | 256-colour palette | Full colour, lossy |
| Transparency | 8-bit alpha | 1-bit on/off | None |
| Audio | No | No | Yes |
| Size for the same 20 frames | About 163 KB in our check | About 82 KB in the same check | Far smaller again for longer footage |
| Plays as | An image, no player needed | An image, no player needed | Video, needs a player element |
| Where unsupported | Shows the still image | Effectively always supported | Universal on modern devices |
| Use it for | Short loops where colour fidelity matters | Short loops where reach matters | Anything longer than a few seconds |
For anything beyond a few seconds, keep it as video: XVID to MP4 will be a small fraction of the size for the same footage, and it keeps the audio.
The APNG stage is lossless — each decoded frame is stored exactly, with no palette reduction and no lossy re-encoding. What you cannot recover is what Xvid already discarded: it is a lossy codec, so block artifacts and smearing already present in the source are preserved faithfully rather than cleaned up. Lowering the Framerate drops whole frames, and lowering the resolution discards detail, so those are the two settings that actually cost you anything.
Because Xvid predicts each frame from its neighbours and throws away detail, while APNG stores every frame losslessly. In our before/after check a 57 KB, two-second, 480×270 clip became a roughly 163 KB APNG — nearly three times the source. Cut the resolution, cut the framerate, or shorten the clip; those are the levers, and the first two are on the page.
No. APNG is an image format with no audio track at all, so any sound in the source is discarded. If you need the audio, convert to a video container instead — XVID to MP4 keeps both streams.
Not directly — this page accepts the .xvid extension. Xvid is a codec rather than a container, and the overwhelming majority of Xvid video is stored inside AVI, so for a .avi file use AVI to APNG. It runs the same frame-extraction and assembly pipeline; only the accepted input differs.
A few seconds. Output size grows with resolution multiplied by frame count and there is no inter-frame compression to absorb it, so a 30-second clip at full resolution produces a file nobody will wait to load. If the clip is longer, either trim it first or keep it as video.
Choose APNG when the footage has gradients, skin tones or fine detail that a 256-colour palette would band, and when you want the file to degrade to a still picture rather than break. Choose GIF when the destination is an old email client or a platform that rejects APNG, and accept the palette limit — XVID to GIF does that. On the same 20 extracted frames, the GIF was roughly half the size of the APNG, which is exactly what the palette reduction buys you.
Yes. Frames are resampled at the rate you select and each frame's delay is written as an exact 1/N-second fraction, so the APNG's real-time length matches the source. This is a genuine advantage over GIF, which stores delays in whole centiseconds and so cannot express rates like 15 FPS exactly.
It displays the still image held in the file's ordinary PNG data instead of animating — never a broken-image icon. The W3C PNG Third Edition Recommendation of 24 June 2025, which brought APNG into the PNG standard as section 4.9, defines exactly that behaviour for decoders that do not handle the animation chunks.