Initializing... drag & drop files here
Supports: AVIF
This tool decodes a modern AVIF image into a PPM — the Portable Pixmap from the Netpbm family, which stores raw, uncompressed RGB pixels with no codec in the way. It exists for image-processing and computer-vision pipelines that read Netpbm natively: OpenCV, Pillow, ImageMagick, FFmpeg, and the Netpbm command-line utilities all consume PPM directly. Expect the output to be much larger than the AVIF it came from — that is the point. AVIF is a compressed delivery format; PPM is the decompressed pixels a program wants to work on. If you instead want an image you can open and share, AVIF to PNG keeps full quality with transparency in a far smaller file, and AVIF to JPG is better for posting or emailing.
| Property | AVIF | PPM |
|---|---|---|
| Full name | AV1 Image File Format | Portable Pixmap (Netpbm family) |
| Origin | AOMedia, 2019 | Jef Poskanzer, late 1980s |
| Compression | Lossy or lossless (AV1 intra-frame) | None — every pixel stored verbatim |
| Typical file size | Very small | Large (raw pixels) |
| Alpha / transparency | Yes | No — RGB only |
| Metadata | EXIF, ICC color profiles, HDR | None — header is width, height, maxval |
| Bit depth | Up to 12-bit, HDR | 8-bit or 16-bit per channel here |
| Native browser support | ~93% of browsers (Chrome 85+, Firefox 93+, Safari 16.4+, Edge 121+) | None |
| Best for | Web delivery, storage, sharing | An exact-pixel intermediate for image tools |
A PPM holds raw pixel data, so a single 1920 × 1080 image in 8-bit RGB is about 1920 × 1080 × 3 ≈ 6.2 MB no matter how the source looked — even though the AVIF it came from might be only a few hundred kilobytes. Choosing 16-bit roughly doubles that, since each sample becomes two bytes.
Because the use case is feeding raw pixels into a program, not saving space. AVIF is a compressed delivery format; many image-processing, computer-vision, and research toolchains — OpenCV, Pillow, the Netpbm utilities, ImageMagick — would rather read a simple PPM than decode AVIF themselves. The conversion decompresses the image into a header plus a flat array of RGB bytes, which is trivial for code to parse. The file gets bigger on purpose; that is the format's whole reason for existing.
Decoding to PPM adds no new loss — the pixels written are exactly the decoder's output, bit for bit, with no second round of compression. There is one caveat: if the source AVIF was saved with lossy compression, that loss is already baked into the pixels and cannot be recovered. A losslessly encoded AVIF decodes to PPM with no degradation at all. Either way, the PPM is a faithful copy of whatever the AVIF currently contains.
It is flattened. AVIF supports an alpha channel, but the PPM specification has no alpha — it stores only red, green, and blue. Transparent or semi-transparent regions are composited against a background during conversion rather than carried through. If preserving transparency matters, convert to AVIF to PNG instead, which keeps the alpha channel and is lossless and compressed. The Netpbm family's PAM format can hold alpha, but standard PPM cannot.
Not browsers, and not most consumer photo viewers. PPM is meant for image tooling: ImageMagick, GIMP, Photoshop, FFmpeg, and the Netpbm utilities read it directly, and it is a common input for OpenCV and Pillow. In our testing, an 8-bit P6 export of a 1080p image opened straight away in ImageMagick and GIMP at roughly 6.2 MB, while Windows Photos and Chrome would not preview it. If you need an image that opens anywhere, convert to AVIF to PNG instead.
Your AVIF is uploaded over an encrypted connection and processed entirely on our servers — not in your browser. Files are deleted automatically a few hours after conversion, with no sign-up and no watermark, and they are never shared or made public.