In your browser — no upload, no signup. Alpha transparency preserved. First encode: ~1 s.
or drop the image here
Converting…
RoundCut converts PNG to AVIF entirely in your browser using @jsquash/avif, a WASM port of libavif. The file is never uploaded. AVIF is lossy at our q85 setting — visually near-lossless for photos and typically 30 to 50 percent smaller than the same image as WebP. PNG transparency survives intact: the alpha channel is preserved.
Drop a PNG file on the upload area (or click to pick one). The conversion starts the moment the file lands — no Convert button to chase. The first encode in a session pays a one-time cost: about 1 second to fetch and warm up the AVIF encoder (a 2.5 MB WASM module). After that, encodes are fast — roughly 40 ms for small images, 250 ms for a 1 MP photo, and around 2.8 s for a 4K shot. When the AVIF is ready, the Download button saves it to your device.
Yes. Unlike PNG to JPG, where transparency is destroyed and replaced with white, AVIF natively supports an alpha channel. Every transparent pixel in your PNG stays transparent in the AVIF output. Logos, icons, sticker cut-outs, UI assets — anything that depends on a transparent background — survives the conversion intact, with no flattening, no halo, no manual masking. This is the structural advantage of AVIF over JPG and the main reason to convert PNG to AVIF rather than PNG to JPG.
AVIF wins on size: at comparable visual quality it's roughly 20 to 30 percent smaller than WebP, and 30 to 50 percent smaller than PNG for photographs. WebP wins on compatibility — near-universal support, including older Safari. AVIF reaches 94.3 percent of global browsers (Chrome 85+, Firefox 93+, Safari 16.4+, Edge 121+) and is the right choice when bandwidth matters and your audience is on modern browsers. Best practice in 2026: ship AVIF first with a WebP fallback via the picture element, and keep PNG for the source of truth.
AVIF is lossy — claiming otherwise would be a lie. At our q85 setting, photos measure roughly 42.6 dB PSNR, which is visually indistinguishable from the source for natural images. Graphics with sharp text or fine line art may show subtle artifacts at any setting; for those, keep the PNG. There is no quality slider — every conversion uses the same q85 setting. Encoding speed is honest: the WASM module loads once per session (~1 s cold start), then warm encodes are fast on Chromium and WebKit. Firefox is about 4 times slower for AVIF — Chrome will be faster for large images.
The conversion runs entirely in your browser via the @jsquash/avif WASM module. Nothing is uploaded, nothing is logged, nothing is queued on a server. Open DevTools, switch to the Network tab, and convert: zero outbound image requests will appear. There is no account, no funnel, no server fallback — the same client-side code path runs on every browser. Most online AVIF converters upload your PNG to their servers and delete it later; this one never receives it in the first place.
AVIF reaches roughly 94.3 percent of global browsers as of 2026: Chrome 85 and later, Firefox 93 and later, Safari 16.4 and later (iOS 16 and later), and Edge 121 and later. Internet Explorer, Opera Mini, and iOS 15 or below do not support AVIF. If your audience includes those, ship AVIF first with a WebP fallback via the picture element, so unsupported browsers receive WebP instead.
Yes. AVIF natively supports an alpha channel, and our @jsquash/avif encoder preserves it. Every transparent pixel in your source PNG stays transparent in the AVIF output — no flattening, no white background, no halo. This is the structural advantage over JPG, which has no alpha and must replace transparency with a solid color.
AVIF is roughly 20 to 30 percent smaller than WebP at comparable visual quality and supports a wider color gamut and higher bit depth. WebP has wider browser support — near-universal, including older Safari. AVIF reaches about 94.3 percent of global browsers in 2026. For modern audiences and bandwidth-sensitive pages, AVIF wins; for maximum compatibility, WebP wins. The 2026 best practice is AVIF first with a WebP fallback.
The AVIF encoder is a 2.5 MB WASM module that loads once per session — about 1 second on the first encode. After that, warm encodes are fast: roughly 40 ms for small images, 250 ms for 1 MP, and around 2.8 s for a 4K photograph. Large images (above 8 MP) on mobile can take 10 to 30 seconds. Firefox is about 4 times slower than Chrome for AVIF — if you are on Firefox with a large image, switching to Chrome will be noticeably faster.
Your file never leaves your browser. The conversion runs entirely on your device using the @jsquash/avif WASM encoder — no upload, no server, no telemetry on file contents. You can verify it: open DevTools, switch to the Network tab, then convert. Zero outbound image requests will appear during the conversion.
Yes — AVIF is a lossy format, unlike PNG which is lossless. At our q85 setting, photographs measure around 42.6 dB PSNR, which is visually near-lossless to the naked eye for natural images. Graphics with sharp text, fine line art, or hard color transitions may show subtle artifacts at any AVIF setting. If you need lossless output, keep the PNG — converting is a downgrade for those cases.