Initializing... drag & drop files here
Supports: 3G2, 3GP, 3GPP, ASF, AV1, AVCHD +31 more
2.100 = 2.1 seconds) to capture one frame, or use Multiple Frames to grab a sequence.AVIF (AV1 Image File Format) was published in February 2019 by the Alliance for Open Media and uses the same AV1 codec that powers modern video streaming, wrapped in an HEIF/ISOBMFF container. Per MDN, lossy AVIF files are roughly 50% smaller than equivalent JPEG and modestly smaller than WebP at matched perceptual quality, while adding 10- and 12-bit color, HDR (BT.2100 / PQ / HLG), transparency, and image sequences. Pulling a frame (or a short sequence) out of a video into AVIF is the most efficient way to publish that still on the modern web.
.mov screencast at 4K and saving as AVIF produces a much smaller file than PNG while retaining clean text edges at high quality presets.<picture>, so shipping AVIF originals is safe.| Property | AVIF | WebP | JPEG | PNG |
|---|---|---|---|---|
| Typical size at matched quality | Baseline (smallest) | ~20-30% larger | ~50-100% larger | Much larger (lossless) |
| Max color depth | 8 / 10 / 12-bit | 8-bit | 8-bit | 8 / 16-bit |
| HDR (BT.2100 / PQ / HLG) | Yes | No | No | No |
| Transparency (alpha) | Yes | Yes | No | Yes |
| Animation / image sequences | Yes | Yes | No | No (APNG separate) |
| Underlying codec | AV1 (AOMedia) | VP8 / VP8L | DCT (1992) | DEFLATE |
| Browser support (May 2026) | Chrome 85+, Firefox 93+, Safari 16.4+, Edge 121+ (~94% global, caniuse) | Universal | Universal | Universal |
| Progressive rendering | No | No | Yes | Yes (interlaced) |
| Preset | Typical use | Notes |
|---|---|---|
| Highest | Print, retouching masters, archival | Near-lossless; files ~3-5× larger than Very High |
| Very High | Hero images, marketing stills | Default; visually indistinguishable from source for most content |
| High | Standard web images, blog thumbnails | Best size/quality balance for most pages |
| Medium | List thumbnails, low-priority images | ~50-60% of High's size; minor texture loss |
| Low / Lowest | Placeholders, previews, LQIP | Visible artifacts; use only when size dominates |
For converting an existing animated GIF instead of a video, see convert-gif-to-avif. For the file-by-file inputs, the format-specific routes are convert-mp4-to-avif, convert-mov-to-avif, and convert-webm-to-avif. To re-compress an AVIF that's already on disk, use compress-avif.
Per MDN, lossy AVIF is roughly 50% smaller than JPEG at matched perceptual quality, and somewhat smaller than WebP. Exact ratio depends on content — flat illustrations and screencaps compress hardest, while heavy film grain or noise narrows the gap. The Very High preset is a good starting point for visual parity with high-quality JPEG.
Yes. Use the Frame Selection > Multiple Frames option to grab a sequence; the output is a single AVIF file containing the frames. Image sequences are part of the AVIF specification. Decoder support has matured but is not yet universal — Chrome and Firefox decode animated AVIF reliably, and Safari 16.4+ supports image sequences, though playback behavior in some browsers still trails animated WebP. For broadest compatibility, animated WebP or a short MP4/WebM remains safer; AVIF wins on size.
As of May 2026, AVIF stills decode in Chrome 85+ (Aug 2020), Firefox 93+ (Oct 2021), Safari 16.4+ (March 2023), and Edge 121+. Global support is about 94% per caniuse. For the small residual audience, serve AVIF first via <picture> with a WebP and JPEG fallback — that pattern is what Cloudflare, Shopify, and Next.js' Image component use.
Seconds with optional milliseconds, e.g. 0 for the first frame, 12 for the 12-second mark, or 2.100 for 2 seconds and 100 milliseconds. The frame at (or nearest to) that decode timestamp is extracted. If your source is variable-frame-rate (typical for screen recordings), the picked frame is the closest keyframe-snapped sample.
Video frames are usually stored in 4:2:0 YUV with the camera/encoder's color matrix (BT.709 for HD, BT.2020 for HDR). The converter decodes that and re-encodes to AVIF, which can also store 4:2:0 in the same color space at higher bit depth. At Very High or above the difference is imperceptible; at Medium or below you may see softening of fine textures or banding in smooth gradients — typical lossy compression behavior, not a bug.
AVIF supports 10-bit and 12-bit color and the BT.2100 / PQ / HLG transfer functions used by HDR10 and HLG broadcast. Dolby Vision dynamic metadata itself is proprietary and is not carried into AVIF, but the underlying HDR10 base layer (PQ + BT.2020 + 10-bit) is preserved. Pick the Highest or Very High preset to keep grading headroom.
The browser uploads in-session, so the practical ceiling is upload size and connection speed and network rather than a fixed cap. For multi-gigabyte source files, trim the clip first (see video-trimmer) and convert the relevant segment — AVIF extraction only needs the frames you actually want.
AVIF compresses better and supports HDR + 10/12-bit color; WebP has slightly broader historical support and simpler encoder tooling. With ~94% global AVIF support in 2026, the standard recommendation (per MDN) is to serve AVIF first and fall back to WebP, then JPEG, via <picture>. If you only have time to ship one format, AVIF is the better technical choice; if you need a single drop-in <img> replacement for the widest audience, WebP is still slightly safer.
AVIF supports an alpha channel, so transparency is preserved during the convert step when the source container carries it. Most consumer footage (H.264 MP4 from phones, screen recordings) has no alpha and will produce an opaque AVIF. ProRes 4444, HEVC-with-alpha, and certain WebM/VP9 streams do carry alpha and will round-trip into AVIF cleanly.
Safari added AVIF still support in 16.1 (partial) and 16.4 (March 2023, full per caniuse) including image sequences. In practice, animated AVIF playback behavior across browsers is less mature than animated WebP, so for short looping content where Safari < 17 is a concern, animated WebP or a muted autoplay <video> is the safer fallback.