Which browsers can decode the source AVIF for this conversion?

AVIF decoding support: Chrome 85+ (August 2020), Firefox 93+ (October 2021), Safari iOS 16.0+ / macOS 16.1+ (September 2022 — still AVIF), Safari 16.4+ (27 March 2023 — full support including animation, grid, and image sequences on macOS Ventura 13.3+ / iOS 16.4+), Edge 121+ (January 2024), Opera 71+. Older browsers cannot decode AVIF natively — the conversion will fail in Safari 16.0–16.3 and earlier. JPEG output via Canvas toBlob('image/jpeg') is universally supported, so this conversion direction works in any browser that can decode AVIF.

AVIF to JPG Converter Online — Modern AVIF to Universal JPEG

Q: Why is the JPG often larger than the source AVIF?

AVIF's AV1 codec uses sophisticated intra-prediction modes (recursive partitioning, directional + non-directional predictors, transform coefficient coding with arithmetic compression) that pack natural-image entropy 2× more efficiently than JPEG's 1992-era 8×8 DCT + Huffman pipeline (per ITU-T T.81 Annex K quantisation). Converting AVIF → JPG cannot recover encoding efficiency — the JPEG must encode the decoded pixels with its older, less efficient algorithm. Expect 1.5–2.5× size growth for photographs at JPEG quality 85.

Q: What does the JPG quality slider control?

Quality 1–100 maps to JPEG quantisation table scaling per ITU-T T.81 Annex K. Higher = smaller quantisation steps = more DCT coefficients preserved = larger file. Quality 90+ is visually indistinguishable from lossless on most photographs; 75–85 is the standard web sweet spot; below 70 produces visible 8×8 block boundaries and ringing near sharp edges. Canvas toBlob('image/jpeg', quality) maps quality 0–1 to the underlying browser encoder's Q-table scaling.

AVIF to JPG Converter — Next-Gen Format to Universal JPEG

AVIF (AV1 Image File Format, AOMedia v1.2.0; also ISO/IEC 23000-22:2019 MIAF (first edition June 2019)) pairs the AV1 video codec (AOMedia Bitstream Spec v1.0.0, 25 June 2018) with the HEIF container (ISO/IEC 23008-12). It typically delivers ~2× better compression than JPEG (ITU-T T.81 / ISO/IEC 10918-1, 18 September 1992) at equivalent perceptual quality — the result of AV1's recursive partitioning, sophisticated intra-prediction modes, and arithmetic coding versus JPEG's older 8×8 DCT + Huffman pipeline. Converting AVIF → JPEG sacrifices size for universal compatibility: every legacy editor, email client, CMS, print pipeline, and Office document accepts JFIF-wrapped JPEG (Hamilton, C-Cube Microsystems, 1 September 1992). The conversion runs locally via WHATWG Canvas 2D Context + HTMLCanvasElement.toBlob('image/jpeg', quality). AVIF decoding is required: Chrome 85+ (August 2020), Firefox 93+ (October 2021), Safari iOS 16.0+ (still AVIF, September 2022), Safari 16.4+ (full AVIF, March 2023). JPEG output via toBlob is universally supported.

How to convert AVIF to JPG

Drop an .avif file onto the tool or click to browse — single file or batch. Requires Chrome 85+, Firefox 93+, or Safari 16.4+ for AVIF decoding.
Pick a quality level (1–100). 85–90 is the safe sweet spot for photos; 75 is fine for most web use; below 70 introduces visible compression artefacts.
Pick a background colour for transparent regions (default white) — alpha pixels are composited against this since JPEG has no alpha channel per ITU-T T.81.
Review before/after sizes (JPG typically 1.5–2.5× larger for photos, the inverse of AVIF advantage), then download the JFIF-wrapped JPG.

Common use cases

Shipping an AVIF photo to an email client, CMS, or vendor portal that strictly accepts JPG/JPEG MIME types only.
Opening an AVIF download in a legacy desktop editor (Photoshop pre-CC 2024, certain RAW workflows, archival systems) that doesn't decode AVIF.
Producing JPG fallback copies for cross-platform sharing with users on Safari 14.0–15.x / iOS 14–15 (no AVIF decode support); Safari 16.0–16.3 needs JPG only for animated AVIFs.
Converting AVIF exports from web tools to JPG for print services, photo books, or archival workflows that mandate JPEG.

Frequently asked questions

What is AVIF and why convert to JPG?

AVIF (AOMedia v1.2.0; ISO/IEC 23000-22:2019 MIAF (first edition June 2019)) pairs AV1 codec (AOMedia v1.0.0 June 2018) with HEIF container (ISO/IEC 23008-12). ~2× better compression than JPEG (ITU-T T.81, Sept 1992). Convert when destination cannot decode AVIF — legacy editors, certain CMSes, print pipelines.

Why is the JPG often larger than the source AVIF?

AVIF's AV1 codec uses recursive partitioning + sophisticated intra-prediction + arithmetic coding, packing entropy 2× more efficiently than JPEG's 1992 8×8 DCT + Huffman. Re-encoding can't recover efficiency — JPEG's older algorithm is 1.5–2.5× larger for photos at quality 85.

