fix(media): import, upload, and serve AVIF images - #467
Merged
Conversation
AVIF was known by extension but excluded from the upload policy, then misclassified by the broad MP4 ftyp signature and served as a generic download.
DavidBabinec
marked this pull request as ready for review
August 31, 2026 21:09
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #408
The bug
AVIF files were filtered out of static imports, misidentified as MP4 during upload sniffing, and served as generic downloads. A reported Webflow import silently lost 353 images.
The fix
Accept AVIF across the import and upload policies, detect its
ftyp/avifbrand before the broader MP4 signature, generate the existing responsive image ladder, and serve it asimage/avif. Regression coverage pins each boundary and the media/import docs now name the supported format.Verification