Skip to content
Zumkor
← Back to blog 10 min read

How to convert AVIF to JPG on Mac (batch, offline, 2026)

Got an .avif file that won't open or upload? Convert AVIF to JPG on your Mac with Preview, Quick Actions, sips, or Zumkor — single files or folders, fully offline.

Convert your photos with Zumkor on your Mac — free for 7 days, then 5 files a day free or $19.99 once. Needs macOS 14.0 or later on an Apple silicon Mac (Apple M1 or later).

Get Zumkor on the Mac App Store

You saved an image from a website and got a file ending in .avif. Double-clicking it works — your Mac shows the picture just fine — but the thing you saved it for doesn’t: the upload form says “unsupported file type,” the print service refuses it, Word or an older Photoshop won’t place it, the listing platform wants JPG or PNG only. The file opens; it just doesn’t travel.

If that story sounds familiar, it’s because it already happened once. WebP pulled exactly this trick a few years ago, and AVIF is the sequel: an even more aggressive web-native format that big sites and CDNs now serve by default, which means “Save Image” increasingly hands you an .avif whether you asked for one or not.

This guide covers how to convert AVIF to JPG on a Mac — the built-in free routes, the command line, and the one-drag batch route — entirely on-device, plus the three format gotchas (transparency, HDR, animation) that produce surprising results if you don’t see them coming.

In this guide12 sections

What AVIF is, and why your workflow rejects it

AVIF is the AV1 Image File Format — a still image compressed with the AV1 video codec’s intra-frame tools and wrapped in the same container family as HEIC. It exists for one reason: size. An AVIF is typically around half the size of an equivalent JPG and meaningfully smaller than the same image as WebP, at the same visual quality. It also supports transparency, animation, and HDR with wide color — none of which JPG can hold.

For a website serving millions of images, halving image bandwidth is real money, so the big CDNs (Cloudflare, Fastly, Akamai, the image-optimization layers under Shopify and WordPress) started converting catalogs and serving AVIF to any browser that advertises support. Every mainstream browser now does. That’s why the files are suddenly in your Downloads folder.

The catch, as always, is the receiving end. Browsers read AVIF; a long tail of everything else still doesn’t: corporate upload portals, government form uploads, print kiosks and photo-book services, embroidery and laser-cutter software, Microsoft Office on plenty of Windows machines, older Adobe versions, and any in-house tool written before 2023. When one of those is the destination, the fix is the same as it was for WebP: hand it a plain JPG, the one image format that opens literally everywhere.

The good news: macOS reads AVIF natively — it has since Ventura (macOS 13), so any Mac recent enough to matter previews and opens .avif without installing anything. Your machine can already do this conversion. You just need to know where the converters live.

Can you avoid saving AVIF in the first place?

Sometimes. Many sites don’t store AVIF at all — they keep a JPG or PNG original and let a CDN convert on the fly, serving AVIF only to browsers that accept it. Two tricks exploit that. If the image URL carries a query string like ?format=avif or &fm=avif, editing it in the address bar and reloading sometimes fetches the original directly. And for a quick one-off, right-click the image and choose Copy Image (not Copy Image Address), then paste straight into the destination — Pages, Keynote, a mail message — since the clipboard carries decoded bitmap data, and the AVIF wrapper never touches the receiving app.

Both tricks are hit-or-miss, which is why they’re a sidebar. When they fail, or when you already have a folder of .avif files, you convert. Here’s how, from lightest to heaviest duty.

First: skip the web converters

Searching “avif to jpg” surfaces a wall of upload-a-file converter sites. They’re the one bad option on this list, for the same two reasons as always: you’re uploading files to a stranger’s server to perform an operation your Mac completes locally in a fraction of a second, and free converter sites are ad-funded precisely because your files and attention are the product. For a meme, fine; for product photos, client work, or anything private, no.

Everything below runs entirely on your Mac, offline. Nothing leaves the machine.

