JPG to AVIF Converter

The quality numbers are not comparable to JPG's, and this is the single most useful thing to know here. AVIF at 65 looks roughly like JPG at 85. Using your usual JPG number produces a much larger file than you need and throws away most of the benefit.

• 80–95 — Near-transparent quality. Files are still smaller than the JPG, but you are leaving most of the saving unclaimed. Use before further editing.
• 55–79 — The useful band for web photographs. 65 is the default and is where AVIF's advantage is largest.
• 40–54 — Clearly smaller again, and AVIF degrades more gracefully than JPEG does — it softens rather than blocking.
• Below 40 — Visible smoothing and loss of texture.

Because this is a lossy-to-lossy conversion, the usual caution applies: convert once, from the best original you have. Your JPG has already had detail removed, and AVIF will remove more. Converting a heavily compressed JPG gives a small AVIF that still carries every JPEG artefact from the original.

If a file comes out larger, the JPG was already compressed very hard. Lower the quality, or accept that the original is already efficient.

One pleasant surprise: AVIF handles flat colour and hard edges better than JPEG, so screenshots and graphics that JPEG smears often convert well.

When AVIF is the right choice

• Photographs on a website you control. The clearest case: dramatic size reduction, and every current browser displays it.
• Image-heavy pages — galleries, portfolios, product listings — where the saving multiplies across every image on the page.
• Mobile-heavy traffic, where bandwidth costs your visitors money.
• Anywhere page speed matters, which affects both ranking and how many visitors stay.

When to stay with JPG or use WebP

Keep JPG for anything you hand to someone else: email, upload forms, print services, or a file whose destination you cannot predict.

Consider WebP when you want most of the benefit with fewer trade-offs — it is not quite as small, but it encodes far faster and has broader support outside the browser. For a large batch, WebP is often the more practical choice.

Serving AVIF with a fallback

The standard approach lets each browser take the best format it understands:

<picture>
  <source srcset="photo.avif" type="image/avif">
  <source srcset="photo.webp" type="image/webp">
  <img src="photo.jpg" alt="…">
</picture>

Browsers pick the first type they support, so modern ones get the smallest file and everything else falls back cleanly.

Camera metadata

EXIF data, including GPS coordinates recording where a photo was taken, is not carried into the AVIF. That is generally what you want for images about to be published. The orientation flag is applied to the pixels first, so photos stay the right way up.