Initializing... drag & drop files here
Supports: AV1, MP4, MKV, WEBM
A .av1 file is a raw AV1 elementary stream — AOMedia's royalty-free video bitstream (Open Bitstream Units, sometimes with a minimal IVF header) with no container, no seek index, and no audio track. APNG is the opposite kind of file: a still-image format extended with animation chunks, so it plays inline in a browser tab, a README, or a chat window with no video player and no autoplay policy to fight. This converter decodes the AV1 frames on our servers and re-renders them as an animated PNG at the framerate and size you choose.
| Property | Value |
|---|---|
| What it is | PNG plus three animation chunks: acTL (animation control), fcTL (frame control), fdAT (frame data) |
| Standard | PNG Specification (Third Edition), section 11.3.6 |
| Status | W3C Recommendation, published 24 June 2025 |
| Compression | DEFLATE — a lossless algorithm, applied per frame |
| Colour depth | Up to 24-bit truecolour, plus an 8-bit alpha channel |
| Transparency | Full 8-bit alpha (soft, anti-aliased edges) |
| Frame coding | Frames may be sub-rectangles composited with dispose/blend rules — but there is no motion compensation |
| Audio | Not supported; APNG is image-only |
| Behaviour in old decoders | The APNG chunks are ancillary, so a non-animating decoder ignores them and shows the static default image |
| Native browser support | 95.94% of tracked global traffic (caniuse): Chrome 59+, Firefox 3+, Safari 8+, Edge 79+, Opera 9.5+ |
| Best for | Short loops that need clean alpha and exact colour — logos, UI motion, stickers, docs |
.av1 file onto the page, or click "+ Add Files" to browse for it. Several clips can be queued and converted with the same settings in one pass.| Property | APNG | GIF | Animated WebP |
|---|---|---|---|
| Colour depth | 24-bit truecolour | 8-bit palette (256 colours per frame) | 24-bit truecolour |
| Transparency | 8-bit alpha, soft edges | 1-bit on/off, hard edges | 8-bit alpha |
| Frame compression | Lossless (DEFLATE) | Lossless LZW over an indexed palette | Lossy or lossless |
| Typical size for the same loop | Large | Large, and worse on photographic content | Smallest of the three |
| Browser support | 95.94% (Chrome 59+, Firefox 3+, Safari 8+, Edge 79+) | Effectively universal | Chrome, Edge, Firefox, Safari 14.1+ |
| Behaviour where unsupported | Static first frame | n/a | Broken image |
| Best for | Clean alpha, gradients, exact colour | Maximum compatibility, simple loops | Smallest web-delivery animation |
APNG size is driven by one number: total frames, which is framerate multiplied by clip length. At the default 10 FPS a 6-second clip becomes 60 frames; at 30 FPS it becomes 180. Each of those frames is a PNG image compressed on its own, so unlike AV1 there is no motion prediction spreading one background across a hundred frames — a static scene helps only as much as DEFLATE can exploit it inside each frame.
That gives you three practical levers, in order of impact:
.av1, then convert the trimmed segment.If the result is still too heavy and you can live with a 256-colour palette, AV1 to GIF is the smaller, more universally supported option. If you only need one still image rather than motion, AV1 to PNG extracts a single frame instead.
APNG's DEFLATE compression is lossless, so it is not the format throwing detail away. The real limits are upstream and in your settings: AV1 is a lossy video codec, so every frame already carries the artifacts the encoder baked in, and the framerate you choose decides which frames survive at all. Keeping Image resolution on Keep original and the framerate at 10 FPS or higher preserves the most of what the source actually contains.
Because the two formats compress along different axes. AV1 uses motion compensation and temporal prediction — a frame mostly stores what changed since the last one — plus modern entropy coding. APNG stores each frame as a PNG image; it can composite a smaller sub-rectangle over the previous frame, but it has no motion vectors and no inter-frame transform. Multi-fold growth from an AV1 source is normal, not a fault in the conversion.
APNG carries a full 8-bit alpha channel, and that alpha is preserved rather than flattened. But a video source rarely has any transparency to preserve: AV1 video frames arrive as opaque YUV pictures, so the APNG will normally be fully opaque. APNG's alpha matters when the artwork itself has transparent regions — for a video frame grab, the benefit you actually get from APNG is 24-bit colour instead of GIF's 256-colour palette.
APNG animates in Chrome 59+, Firefox 3+, Safari 8+, Edge 79+, and Opera 9.5+, which caniuse puts at 95.94% of tracked global traffic. Where it is not supported, nothing breaks: the animation chunks are ancillary, so the decoder ignores them and renders the static default image — your first frame — as an ordinary PNG. That graceful fallback is written into the PNG Third Edition specification.
No — the AV1-to-APNG page exposes Framerate and Image resolution only; there is no trim or start-time control here, so the whole stream is rendered. Cut the segment you want first with the video cutter (it accepts .av1), then bring the trimmed clip back here. That order also keeps the conversion fast, since there are fewer frames to encode.
Not from this page. APNG stores a loop count in its acTL chunk, but the converter does not expose a loop-count control, so treat the output as a continuously looping animation. If a specific play-once behaviour matters more than the animation itself, an HTML <video> element with an MP4 source gives you real playback control and a far smaller file.
.av1 file, and will the APNG have sound?A bare .av1 is a raw AV1 video bitstream — video only, with no audio track and no container around it. The APNG question is moot either way: the PNG format has no audio channel at all, so no animated PNG anywhere carries sound. If you need the motion and the soundtrack together, convert to MP4 instead of an image format.
Your .av1 is uploaded over an encrypted connection, decoded and re-rendered on our servers, and deleted automatically a few hours later — never shared, never made public, with no sign-up and no watermark. The practical limit on a long clip is upload size and time rather than anything on your end, which is one more reason to trim before converting rather than after.