PicBrewery image optimizer and converter
  1. Home
  2. Convert
  3. JPG to AVIF

Convert JPG to AVIF — Free Online, No Upload

Drop a JPG into PicBrewery and get an AVIF version generated right in your browser — no upload, no watermark. Expect 40–60% smaller files than the source JPG at matching quality, courtesy of the AV1 codec that powers AVIF.

For a wider comparison of AVIF against JPEG, PNG and WebP see the formats comparison table.

How to convert JPG to AVIF

  1. Open PicBrewery.
  2. Drag a JPG file onto the upload area (up to 20 files per batch, 20 MB each).
  3. Wait for AVIF encoding to finish. JPEG, PNG and WebP fill in first; AVIF is last because AV1 is more CPU-intensive — expect 1–3 seconds per megapixel on a modern laptop.
  4. Click the download icon on the AVIF cell. For batches, Download all as ZIP packages only the smallest format per source into one archive.

Why convert JPG to AVIF?

AVIF is a still-image profile of the AV1 video codec, released in 2019 by the Alliance for Open Media. It is currently the strongest mainstream still-image codec: for real-world photographs AVIF is typically 40–60% smaller than MozJPEG at matching perceived quality. The savings come from better block-level prediction, larger transforms and a more flexible entropy coder than JPEG's 30-year-old DCT design. AVIF also adds alpha, HDR, wide-gamut color and 10/12-bit depth — none of which JPEG supports.

The one catch is encode time. JPEG encodes in milliseconds; AVIF needs one to a few seconds per megapixel. For bulk image processing this is fine — the user's device does the work, once, and the resulting file is smaller forever. PicBrewery encodes in Web Workers in parallel with JPEG, PNG and WebP so you can download the faster formats while AVIF is still computing.

Expected file-size savings

Camera photos re-encoded from JPG quality 85 to AVIF quality 55 run 40–60% smaller with no visible loss. High-frequency subjects (foliage, hair, fabric) hit the top of that range; sparse, low-detail subjects (sky gradients, studio backdrops) hit the bottom because JPEG already compresses them well. Screenshot-like JPGs with sharp text often benefit the least from AVIF — lossless WebP or PNG tends to win on such inputs, and PicBrewery shows those alternatives in the same row.

Browser support for AVIF

AVIF is supported by Chrome 85+ (2020), Firefox 93+ (2021), Edge 121+, and Safari 16+ (2022 — macOS Ventura, iOS 16). For older browsers use a <picture> element with AVIF on top and JPG as the fallback — every browser picks the best source it can decode and nobody sees a broken image. The full per-version matrix is on /formats/#avif.

Frequently asked questions

How much smaller is AVIF than JPG?

Typical photographs re-encoded from a quality-85 JPG to a quality-55 AVIF come out 40–60% smaller at visually matched quality. Gains shrink on low-detail graphics (sky gradients, studio backdrops) where JPEG already compresses well, and grow on high-frequency textures (foliage, fabric, skin) where AV1's transforms and intra prediction pull ahead.

Does Safari support AVIF?

Yes, since Safari 16 (macOS Ventura and iOS 16, released in September 2022). Chrome has supported AVIF since version 85 (2020), Firefox since 93 (2021) and Edge since 121. For older browsers, serve AVIF inside a <picture> element with a JPG fallback so everything degrades cleanly.

Why is AVIF encoding so slow?

AVIF is a still-image profile of the AV1 video codec. AV1 achieves best-in-class compression by trying many block sizes, prediction modes and transforms — which is CPU-intensive. PicBrewery uses the aom/libavif encoder compiled to WebAssembly and runs it on a worker pool, but a single megapixel can still take 1–3 seconds depending on your CPU. Smaller files are the payoff.

Is re-encoding JPG to AVIF lossless?

No. Lossy AVIF is a lossy codec, and the JPG is itself already lossy, so pixels shift slightly twice. In practice the second pass is below visible threshold as long as AVIF quality is 50 or higher (PicBrewery defaults to 55). Lossless AVIF exists but is not a good match for JPG input — the file gets bigger, not smaller.

Can I serve AVIF to everyone, or do I need a fallback?

For cutting-edge browsers alone — sure, serve AVIF directly. For universal delivery use a <picture> element with AVIF on top, WebP as the middle tier, and JPG as the final fallback. PicBrewery produces all three from one source image, so building that picture markup is just copy and paste.

Convert JPG to AVIF now

Drop your JPGs into PicBrewery and let it do the heavy lifting. 100% client-side — nothing leaves your device.

Open PicBrewery