Home › Guides › JPEG, PNG, WebP, and AVIF

JPEG, PNG, WebP, and AVIF: Which Image Format to Use

By Ryan • Updated November 18, 2026 • 9 min read

The file extension is the last decision, not the first. A photograph, a screenshot, a logo with a transparent edge, and a picture someone has to open in an old mail client are four different files. Two of them should not be JPEG. One of them cannot be AVIF if you are exporting from this site.

Quick answer: Photographs that will be published on a site you control should be resized, then saved as WebP. Photographs that must open everywhere should be JPEG. Screenshots, logos, QR codes, and anything with small text should be PNG. AVIF is often smaller than WebP and is not in the Image Studio export menu. The byte-level JPEG versus WebP comparison lives in its own article.

Start from the picture, not the file extension

A format is a set of rules for throwing information away, or for refusing to. JPEG was built for photographs. PNG was built so a screenshot, a logo, and a diagram could be saved and opened again with the same pixels. WebP does both jobs in one container, with an alpha channel that JPEG never had. AVIF is a newer still-image form of the AV1 video codec, and it often stores a photograph in fewer bytes than WebP. It is also the one format in that list that Image Studio cannot write.

The export menu on the studio has three choices: JPEG, PNG, and WebP. The quality slider is passed to the browser as the second argument of canvas.toBlob. Browsers use that number for JPEG and WebP. They ignore it for PNG, because PNG's compression is lossless: the slider cannot make a PNG "more lossy." If you need every pixel back, choose PNG and stop looking at the slider. If you need a photograph to get smaller, choose JPEG or WebP and then set the dimensions first. The reason order matters is covered in Resizing vs Compressing.

The byte comparison between JPEG and WebP, including Google's published SSIM study, already has its own article: WebP vs JPEG. This page is the decision in front of the dropdown, including the two formats that article does not spend its length on.

What each format actually keeps

Format Pixels Transparency Image Studio export Use it for
JPEG Lossy DCT. Color is stored more coarsely than brightness (usually 4:2:0). No. Transparent pixels become opaque, typically black. Yes. Slider applies. Photographs for email, print shops, and older tools.
PNG Lossless DEFLATE. Optional palette (PNG-8) for flat colors. Yes. Yes. Slider does nothing. Screenshots, UI, text, logos, QR codes, line art.
WebP Lossy (VP8) or lossless. The studio only exposes the lossy slider. Yes, including on a lossy photo. Yes. Slider applies. No lossless switch. Photographs and cut-outs on a website.
AVIF AV1 still image. Lossy or lossless. Often smaller than WebP, slower to encode. Yes. No. Decode-only, and only if your browser can decode it. A build step (sharp, Squoosh, an image CDN), not this page.

Current Chrome, Edge, Firefox, and Safari all display WebP. Safari added it in version 14 (2020). AVIF arrived later: Chrome 85, Firefox 93, Safari 16. A marketing site aimed at current phones can serve WebP without a fallback and not think about it. A file that has to open in an old Windows mail client, a print-shop portal, or a Word document from 2016 should be JPEG or PNG. "The web supports it" and "this form accepts it" are different tests.

Photographs

A camera JPEG is already lossy. Saving it again as JPEG at a high slider value throws a little more away. Saving it as PNG does not get the discarded detail back, and the PNG is often larger than the JPEG you started with, because PNG is then losslessly compressing a noisy photographic bitmap. That is the wrong trade. Use PNG when the source really is exact: a screenshot, a chart exported from a spreadsheet, a logo.

For a photograph that will be published on a page you control, WebP at a slider around 75–85, after you have resized to the pixel size the layout needs, is the usual export. For a photograph that will be emailed or handed to a printer who asked for JPEG, stay on JPEG. The slider numbers and the 4:2:0 color bleed on red type are in the JPEG compression guide. Do not re-encode the same JPEG in a loop. Keep the camera file and export a derivative. That generation-loss rule is the subject of Lossy vs Lossless.

JPEG has no notion of a partial pixel. If the source is a PNG with a transparent background and you pick JPEG, the browser paints those pixels into an opaque image. In practice the empty area comes out black. If the cut-out has to stay a cut-out, export WebP or PNG and check the comparison view against a non-white page in your head: the studio preview sits on the page background, so a black fringe is easy to miss until the file lands on a colored hero.

