Amazon Switches Kindle Covers to AVIF: 2026 Workflow
If you tried to download a Kindle book cover from Amazon in mid-September 2026, you may have noticed something quietly strange: the file saved to your disk ended in .avif instead of .jpg or .png. That change is not an accident, not a glitch, and not a one-off experiment with a single product image. As reported by Michael Kozlowski at Good e-Reader on September 14, 2026, Amazon has switched every image on its main retail site — including Kindle book cover art and Kindle e-reader product photos — from JPEG and PNG to AVIF, the AV1 Image File Format. International storefronts have followed the same path. Amazon Canada is currently the only major Amazon domain still serving JPEG and PNG.
For ordinary readers, this is invisible. Browsers that support AVIF — every shipping Chrome, Edge, Firefox, Opera and Safari build since 2023 — render the cover perfectly. For anyone running an ebook management workflow that touches cover art — Calibre users, self-publishers, librarians, bloggers who pull book thumbnails, reviewers who grab a cover for a post — this is a small but real problem. Calibre, the dominant open-source ebook manager, does not read AVIF. WordPress does not read AVIF without a plugin. Most static-site generators and CMSes treat .avif as an unknown file extension.
The change exposes a gap between what the web publishing industry has standardized on and what the local-tools ecosystem has caught up to. That gap is the story here. Below: what AVIF is, why Amazon switched, what breaks in practice, and how to keep your ebook cover workflow working.
What AVIF actually is, in plain language
AVIF is the still-image container derived from the AV1 video codec. The Alliance for Open Media — whose members include Google, Netflix, Amazon, Microsoft, Apple, and Meta — developed AV1 as a royalty-free successor to H.264, and AVIF is the way that codec gets used for individual images rather than video frames. The codec itself first shipped in 2019; the AVIF image container specification reached version 1.0.0 in February 2019 and is currently at version 1.2.0.
Compression is the headline. The Alliance for Open Media publishes a side-by-side comparison: AVIF delivers over 50% smaller files than equivalent-quality JPEG, and over 30% smaller files than equivalent-quality WebP. That figure holds across photographic images, which is what most book cover art is. A 200 KB JPEG book cover compresses to roughly 80–100 KB as AVIF at the same perceptual quality.
Beyond size, AVIF supports 10-bit and 12-bit color depth, wide color gamut, alpha-channel transparency, lossless and lossy compression, animation (it can replace animated GIF and APNG), and high dynamic range. Browser support landed progressively: Chrome and Firefox in 2019–2020, Safari in 2021, and mobile platforms a year or two later. As of September 2026, every shipping browser renders AVIF natively, and the format has gone from "emerging" to "default" on the open web.
For a retailer serving millions of product images to billions of page views, a 50% bandwidth reduction is not an aesthetic preference. It is an infrastructure decision measured in petabytes per day and CDN costs. That is the underlying reason Amazon switched.
What Amazon actually changed
According to Good e-Reader's September 14 report, the AVIF rollout is site-wide and touches every image Amazon serves — book covers, Kindle e-reader product photos, accessory imagery, editorial artwork. Right-click a Kindle cover on amazon.com today and the file you download is cover.avif, not cover.jpg. The change happened with no announcement on Amazon's seller or developer channels; it is purely an infrastructure-level image-format migration.
Three storefronts are not part of the migration. Amazon Canada (amazon.ca) is currently still serving JPEG and PNG — Good e-Reader verified this in mid-September. The article does not specify which other international Amazon properties are exceptions, but it explicitly notes that "Amazon Canada still serves them with JPEG and PNG." If you live outside the United States and want a JPEG cover, this is, for now, a workaround. Treat it as temporary; Amazon tends to roll these changes out globally within a quarter or two once the technical migration is verified.
There is also a window where old behavior lingers: if you open an incognito or private-browsing session, Amazon sometimes serves the legacy format. This is consistent with how Amazon stages CDN rollouts — the new format is the default for returning visitors whose cookie state has been refreshed, but a subset of the image-serving infrastructure still serves the old format to specific request classes. Do not rely on this; it will close.
Why this matters for ebook cover workflows
The reason AVIF matters specifically for ebook tooling is that the dominant open-source ecosystem — Calibre, Sigil, the command-line ImageMagick toolchain that a lot of self-publishers use, and most static-site-generated blogs — was built around JPEG, PNG, and (more recently) WebP. Cover art that flows into an EPUB is normally JPEG or PNG. Calibre's metadata editor embeds cover images directly into the EPUB container, and the rendering path inside the EPUB reader expects JPEG or PNG.
As of Calibre 9.14.0 (released August 28, 2026), AVIF is not a supported cover-art format. If you point Calibre at an .avif file — whether through "Download cover from internet" or via a manual drag-and-drop — Calibre will treat the file as unrecognized. Some users see an explicit "unsupported format" error; others see the file silently ignored, with the book's cover slot remaining empty. The behavior depends on how the file was obtained: a file Calibre fetches over HTTP is handled by its image-download code path, while a file a user drops into the metadata dialog hits a stricter format check.
Self-publishers using WordPress for author sites face a similar problem. WordPress core supports JPEG, PNG, GIF, WebP, and ICO natively. AVIF support arrived in WordPress 6.5 (April 2024) but only when the imagick PHP extension is loaded with libavif bindings. On a default LAMP install, an .avif upload fails with "Sorry, you are not allowed to upload this file type." Static-site generators — Astro, Eleventy, Hugo, Jekyll — copy AVIF files into dist/ unchanged, but the surrounding tooling that generates responsive srcset variants usually expects JPEG or PNG.
The workaround that actually works: convert AVIF before using it
The immediate fix for anyone whose workflow expects JPEG or PNG is to convert the .avif file before passing it to the downstream tool. Three approaches work in practice, in order of how widely they apply.
1. Convert with ImageMagick (command line, the canonical choice for self-publishers). ImageMagick 7.1.0-49 and later supports AVIF via the libavif delegate. On a Linux system with the delegate installed, the conversion is one line:
magick convert cover.avif cover.jpg
# or
magick convert cover.avif cover.png
If you are scripting cover downloads for a batch of books, this slots directly into a shell pipeline. The shell command for f in *.avif; do magick convert "$f" "${f%.avif}.jpg"; done converts an entire folder in one pass.
2. Convert with a GUI tool. GIMP 2.10.34 and later reads AVIF; open the file and export as JPEG or PNG. For non-technical users, GIMP is the most accessible option. The file size grows from AVIF's compressed 80–100 KB back to JPEG's roughly 200 KB, but quality is preserved.
3. Get the JPEG from a non-Amazon source. Open Library (openlibrary.org) serves cover images as JPEG at predictable URLs derived from the book's OLID. For any book in Open Library's catalog — which is most in-print English-language books and a long tail of older titles — this is faster than converting. The URL pattern is https://covers.openlibrary.org/b/olid/OL<ID>M-L.jpg. Calibre's "Download cover" feature can be pointed at Open Library directly through its metadata-source preferences.
Calibre users should also know that Calibre's ISBN-based cover lookup currently defaults to Amazon; if you want to avoid the AVIF issue entirely, set Open Library or Google Books as the primary cover source in Preferences → Metadata → Configure plugins → Ebook metadata download. The fetched covers will be JPEG.
What about EPUBs that contain AVIF images?
This is the more interesting question. EPUB 3.3, finalized in early 2026, permits any image format whose core media type is registered. AVIF's core media type is image/avif. EPUB 3.3 does not explicitly include image/avif in its core media types list, which lists image/jpeg, image/png, image/gif, image/svg+xml, and image/webp.
In practice, AVIF inside an EPUB renders fine on the readers that matter: modern Kindle firmware (5.18+), Kobo firmware 4.40+, BOOX firmware 4.0+, Apple Books, and Google Play Books all support AVIF at the rendering layer. Older readers — any Kindle older than a 2022 Paperwhite, any Kobo Aura, any early BOOX — will display a broken-image placeholder if the EPUB's body includes an AVIF.
The practical advice for self-publishers: stick with JPEG for cover art and inline images inside EPUBs until late 2027. The format ecosystem inside reading apps is still catching up; reader-app AVIF support is uneven across model years and firmware versions. Save AVIF for your retail website and blog, where the reader is always a modern browser.
The broader pattern: format drift between web and reading apps
Amazon's AVIF migration is the latest in a string of format gaps between web infrastructure and the ebook ecosystem. The earlier examples are useful as reference points.
WebP, the format Google developed in 2010 and pushed aggressively from 2014 onward, took roughly eight years to reach full support across reading apps. Kobo added WebP support in firmware 4.30 (mid-2023) and currently issues an EPUB validation warning for it; the Kobo 4.42 firmware's EPUB checker flags WebP and AVIF as "may not render correctly on all models." Kindle devices only started accepting WebP-in-EPUB with the Kindle Scribe Colorsoft firmware refresh in 2024.
HEIF, the format Apple adopted as the iPhone default in 2017, never made it into the EPUB core media types list at all. Authors who upload HEIF photos to KDP face a silent conversion to JPEG at upload time.
AVIF is on a faster trajectory than WebP because the underlying AV1 codec is hardware-accelerated in every shipping mobile SoC from 2023 onward, and because the Alliance for Open Media includes every major reader-app vendor as a member. The format gap between "Amazon serves it on the web" and "Calibre reads it locally" is roughly 24 months wide based on the WebP precedent, and Calibre's maintainer Kovid Goyal has not committed publicly to an AVIF roadmap.
What to watch over the next six months
Three signals will indicate whether the AVIF ecosystem is converging or staying split.
Calibre AVIF support. The most likely early indicator is whether Calibre's GitHub issue tracker sees a pull request adding AVIF support to the cover-import code path. AVIF support in Qt (Calibre's underlying GUI toolkit) was added in Qt 6.5 (mid-2023), so the technical foundation is in place; it is a question of whether Kovid Goyal accepts the change or holds off on native AVIF until a more coordinated reader-app story emerges.
WordPress and Ghost. WordPress 6.5 added optional AVIF support, but the default install still rejects .avif uploads on most shared hosts. Ghost added AVIF support in Ghost 5.86 (early 2025). These two platforms together power the majority of author websites; their convergence on AVIF as a default upload type would close the most common gap.
Amazon Canada's rollout timing. The current JPEG/PNG exception on Amazon Canada is the most concrete schedule indicator. When Amazon Canada flips to AVIF, the rollout is complete and the workaround window closes. Based on the historical pattern of Amazon's CDN rollouts — a 90-day window from US to international for the previous WebP migration — expect Amazon Canada to switch by mid-December 2026.
For now: if you maintain a Calibre library of 1,000+ books and rely on Amazon-sourced covers, set Open Library as the primary metadata source. If you publish author sites in WordPress, install an AVIF-supporting plugin or upload covers as JPEG. If you self-publish EPUBs, keep cover art and inline images as JPEG until 2027. The format is coming; the tools are catching up.
Frequently Asked Questions
Why did Amazon switch Kindle book covers to AVIF?
Bandwidth and CDN cost. AVIF files are roughly 50% smaller than equivalent-quality JPEG, and Amazon serves billions of product images per day. The format is royalty-free through the Alliance for Open Media (which Amazon co-founded), supported by every shipping browser since 2023, and hardware-accelerated in current mobile SoCs. The switch is purely an infrastructure decision; readers see no visible difference.
Does Calibre support AVIF cover art yet?
No. As of Calibre 9.14.0 (August 28, 2026), AVIF is not on Calibre's supported cover-art format list. If you point Calibre's "Download cover" feature at an Amazon URL, the resulting .avif file is rejected. If you manually drop an .avif file into the Edit metadata dialog, Calibre treats it as an unknown format and leaves the cover slot empty. Convert the file to JPEG or PNG before importing, or point Calibre at Open Library for cover downloads.
Can I still get JPEG covers from Amazon?
Yes, but only from Amazon Canada (amazon.ca). As of mid-September 2026, the Canadian storefront is still serving JPEG and PNG. The .com, .co.uk, .de, .fr, .it, .es, .co.jp, and most other Amazon properties have switched to AVIF. Treat the Canadian exception as temporary; expect the US-to-international rollout to complete within 90 days based on Amazon's CDN migration history. For a permanent non-AVIF alternative, use Open Library covers or Google Books API thumbnails.
Does EPUB 3.3 support AVIF as an image format?
EPUB 3.3's core media types list explicitly enumerates image/jpeg, image/png, image/gif, image/svg+xml, and image/webp. AVIF (image/avif) is not on the list, but EPUB 3.3's conformance language permits any registered media type with proper fallbacks. In practice, modern reading apps (Kindle firmware 5.18+, Kobo 4.40+, BOOX 4.0+, Apple Books, Google Play Books) render AVIF fine. For maximum compatibility with older readers, stick with JPEG for cover art until 2027.
How do I convert an AVIF file to JPEG?
Three reliable options. On the command line, ImageMagick 7.1.0-49+ with libavif delegate: magick convert cover.avif cover.jpg. On the desktop, GIMP 2.10.34+ opens AVIF directly and exports as JPEG or PNG. In the browser, any modern browser's "Save image as" still saves AVIF as AVIF, so a converter is needed for the actual format change. For bulk conversions of hundreds of covers, ImageMagick in a shell loop is the fastest path.
Will this affect ebooks I already have in Calibre?
No. The AVIF switch only affects images Amazon serves on its website right now. Existing EPUBs in your Calibre library already have JPEG or PNG covers embedded; those are unaffected. The change matters when you try to add a new cover to a book, or when Calibre's automatic metadata fetch hits Amazon and downloads an .avif file it cannot read. Existing books, covers, and metadata are untouched.