Make WordPress Core

#60902 closed defect (bug) (reported-upstream)

WordPress don't create additional sizes for AVIF image files uploaded

Reported by: fernandot's profile fernandot Owned by: adamsilverstein's profile adamsilverstein
Milestone: Priority: normal
Severity: normal Version: 6.5
Component: Media Keywords: needs-patch avif
Focuses: administration Cc:

Description

If you have configured the WordPress media settings to create additional sizes for uploaded images, that setup works fine with JPG and PNG, as well as with WebP files, but not with AVIF files. The only file saved is the original uploaded.

Change History (14)

#1 @adamsilverstein
12 months ago

Hi @fernandot - thanks for the bug report.

Can you please check your server support for AVIF images? Look under Tools->Site Health then the Info tab->Media Handling. check to see if your image handling library shows "AVIF" as a supported image? Without this server support, WordPress can't create the subsized images you are expecting. If you don't have AVIF support, ask your host about how you can get it.

One possible improvement here would be to disallow uploads entirely when AVIF isn't supported on the server (which I thought might already be the case?). Where are you uploading the image? In the media library or directly into the editor?

This ticket was mentioned in Slack in #core-media by antpb. View the logs.


12 months ago

#3 @joedolson
12 months ago

  • Keywords reporter-feedback added

#4 @fernandot
12 months ago

Hi @adamsilverstein

You're right

The server (SiteGround) doesn't show support for AVIF, I'll ask them to add it because is a hosting that a lot of people use.

I uploaded the image via the editor media uploader.

Yes, a good point would be to inform the user that the server doesn't support AVIF files and prevent the upload, for a streamlined user experience.

This ticket was mentioned in Slack in #core-media by azaozz. View the logs.


12 months ago

#6 @fernandot
12 months ago

Hi there again :)

I've asked the hosting and the response is that the GD extension only offers support for AVIF images format from PHP 8.1.

So, this could be anything that can affect any other WP user without PHP 8.1, isn't it?

#7 @adamsilverstein
12 months ago

  • Keywords reporter-feedback removed

Yes, a good point would be to inform the user that the server doesn't support AVIF files and prevent the upload, for a streamlined user experience.

I agree we could better inform the user here, and maybe block the upload as long as that can be bypassed as some users are expecting to be able to upload and use (the full sized) AVIF images even if the server doesn't support AVIF

I've asked the hosting and the response is that the GD extension only offers support for AVIF images format from PHP 8.1.

That is generally true for PHP's built in GD support. WordPress also supports the Imagick library for image processing which lets you enable AVIF support with lower PHP versions - although if possible I would consider upgrading to PHP 8.1 or higher anyway! Good to ask your host for AVIF support, until then you should probably stick to WebP or JPEG for images.

#8 @fernandot
12 months ago

The ticket isn't for me, I can upgrade to PHP 8.1 and beyond but for general purposes I think this issue should be caught in attention in order to notice WP users or anything else because it isn't documented yet that the WordPress AVIF support depends on the server Media support (GD or Imagick) and offer to users a way to inform their hosting company about it, as we use to do with other issues :)

#9 follow-up: @adamsilverstein
12 months ago

  • Keywords avif added

I agree we should help users understand what could go wrong here. In fact, I thought we already prevented users from uploading images when the server doesn't support their mime type. A user reported just that recently, I think because they are trying to upload AVIF images on a server that lacks support: https://core.trac.wordpress.org/ticket/60932

@fernandot quick question: are you testing the uploading using the media library, or are you uploading the images in the block editor?

This ticket was mentioned in Slack in #core-performance by mukeshpanchal27. View the logs.


11 months ago

#11 @mukesh27
11 months ago

  • Focuses performance removed

Hi there!

Thanks for the ticket. As discussed in today's performance scrub this ticket is not related to Performance so i'm going to remove it. Thanks!

#12 in reply to: ↑ 9 @fernandot
11 months ago

Inside the block editor.

Replying to adamsilverstein:

I agree we should help users understand what could go wrong here. In fact, I thought we already prevented users from uploading images when the server doesn't support their mime type. A user reported just that recently, I think because they are trying to upload AVIF images on a server that lacks support: https://core.trac.wordpress.org/ticket/60932

@fernandot quick question: are you testing the uploading using the media library, or are you uploading the images in the block editor?

#13 @adamsilverstein
11 months ago

  • Milestone changed from Awaiting Review to 6.6
  • Owner set to adamsilverstein
  • Status changed from new to assigned

#14 @adamsilverstein
10 months ago

  • Milestone 6.6 deleted
  • Resolution set to reported-upstream
  • Status changed from assigned to closed

Inside the block editor.

Thanks for clarifying @fernandot - I am going to close this ticket in favor of this Gutenberg PR where we aim to prevent uploading there if your server doesn't support AVIF.

Note: See TracTickets for help on using tickets.