What happens to the AVIF alpha channel during conversion?

AVIF supports 8-bit and 10-bit alpha (auxiliary image item per ISO/IEC 23008-12). JPEG has no alpha (T.81). Tool composites transparent AVIF pixels against configurable background (default white) via Canvas 2D, encodes opaque RGB to JFIF. Keep AVIF or convert to PNG if transparency matters.

Which browsers can decode the source AVIF?

Chrome 85+ (Aug 2020), Firefox 93+ (Oct 2021), Safari iOS 16.0+ (Sept 2022, still AVIF), Safari 16.4+ (March 2023 — full support including animation/grid), Edge 121+ (January 2024), Opera 71+. Older browsers fail. JPEG output via toBlob('image/jpeg') is universally supported.

What does the JPG quality slider control?

Quality 1–100 maps to JPEG quantisation tables per ITU-T T.81 Annex K. Higher = smaller quantisation steps = more DCT coefficients preserved = larger file. Quality 90+ visually indistinguishable from lossless; 75–85 is web sweet spot; below 70 produces visible block boundaries and ringing.

What you trade going AVIF → JPG — and the AVIF decode requirement

The conversion path is decode-the-AVIF-to-pixels then re-encode-as-JPEG with two technical considerations bare format-swapping tools often miss: (1) AVIF supports 8-bit and 10-bit alpha channels (alpha plane carried in auxiliary image item per ISO/IEC 23008-12 HEIF); JPEG has no alpha so transparent pixels must be composited against a configurable background colour (default white) using the WHATWG Canvas 2D Context before encoding. (2) AVIF supports HDR + Wide Color Gamut (Rec.2020 colour space) but the standard Canvas 2D path defaults to sRGB (IEC 61966-2-1:1999); HDR AVIFs are tone-mapped to SDR sRGB before JPEG encoding, losing wide-gamut and high-dynamic-range information. Quality control (1–100) maps to JPEG quantisation table scaling per ITU-T T.81 Annex K — 85 is the standard web sweet spot. Output file size is typically 1.5–2.5× larger than the source AVIF for photographs (the inverse of AVIF's ~2× compression advantage), so this conversion is appropriate only when compatibility outweighs size — emailing photos to non-technical recipients, importing into a legacy editor, producing JPG fallbacks for sites that can't serve AVIF. Critical browser requirement: AVIF still-image decoding requires Chrome 85+, Firefox 93+, or Safari iOS 16.0+ (September 2022); animated AVIF + image sequences require Safari 16.4+ (March 2023). Safari 14.0–15.x cannot decode any AVIF and the tool will fail.

AVIF source decoded per AOMedia AV1 Image File Format spec v1.2.0
AV1 codec decoding per AOMedia Bitstream Spec v1.0.0 (25 June 2018)
Adjustable JPEG quality 1–100 mapped to ITU-T T.81 Annex K quantisation tables
Configurable background colour for alpha compositing (AVIF transparency → opaque JPEG)
Output JFIF v1.02 container (Hamilton 1992) accepted by every legacy editor and CMS
Browser-side via WHATWG Canvas toBlob('image/jpeg', quality) — works in every browser that can decode AVIF (Chrome 85+, Firefox 93+, Safari 16.4+)

Free. No signup. No file uploads. Ads via AdSense (consent required).

Sources (5)

Alliance for Open Media (AOMedia) — Storage and Transport Format WG (2024). AV1 Image File Format (AVIF). AOMedia specification v1.2.0 (aomediacodec.github.io/av1-avif/); also formalised in ISO/IEC 23000-22:2019 MIAF (first edition June 2019) — HEIF-derivative container with AV1 bitstream payload.
AOMedia Codec Working Group (2018). AV1 Bitstream & Decoding Process Specification. AOMedia v1.0.0 (25 June 2018; v1.0.0-errata1 8 January 2019) — open royalty-free video codec underlying AVIF stills.
ISO/IEC JTC 1/SC 29/WG 11 (MPEG) (2017). Information technology — High efficiency coding and media delivery in heterogeneous environments — Part 12: Image File Format (HEIF). ISO/IEC 23008-12:2017 (first edition) / 2022 (second edition) / 2025 (third edition) — base container that AVIF derives from.
ITU-T (CCITT) Study Group VIII & ISO/IEC JTC 1/SC 29/WG 10 (JPEG) (1992). Information technology — Digital compression and coding of continuous-tone still images: Requirements and guidelines. ITU-T Recommendation T.81 (18 September 1992) / ISO/IEC 10918-1:1994 — target JPEG baseline DCT bitstream.
WHATWG (live). HTML Living Standard — Canvas 2D Context + HTMLCanvasElement.toBlob(). html.spec.whatwg.org/#2dcontext (browser AVIF decoding: Chrome 85+ August 2020, Firefox 93+ October 2021, Safari 16.4+ March 2023; conversion via toBlob('image/jpeg', quality) is universally supported including Safari).

These are the W3C, ISO/IEC, ITU-T, and IETF specifications the tool implements or builds on. Locate them on w3.org, iso.org, itu.int, or datatracker.ietf.org.