Method 1: Preview (best for one or two images)

Preview opens .avif like any other image, and exporting is one dialog:

  1. Double-click the .avif file — it opens in Preview.
  2. Choose File → Export.
  3. Set Format to JPEG.
  4. Set the Quality slider — 80–90% is visually identical to the source and much smaller than 100%.
  5. Click Save.

Done for a single file. Preview also handles a small batch: open several AVIF files at once, press ⌘A in the thumbnail sidebar, then File → Export Selected Images and pick JPEG in the options. Workable up to a couple dozen files; past that, the sidebar dance gets old.

Method 2: Finder’s Quick Action (fastest free batch)

The converter hiding in the right-click menu handles AVIF too:

  1. In Finder, select the .avif files — ⌘-click a handful, or ⌘A for a folder’s worth.
  2. Right-click the selection.
  3. Choose Quick Actions → Convert Image.
  4. Set Format to JPEG, pick an image size (Actual Size keeps original resolution), and untick “Preserve Metadata” if you don’t want it carried over.
  5. Click Convert to JPEG.

Fresh .jpg copies appear next to the originals, originals untouched. For a one-off batch of saved web images, this is the best free answer on the platform. Its limits are unchanged: output only as JPEG, PNG, or HEIF; no precise quality control; no renaming, so you keep whatever chaotic filenames the CDN generated.

Method 3: sips in Terminal (scripted batches)

Because AVIF decoding lives in the system’s ImageIO layer, the built-in sips command reads it on any modern Mac.

One file:

sips -s format jpeg image.avif --out image.jpg

A whole folder:

cd ~/Downloads/avif-images
for f in *.avif; do
  [ -e "$f" ] || continue
  sips -s format jpeg "$f" --out "${f%.*}.jpg"
done

With an explicit quality level (0–100):

sips -s format jpeg -s formatOptions 85 image.avif --out image.jpg

Fast, free, scriptable — ideal when AVIF conversion is one step in an automated pipeline. Also unforgiving: no preview, no undo, and a mistyped --out can clobber a file. Reach for it when you’d be writing a script anyway.

Method 4: Zumkor (drag the folder, done)

If stray AVIF files are becoming a recurring irritation rather than a one-time surprise — you collect reference images, save product shots for listings, or prepare assets for clients — this is the chore Zumkor exists to delete (it needs macOS 14 or later on an Apple silicon Mac — any M-series machine):

  1. Open Zumkor and drag in the AVIF files, or the whole folder they’re sitting in — subfolders included.
  2. Pick JPG as the output format.
  3. (Optional) Pick a resize preset — “Email-friendly” (1600 px) or “Web small” (1280 px) if the images are headed for email or a document — and flip on the metadata strip if they shouldn’t carry EXIF or location data.
  4. Click Convert and choose the output folder.

Every file converts in one pass, on your Mac, with nothing uploaded — it works with Wi-Fi off. Originals stay put. And because Zumkor is free for 7 days and then a one-time $19.99 purchase, not a subscription, the math stays simple: buy once, keep it forever.

The honest trade-off, same as ever: for one image, once, Preview is free and already open. Zumkor earns its slot when the folder has forty files in it, when the same download session also produced WebP strays and HEIC photos that all need to become JPG in the same pass, or when you want the resize and metadata strip folded into the conversion instead of done as separate steps.

The three AVIF gotchas

AVIF is a richer format than JPG, and three of its features don’t survive the trip. None of these is a tool failure — they’re format physics — but each can bite silently.

Transparency. AVIF supports transparent backgrounds; JPG does not. Convert a logo or product cut-out to JPG and the transparency gets flattened, typically to white. If white is fine (for product shots it usually is), proceed. If the transparency needs to survive, convert to PNG instead — every method above offers PNG in the same menu, and Zumkor writes PNG (plus HEIC, TIFF, WebP, and AVIF itself) alongside JPG.

