Choose AVIF according to the destination and device
This workspace converts JPG, PNG or WebP to AVIF and can convert a supported AVIF to JPG, PNG or WebP. AVIF encoding can require more processing time than simpler formats. The verified profile is static SDR imagery, limited to four million pixels. Animation, unverified HDR and high-bit-depth input should not be treated as ordinary supported pictures. Pick the output according to the receiving website, editor or device.
When a form does not accept AVIF, select a format it permits. When preparing a website image, compare AVIF and WebP using actual size and visible detail rather than relying on a format label. Processing remains local; a slower device may benefit from a smaller source or WebP. Open the exported file in the intended destination, because a successful browser conversion does not establish universal compatibility.
Worked example
A 160 by 100 PNG contains 16,000 pixels and fits the stated AVIF limit. With AVIF selected and dimensions unchanged, the requested output is 160 by 100. Converting an AVIF for a JPG-only form is a different use of the same workspace: select JPG and confirm its background. Neither example promises a particular file-size saving.
Local processing and limits
One supported static image is processed at a time. The general input limit is 10 MiB and twelve million pixels; AVIF processing is limited to four million pixels. Unsupported animation, image sequences, HDR and unverified container features are refused. Large images need more memory even when their compressed file is small. A failed operation does not switch to a server-upload fallback.
The browser downloads its own application and codec resources from the same host. Your selected image, result, filename and metadata are not sent to an upload service. Images are not written to localStorage, IndexedDB or a service-worker recovery cache. Reloading the page leaves the image workspace empty. Downloaded files remain under your control; inspect them before sharing.