AVIF converter
Convert AVIF images while handling AV1 compression, alpha, HDR color, browser support, metadata, and legacy fallbacks.
.avif
Format
About AVIF
AVIF stores still images in the AV1 Image File Format, using the ISO base media container family with AV1-coded image items and supporting metadata, alpha, grids, and advanced color information. It is built for modern web delivery: photos, product images, hero art, and transparent assets can often become smaller than older JPEG or PNG derivatives at comparable visual quality. That benefit comes with operational tradeoffs. Encoding can be slower, old upload forms may reject the extension, and not every image editor exposes the same controls. Our image routes convert AVIF to JPG, PNG, WebP, TIFF, PDF, ICO, BMP, GIF, and HEIC, and write AVIF from several common inputs.
AVIF supports 8, 10, and 12-bit signals, monochrome or color images, chroma subsampling, lossless and lossy modes, alpha planes, ICC and NCLX color descriptions, EXIF or XMP metadata, and in some ecosystems image sequences. Those features make it more capable than a simple web thumbnail format. They also create conversion hazards. A 10-bit HDR AVIF may look dull after a target clamps it to ordinary 8-bit SDR. A transparent AVIF converted to JPG needs a background color. A browser may decode AVIF correctly while a CMS image library, email client, or office tool still cannot.
Readers and writers include modern browsers, image CDNs, Squoosh, Sharp, ImageMagick builds with codec support, phone and camera software in some workflows, design export tools, and performance-focused web pipelines. AVIF is normally a delivery derivative, not the only master asset. Designers may keep PSD, SVG, PNG, TIFF, or original camera files, then generate AVIF plus WebP or JPG fallbacks for different clients. That source-versus-output distinction matters because repeated lossy conversion from AVIF to another lossy target can compound compression artifacts and remove metadata the original file retained during review cycles.
AVIF conversion gotchas are about compatibility and color. AVIF to JPG is safest for old systems but loses alpha, animation-like sequences, and some color depth. AVIF to PNG keeps transparency for still graphics but may produce larger files. AVIF to WebP is a practical browser fallback when a stack supports WebP but not AVIF. PNG or JPG to AVIF should start from the highest quality source, not an already compressed delivery file. Before batch conversion, test one saturated image, one transparent asset, and one photo with fine texture. Check whether metadata, orientation, and profiles survive in the system that will actually receive the output.
Common AVIF problems
A CMS rejects AVIF even though browsers display it.
Use /convert/avif-to-webp for a modern fallback or /convert/avif-to-jpg for the broadest still-image compatibility.
Transparency is required for an icon or product cutout.
Use /convert/avif-to-png instead of JPG, then verify alpha edges against light and dark backgrounds.
An HDR-looking AVIF becomes flat after export.
Use /convert/avif-to-png for review and compare color on the target display before approving an SDR derivative.
A web pipeline needs smaller files from source images.
Use /convert/jpg-to-avif or /convert/png-to-avif from the clean source, not from a recompressed thumbnail.
A client needs a document-style proof of an AVIF image.
Use /convert/avif-to-pdf, then confirm page size and image scaling before sending the proof.