HDR and wide color. AVIF can carry HDR imagery with more brightness range than JPG can represent. Convert an HDR AVIF to JPG and the image gets tone-mapped down to standard range — usually looking slightly flatter and dimmer than it did in the browser. There’s no fix inside JPG; it’s an SDR format. If the image looks washed out after conversion, this is why, not a bad encoder.

Animation. Like WebP and GIF, AVIF can be animated. JPG is a still format, so converting an animated AVIF yields a single frame — usually the first — and the motion is gone. If a file seems to have “lost” its animation, it was never going to keep it in a JPG.

Getting the output right

  • Quality. JPG is lossy, and web-served AVIF is almost always lossy already. Exporting at 100% inflates the file for nothing; 80–90% is the sweet spot. Below ~60%, gradients and flat-color areas start showing blocky artifacts.
  • Don’t round-trip repeatedly. AVIF→JPG→edit→JPG stacks lossy compression on lossy compression, and AVIF’s aggressive compression means the source has less headroom than a camera JPG would. Convert once, keep the output, and return to the original AVIF for fresh copies.
  • Resolution. CDN-served images can be enormous. If the JPG is bound for email or a document, downsizing the long edge cuts the file dramatically with no visible difference on screen — Preview’s export can’t resize in the same step; the Quick Action has coarse presets; Zumkor’s “Email-friendly” (1600 px) and “Web small” (1280 px) presets resize inside the conversion pass.
  • JPG vs. PNG. Photos and anything photographic → JPG. Screenshots, diagrams, logos, anything with transparency → PNG, same reasoning as the PNG-vs-JPG trade-off generally.

The reverse direction is worth knowing too

If you build for the web rather than just save from it, AVIF stops being the problem and becomes the tool: converting your JPG and PNG assets to AVIF is how you make your own pages faster instead of merely coping with everyone else’s. Zumkor writes AVIF as well as reading it — the “AVIF web” preset converts a folder of source images into web-ready AVIF in one drag, the same operation this guide describes run in the other direction. Few Mac apps handle both directions of this format; it’s the same one-time purchase either way.

Bottom line

  • One or two images: Preview → File → Export → JPEG. Ten seconds, free.
  • A folder, occasionally: select all in Finder → right-click → Quick Actions → Convert Image. The best free batch option.
  • Part of a script: a sips loop.
  • A recurring chore, or mixed AVIF/WebP/HEIC cleanup: Zumkor — drag the folder, pick JPG, everything converts offline in one pass, with resize and metadata stripping in the same step. Free for 7 days, then one-time $19.99.
  • Transparency to keep? Convert to PNG instead. HDR source? Expect a flatter SDR JPG — that’s the format, not the tool.

Whatever you pick, keep it on the Mac. Uploading images to a converter site to fix a format your own machine has read natively since 2022 is the one genuinely bad option on the list.

FAQ

Can a Mac open AVIF files without extra software?

Yes — macOS has read AVIF natively since Ventura (macOS 13), so on any recent Mac, Quick Look previews it and Preview opens it like any other image. The problem is rarely opening the file; it’s everything downstream — upload forms, print services, Office documents, and older apps that still reject .avif — which is why converting to JPG remains necessary.

Does converting AVIF to JPG lose quality?

Slightly, in principle — web-served AVIF is almost always lossy and JPG always is, so re-encoding discards a little data — but at 80–90% JPG quality the difference is invisible. The structural losses matter more: JPG flattens AVIF transparency (usually to white — convert to PNG to keep it), tone-maps HDR down to SDR, and reduces an animated AVIF to a single still frame. Convert once and keep the output rather than round-tripping.

How do I batch convert AVIF files to JPG on a Mac?

For a free one-off, select the files in Finder, right-click, and choose Quick Actions → Convert Image → JPEG. For scripted pipelines, loop sips -s format jpeg in Terminal. For a recurring chore, drag the folder into Zumkor, pick JPG, and convert everything offline in one pass — with resize presets and metadata stripping applied in the same step.