AVIF to JPG

AVIF to JPG conversion is a compatibility trade. AVIF can represent efficient still images, transparency, image sequences, high bit depth, HDR and wide color. JPG is a familiar still-image format, but it cannot carry every one of those capabilities. This page creates a new JPG from the pixels the current browser can decode; it does not simply rename the file.

What changes when AVIF becomes JPG

The Alliance for Open Media's AVIF specification defines an AV1-based image format in an ISO Base Media File Format container. MDN's image format guide describes AVIF support for features such as alpha transparency, animation and HDR.

The most reliable gain is compatibility. A workflow that cannot open AVIF may accept the generated JPG. The possible costs include another lossy encode, a larger file, flattened transparency, one-frame output and changes to color or dynamic range.

How to convert AVIF to JPG on this page

1. Add AVIF files. Choose or drop up to 30 .avif files. Each file can be up to 40 MB, and the batch can total up to 200 MB.
2. Choose JPG quality. Start at 92% for a careful photographic conversion. Lower it when byte size matters more than subtle texture.
3. Choose dimensions. Keep the decoded dimensions or limit the longest side to 4096, 2560, 1920 or 1600 pixels. Smaller images are not enlarged.
4. Choose a background. JPG cannot store alpha transparency. Select white, soft gray, dark or a custom six-digit hex color.
5. Convert and inspect. The browser decodes each AVIF. The result reports actual dimensions, byte size, container brand, image-sequence status and the implementation's metadata boundary.
6. Download. Save one JPG or package all successful results in a ZIP archive.

The page verifies that the ISO media ftyp box declares an avif or avis brand before conversion. A renamed HEIC, MP4 or unrelated ISO media file is rejected rather than being treated as AVIF.

Choose JPG quality and dimensions

The quality range is 60% to 100%. It is passed to the browser's JPEG encoder through Canvas toBlob(). The number is an encoder instruction, not a universal visual score, so exact bytes can differ between browser engines.

Practical starting points:

• 90–95%: detailed photographs, product images and files that may be inspected closely.
• 80–89%: common website uploads, email and presentations.
• 60–79%: stricter file-size situations where visible texture loss is acceptable.

An AVIF source may already use lossy compression. Creating a JPG adds another lossy stage, and 100% JPEG quality does not reconstruct original information or create a mathematically lossless result.

Dimensions often matter more than small quality adjustments. A 4000 × 3000 image contains four times as many pixels as a 2000 × 1500 image. Select a longest-side limit based on the destination, then use the result panel to verify the actual width and height.

This page does not target an exact file size. If a receiving system specifies KB or MB, create a visually acceptable JPG first and then use Image Compressor to measure and reduce the actual output.

Transparency needs a background

AVIF can include an alpha plane; JPG cannot. The converter paints the selected background across the output canvas before drawing the AVIF. Transparent and partially transparent pixels are therefore blended with that color.

Choose the color for the final destination:

• White for forms, documents and most light pages.
• Soft gray when pale edges need separation from white.
• Dark for assets intended for a dark interface or slide.
• A custom hex value when the exact page or brand background is known.

Soft shadows and antialiased edges contain partially transparent pixels. They can look clean on one background and develop a halo on another. Inspect the complete perimeter in the JPG preview.

This implementation does not fully parse AVIF item properties to declare whether a specific source contains alpha. It applies the background safely and reports that source alpha was not fully inspected rather than guessing.

Image sequences become one still frame

An AVIF container can declare the avis brand for an image sequence. JPG has no equivalent animation or frame-timing model. When avis is present, the page labels the source as a sequence and exports only the first image decoded by the browser.

That output can be useful as a thumbnail, poster or static fallback. It does not preserve later frames, durations, looping or sequence-level behavior. Keep the original AVIF when motion matters, or use an animation-aware workflow that explicitly supports the desired destination format.

The tool detects the sequence brand in the ftyp box. It does not enumerate every item or expose frame selection.

HDR, wide color and browser decoding

AVIF can store higher bit depth, HDR transfer functions and wide color. A browser may color-manage and tone-map those values while decoding and drawing to Canvas. The new JPG reflects the pixels produced by that browser pipeline; it does not preserve the source AVIF's signaling as equivalent container metadata.

This matters most for bright highlights, saturated colors, smooth gradients and images authored for HDR displays. Compare the JPG on the intended display and browser. Do not delete the AVIF after seeing only a small preview.

The result states that Alpha/HDR properties were not fully inspected and that browser-decoded pixels were exported. This is more accurate than claiming the output retained the source bit depth or color profile.

Use a color-managed desktop application when exact profile, high-bit-depth or HDR preservation is a requirement. JPG may be the correct delivery file for compatibility, but it should not replace the AVIF master in that workflow.

Check the generated JPG

Review each result in this order:

1. Frame: if the source is an image sequence, confirm the first decoded frame is useful.
2. Orientation and crop: make sure the browser-decoded image is upright and complete.
3. Transparency edges: inspect shadows, cutouts, rounded corners and logos against the selected background.
4. Highlights and color: compare bright areas, saturated colors and gradients for clipping or shifts.
5. Fine detail: check hair, fabric, foliage, text and high-contrast edges for JPEG artifacts.
6. Dimensions and bytes: verify the actual output size rather than assuming JPG is smaller.
7. Metadata: assume source container metadata and color properties were not copied.

