Nifty Tools

AVIF to JPG

Convert avif to jpg in your browser. Batch up to 50 images at a time. No upload, no signup, no watermark. Quality slider, alpha flattens to white.

Processing mode: Local Browser-local

  • No file leaves your browser
  • Mode: Browser-local
  • 250+ files processed in the last 24h
Waiting for AVIF images.

How to use it

AVIF to JPG Converter — Free, In Your Browser

  1. Drop your AVIF files onto the workspace, paste from the clipboard, or pick them with the file picker. Up to 50 images per batch, 100 MB per file.
  2. Adjust the quality slider if you want — the default 0.92 usually produces files close to the source for ordinary photographs.
  3. Click Convert. Each image decodes through the browser's built-in AVIF path, draws into a canvas with an opaque white background, and re-encodes as JPG via `canvas.toBlob("image/jpeg", quality)`. Download individually or grab the whole batch as a single ZIP.

Good for

Common use cases

AVIF lands smaller than WebP or JPEG at the same visual quality and renders in current Chrome, Edge, Firefox, and Safari, but the support story collapses the moment the file leaves the browser. Recent Photoshop versions support AVIF natively, but older perpetual-licence and CS-era installs cannot read it without a plugin or refuse it outright. Many older or locked-down Office installs — perpetual-licence Office 2019-era deployments and enterprise machines without current Microsoft 365 image-format updates — still fail to render AVIF reliably; the paste lands as a broken-image placeholder that sends the document back to the sender. Major marketplace upload flows (Etsy lists `.jpg`, `.gif`, `.png`, `.svg`, `.heic` as accepted product images and does not name AVIF; eBay and Amazon Seller Central upload tooling has historically centred on JPG/PNG/GIF) do not document AVIF as an accepted format. Email clients running on older Outlook versions render the attachment as a broken-image icon. Print-on-demand pipelines like Printful and Society6 document JPG and PNG as accepted raster uploads with no AVIF entry. The cheapest fix is swapping the container — JPG when the destination cares about file size and accepts photographic content (which is almost always), PNG via the sister tool AVIF to PNG when transparency or lossless reproduction matters. Doing the conversion in the browser keeps confidential mockups, design comps, and licensed product photography off third-party servers — the AVIF source never leaves the tab, the JPG materialises locally, and the only network traffic is the page load itself.

Processing mode

Browser-local

Files are processed by your browser. They never reach our servers.

Questions

AVIF to JPG Converter — Free, In Your Browser FAQ

Why won't Etsy, my older Photoshop, or my locked-down Office build accept the AVIF I saved from the web?

The format itself is the issue for that surface. Etsy's official image requirements list `.jpg`, `.gif`, `.png`, `.svg`, and `.heic` as accepted product images, with no AVIF in the list — uploads of AVIF files may fail validation before the listing flow can continue. Recent Photoshop versions support AVIF natively, but older perpetual-licence and CS-era installs reject the file without a plugin. Many older or locked-down Office installs — perpetual-licence Office 2019-era deployments and enterprise machines without current Microsoft 365 image-format updates — render AVIF as a broken-image placeholder when pasted into Word, Outlook, or PowerPoint. Converting to JPG removes the format dependency entirely, and at quality 0.92 the visual result is usually close to the AVIF source for ordinary photographs.

Does converting AVIF to JPG lose image quality?

There is one lossy step. The AVIF decodes into a canvas, then re-encodes as JPG at the quality you select (default 0.92, a high-quality setting for ordinary photographs). For most photographic content the result is usually close to the source, but it is not bit-for-bit identical. AVIF was tuned for compression density, so the file size sometimes goes *up* when you swap to JPG — that is expected, the AVIF was already a tighter encode of the same visual content. If the AVIF itself was an export from a workflow that started life as a JPG (common for stock photos and many web-delivery pipelines), you are not losing anything meaningful in the conversion. If you need lossless preservation of an image with transparency, use AVIF to PNG (the sister tool) instead.

What happens to the transparent regions in my AVIF?

JPG does not support an alpha channel, so transparent regions in the source AVIF flatten to white before encoding. The tool fills the canvas with a solid white background before drawing the image, which means transparent areas come through as crisp white rather than the black artefact that some converters produce when they drop the alpha channel without filling. If your AVIF is a logo, icon, or product cutout with intentional transparency that needs to survive the conversion, JPG is the wrong target format — pick AVIF to PNG instead. JPG is the right target when the AVIF is a photograph, a screenshot, or any artwork already on a flat background.

Which browsers can run this AVIF converter?

Every current Chrome, Edge, Firefox, and Safari. AVIF decoding rolled out across the major engines at different times — Chrome 85 (August 2020), Firefox 93 (October 2021), iOS Safari 16 (September 2022), macOS Safari 16.4 (March 2023 — earlier 16.x desktop builds shipped partial or no AVIF support), and Edge 121 (January 2024). The tool relies on the browser's built-in `<img>` decoder for AVIF, so any browser that renders an `.avif` inline on a webpage can also run this converter. The JPG encode step uses `canvas.toBlob("image/jpeg", quality)` — `image/jpeg` is widely supported across every current Chrome, Edge, Firefox, and Safari build, but only `image/png` is universally guaranteed by the HTML spec, so the tool checks the returned blob's MIME type and surfaces a clear error if a browser silently fell back to PNG rather than handing back a `.jpg` file that is actually PNG bytes. If you are on an older build that pre-dates AVIF support, the tool will surface a clear decode-failed error rather than producing a broken file — the workaround is to update to a current Chrome, Edge, Firefox, or Safari.

Is there a file size or batch limit?

Each AVIF must be under 100 MB and a single batch can hold up to 50 images. The 100 MB cap protects lower-RAM devices from running out of memory during decode, since the browser materialises the full pixel grid into a canvas before re-encoding. The 50-file cap keeps the ZIP build responsive — for large batches the bottleneck is browser memory, not the conversion itself, since each image processes sequentially. If you need to convert more than 50 images, run the tool twice and stack the resulting ZIPs — the conversion is deterministic, so the second batch produces output identical to what one continuous run would have written.

Why is the JPG sometimes larger than the AVIF source?

AVIF is tuned for compression density: it lands smaller than JPEG at the same visual quality, often by 20-50% for photographic content. JPG at quality 0.92 is a high-quality encode of the same pixel data, so for content that AVIF compressed aggressively the JPG ends up bigger. This is expected and not a bug — the AVIF was a denser encode of the same image, so unwinding it back into a more broadly-supported container costs file size. If size matters more than broad compatibility for the destination, leave the AVIF alone and only convert when a specific recipient or platform rejects the format.

Will this tool stay free?

The basic workflow is designed to stay free. Paid upgrades later will focus on bigger limits, batch work, OCR, saved presets, and ad-free use.