Screenshots, UI, and anything with small text

JPEG's 8×8 blocks are invisible on a leaf and obvious on a glyph. A screenshot of a terminal, a dialog, or a spreadsheet should stay PNG. WebP lossy can do better than JPEG on the same screenshot, and it still rings the stems of letters if you push the slider down. If the text has to be read, PNG is the boring correct answer. The file is larger. That is the point.

Flat-color graphics, simple logos, and icons with a handful of colors are the case where an indexed PNG is tiny. The studio does not offer a "256 colors" switch. It writes a normal PNG from the canvas. For a one-color logo that is already a small PNG, running it through the studio at the same pixel size will not magically shrink it, and it can grow if the canvas output is a 24-bit or 32-bit PNG of pixels that used to be a palette. Leave those files alone unless you are resizing them.

QR codes and barcodes are the strict version of the same rule. A lossy encoder changes the modules. Phone cameras are tolerant, until they are not. Export PNG, at the pixel size you will print, and do not let a later tool recompress it as JPEG at quality 60.

What the canvas throws away besides the format

Every download from Image Studio is a new file painted from pixels. The browser decodes the source into an 8-bit canvas. A few consequences follow, and they apply no matter which of the three formats you pick:

AVIF, without pretending this site writes it

AVIF is worth knowing about so you do not hunt for it in the dropdown. On photographic images, published encoder comparisons (including the work vendors did while shipping AV1 stills) usually show AVIF smaller than WebP at a similar visual quality, at the cost of a slower encode. Browser support in current desktop and mobile versions is broad. Email clients and office apps are spottier. A page can offer AVIF with a WebP or JPEG fallback using the <picture> element. That markup is described in the Core Web Vitals image guide.

If your browser can decode an AVIF, you can drop it on Image Studio and re-encode to WebP or JPEG. You will not keep AVIF's size advantage. You also cannot damage the original AVIF: the studio never writes back over the file you opened. It downloads a new one. For a site that should actually ship AVIF, encode it where you build the site (libvips or sharp are the usual libraries) and keep WebP or JPEG next to it for clients that still lack AVIF.

A short decision procedure

  1. Open the file in Image Studio. If the metadata panel shows a GPS coordinate and this export will be published, you do not need to do anything extra: the new file will not contain it. Confirm that by opening the download, not by trusting the filename.
  2. Crop to the frame you will actually show. Set the width and height to the pixels the destination needs. A 6000-pixel JPEG saved as WebP is still a 6000-pixel image.
  3. If you can see small text, a logo edge, a QR code, or a transparent background that must survive, choose PNG. Ignore the slider.
  4. If it is a photograph for a website, choose WebP and leave the slider near 80. Drag the comparison divider across a face, a sky, and any type that sits on the photo.
  5. If the receiver asked for JPEG, or you are not sure they can open WebP, choose JPEG at the same slider. Zoom once with Zoom & Inspect before you download.
  6. Name the download for the destination (hero-1200.webp in your own files). The studio's automatic name includes the pixel width, which is useful, and it does not include the quality, so keep the original elsewhere.

Social pixel sizes are a separate table. Use the Instagram and social sizes guide for those numbers, then come back here only to pick JPEG versus PNG. Instagram will recompress what you upload. Give it a clean JPEG at the right pixel size rather than a PNG of a photograph.

Frequently Asked Questions

Does Image Studio export AVIF?

No. The format menu is JPEG, PNG, and WebP. If your browser can decode an AVIF you dropped in, you can re-encode it to one of those three. To publish AVIF, encode it in your site's build step and keep a WebP or JPEG fallback.

Will the quality slider shrink a PNG?

No. Browsers ignore the quality argument for image/png because PNG compression is lossless. Choose PNG when the pixels have to survive, and use the slider only for JPEG and WebP.

What happens to a transparent background if I pick JPEG?

JPEG has no alpha channel. Transparent pixels are flattened to an opaque color, usually black. Use PNG or WebP when the cut-out has to stay a cut-out.

Can I drop a HEIC or a camera RAW file on the studio?

Only if the browser can decode it. Chrome generally does not decode iPhone HEIC or camera RAW formats such as CR2 and NEF. Export a JPEG from the camera app or your photo editor first.

Export JPEG, PNG, or WebP locally

The format menu is on the compress tab. Files stay in the browser.

Open Image Studio