AVIF can be more efficient than JPG. A high-quality JPG may be larger even though it offers fewer format features. That is not automatically a conversion failure.

Illustrative AVIF to JPG examples

Prepare an AVIF photo for an older upload form

Assume a 2400 × 1600 still AVIF is rejected by a website. Keep dimensions, select white and use 90% quality. The output remains 2400 × 1600. Its actual bytes depend on the decoded photograph and browser encoder.

Flatten a transparent product image

Assume a 2000 × 2000 AVIF contains a cutout with a soft alpha shadow. Choose the exact background used by the destination and 92% quality. Inspect the full edge and shadow before download because the compositing is permanent in JPG.

Create a static preview from an AVIF sequence

Assume the container declares avis and the decoded frame is 1920 × 1080. Limit the longest side to 1600 pixels. The JPG becomes 1600 × 900 and contains only the first decoded frame.

Illustrative examples. Exact bytes, tone mapping and visible artifacts depend on the source AVIF, browser decoder, display and JPEG encoder.

When JPG is not the better format

Keep AVIF when the destination supports it and you need its delivery efficiency, transparency, HDR, wide color or sequence behavior. Converting only because JPG is familiar can increase bytes and remove useful capabilities.

JPG is appropriate when broad still-image compatibility is the dominant requirement. It is less appropriate as a replacement master for continued editing, high-dynamic-range work or transparent assets.

If the destination supports WebP or PNG but not AVIF, choose the output according to the content: PNG for lossless sharp graphics and transparency, WebP for modern web delivery where supported, and JPG for conventional photographic workflows.

Local conversion and alternatives

The converter services reviewed for this guide offer broader hosted workflows:

• CloudConvert provides server-side AVIF conversion within a multi-format platform and exposes additional conversion controls.
• FreeConvert is useful when hosted processing, cloud or URL imports, and additional image settings are required.
• Convertio supports cloud-source workflows and many output formats.

base97 is intentionally narrower. Its verified differences are local browser processing, ftyp brand validation, explicit avis sequence reporting, deliberate transparency backgrounds, per-file failure isolation and a detailed result before individual or ZIP download. It does not claim more accurate tone mapping or smaller JPG files than server-side converters.

This version does not support URLs, cloud drives, server conversion, metadata retention, HDR-preserving output, frame selection, all-frame export, exact target sizes, multiple output formats or per-file settings.

Troubleshoot AVIF to JPG conversion

The file is rejected before conversion

The page checks the ISO media ftyp box for avif or avis. Renaming another file to .avif is not enough. Export or obtain a valid AVIF source.

The browser cannot decode the AVIF

The current browser may not support the file's AV1 profile, bit depth, chroma mode or other feature. Try an up-to-date browser or use a desktop/server converter with a broader AVIF decoder. The page does not upload the file to fall back to a server.

The JPG is larger than the AVIF

That can be normal because AVIF may encode the same photograph more efficiently. Lower JPG quality, reduce dimensions or keep the AVIF if the destination supports it.

Colors or highlights look different

HDR, high-bit-depth and wide-gamut data can change when browser-decoded pixels are drawn to Canvas and encoded as JPG. Use a color-managed workflow when those properties must be preserved.

Transparent edges have a halo

Convert again from the original AVIF using the exact destination background. Do not repeatedly re-encode the generated JPG.

The image sequence stopped moving

JPG is a still format. This tool exports one decoded frame and does not preserve sequence timing or later frames.

Conversion becomes slow

AVIF decoding and large Canvas buffers can require substantial CPU and memory. Convert fewer files at once. Images above 12,000 pixels on either side or 60 megapixels are blocked by this page.

AVIF to JPG FAQ

Can AVIF be converted to JPG without losing quality?

No. JPG encoding is lossy, and conversion can also reduce AVIF capabilities such as high bit depth, HDR, wide color, transparency or animation. Use a higher JPG quality, keep the dimensions and inspect the result when compatibility matters more than retaining those features.

What happens to transparent AVIF pixels?

JPG has no alpha channel. This page paints the selected background before drawing the browser-decoded AVIF, so transparent and partially transparent pixels are composited onto that color.

Does this preserve an animated AVIF image sequence?

No. If the AVIF container declares the avis sequence brand, the page reports it and exports only the first image decoded by the browser as a still JPG. Timing, later frames and looping are not retained.

Does the JPG keep AVIF metadata, HDR or its color profile?

No. The Canvas export creates a new JPG from browser-decoded pixels. This implementation does not copy AVIF container metadata, HDR signaling, high-bit-depth data or source color profiles into equivalent JPG structures.

Are my AVIF files uploaded to base97?

No. The current tool checks the AVIF container brand, decodes, resizes, composites, encodes and packages the selected files with browser-side code on the current device. It does not send those image files to a base97 server.