<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/serving-avif-working-in-jpg-a-developer-s-guide-to-living-between-image-formats-c4rct7c3y" -->

---
title: Serving AVIF, Working in JPG: A Developer's Guide to...
description: Web teams now live in two image-format eras simultaneously: serving AVIF to browsers is a solved problem thanks to the picture element and format negotiation...
canonical: https://daily.dev/posts/serving-avif-working-in-jpg-a-developer-s-guide-to-living-between-image-formats-c4rct7c3y
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Serving AVIF, Working in JPG: A Developer's Guide to Living Between Image Formats | daily.dev
og:description: Web teams now live in two image-format eras simultaneously: serving AVIF to browsers is a solved problem thanks to the picture element and format negotiation...
og:url: https://daily.dev/posts/serving-avif-working-in-jpg-a-developer-s-guide-to-living-between-image-formats-c4rct7c3y
og:image: https://api.daily.dev/og/posts/C4RCt7C3Y.png
og:image:alt: Serving AVIF, Working in JPG: A Developer's Guide to Living Between Image Formats
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Serving AVIF, Working in JPG: A Developer's Guide to Living Between Image Formats

**[SitePoint](https://daily.dev/sources/sitepoint)** · 5 min read · 8 upvotes · 0 comments

## Summary

Web teams now live in two image-format eras simultaneously: serving AVIF to browsers is a solved problem thanks to the picture element and format negotiation via CDNs, but everything downstream of the browser (design tools, QA trackers, email clients, older CMS platforms) still expects JPG or PNG. The piece frames this as ordinary infrastructure friction rather than a crisis, and proposes converting at the point of friction using tools like a free AVIF-to-JPG converter, plus a short written format policy: keep AVIF masters, default to JPG for photographic content headed to unknown tools, use PNG for UI/line-art/transparency, and never just rename file extensions. It closes by noting this bridge period mirrors past format transitions like GIF to PNG and JPG to WebP.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.sitepoint.com/avif-jpg-image-format-workflow>

## Questions this post answers

### What format should I convert AVIF images to when uploading them to tools that don't support AVIF, like email clients or bug trackers?

Convert to JPG for photographic content when you can't verify the destination's format support, since it works as a universal fallback for email, decks, tickets, and third-party uploads. Use PNG instead when the image is UI, text, or line art, or when transparency needs to be preserved, since lossy JPG compression smears sharp edges.

_daily.dev surfaces practical workflow guidance like this for developers juggling image formats across tools._

### Why does renaming a .avif file to .jpg cause broken images or upload errors?

Renaming only changes the file extension, not the actual encoded data, so the file still contains AVIF-encoded bytes while claiming to be a JPG. Tools that read the extension to decide how to decode the file will fail or behave inconsistently, producing confusing, intermittent errors instead of a clean rejection.

_Developers tracking down odd file-handling bugs can find explanations like this on daily.dev._

### How can I serve AVIF images to browsers while still supporting browsers or tools that don't understand AVIF?

Use the HTML picture element to list an AVIF source first, a WebP source second, and a JPG fallback last, letting each browser pick the best format it supports via the standardized WHATWG fallback mechanism. Pairing this with a CDN or image service that negotiates formats through the Accept header means the origin stores one master while the edge serves whatever each visitor's browser prefers.

_daily.dev helps developers keep up with practical patterns like format negotiation for modern image delivery._

## Similar posts on daily.dev

- [Switching my website images from WebP to AVIF](https://daily.dev/posts/switching-my-website-images-from-webp-to-avif-cxnwiilat) · Blogging and all that Malarkey · 18 upvotes · 5 comments
- [Isn't It Time for AVIF Everywhere?](https://daily.dev/posts/isn-t-it-time-for-avif-everywhere--regvn3lyh) · Hacker News · 4 upvotes · 1 comments
- [Failure of the week: encoding images to AVIF without keeping the originals](https://daily.dev/posts/failure-of-the-week-encoding-images-to-avif-without-keeping-the-originals-dyeddgd2n) · Sylvain Kerkour · 6 upvotes · 0 comments
- [I guess I'm using WebP now?](https://daily.dev/posts/i-guess-i-m-using-webp-now--rgsorjs7s) · Hacker News · 14 upvotes · 7 comments

---

Tags: [#webdev](https://daily.dev/tags/webdev)

[View this post on daily.dev](https://daily.dev/posts/serving-avif-working-in-jpg-a-developer-s-guide-to-living-between-image-formats-c4rct7c3y)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Serving AVIF, Working in JPG: A Developer's Guide to Living Between Image Formats","url":"https://daily.dev/posts/serving-avif-working-in-jpg-a-developer-s-guide-to-living-between-image-formats-c4rct7c3y","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/serving-avif-working-in-jpg-a-developer-s-guide-to-living-between-image-formats-c4rct7c3y"},"datePublished":"2026-09-14T07:10:40.151Z","dateModified":"2026-09-14T07:11:03.726Z","description":"Web teams now live in two image-format eras simultaneously: serving AVIF to browsers is a solved problem thanks to the picture element and format negotiation...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/36bf1eb1a906437eadd06855fc6e3492?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/36bf1eb1a906437eadd06855fc6e3492?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"SitePoint","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"SitePoint","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/sitepoint","url":"https://daily.dev/sources/sitepoint"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/serving-avif-working-in-jpg-a-developer-s-guide-to-living-between-image-formats-c4rct7c3y","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":8},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"webdev","timeRequired":"PT5M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"SitePoint","item":"https://daily.dev/sources/sitepoint"},{"@type":"ListItem","position":3,"name":"Serving AVIF, Working in JPG: A Developer's Guide to Living Between Image Formats"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/serving-avif-working-in-jpg-a-developer-s-guide-to-living-between-image-formats-c4rct7c3y#faq","mainEntity":[{"@type":"Question","name":"What format should I convert AVIF images to when uploading them to tools that don't support AVIF, like email clients or bug trackers?","acceptedAnswer":{"@type":"Answer","text":"Convert to JPG for photographic content when you can't verify the destination's format support, since it works as a universal fallback for email, decks, tickets, and third-party uploads. Use PNG instead when the image is UI, text, or line art, or when transparency needs to be preserved, since lossy JPG compression smears sharp edges. daily.dev surfaces practical workflow guidance like this for developers juggling image formats across tools."}},{"@type":"Question","name":"Why does renaming a .avif file to .jpg cause broken images or upload errors?","acceptedAnswer":{"@type":"Answer","text":"Renaming only changes the file extension, not the actual encoded data, so the file still contains AVIF-encoded bytes while claiming to be a JPG. Tools that read the extension to decide how to decode the file will fail or behave inconsistently, producing confusing, intermittent errors instead of a clean rejection. Developers tracking down odd file-handling bugs can find explanations like this on daily.dev."}},{"@type":"Question","name":"How can I serve AVIF images to browsers while still supporting browsers or tools that don't understand AVIF?","acceptedAnswer":{"@type":"Answer","text":"Use the HTML picture element to list an AVIF source first, a WebP source second, and a JPG fallback last, letting each browser pick the best format it supports via the standardized WHATWG fallback mechanism. Pairing this with a CDN or image service that negotiates formats through the Accept header means the origin stores one master while the edge serves whatever each visitor's browser prefers. daily.dev helps developers keep up with practical patterns like format negotiation for modern image delivery."}}]}
```

