Add mime-type for Webp

[markoheijnen]

Would be great that at least WP_Image_Editor (if supported) could be used to transform images to the .webp format. Tickets #24718 and #27789 focus on upload which is something which could be done later.

[wonderboymusic]

​http://caniuse.com/webp

[blobfolio]

PHP support for WebP is starting to catch up. I'd like to investigate whether or not it is feasible to expand this enhancement to include thumbnail generation support as well.

I'll dive deeper in the next week or so and update the patch accordingly, but in the meantime, here are a few references:

GD and EXIF support:

• ​https://php.net/manual/en/function.imagecreatefromwebp.php (PHP 5.5)
• ​https://php.net/manual/en/function.imagewebp.php (PHP 5.5)
• ​https://secure.php.net/manual/en/function.exif-imagetype.php (PHP 7.1)

The output from gd_info() should include ['WebP Support']=>true under environments that support WebP.

Imagick can be compiled with WebP support (e.g. with libwebp-dev, etc.). This does not seem to be very common yet, but we could conditionally check the response of Imagick::queryFormats('WEBP'); a non-empty array() being Yay!, an empty one being Boo!

• ​http://www.imagemagick.org/script/formats.php
• ​https://www.imagemagick.org/script/webp.php

[blobfolio]

Patch with upload_mimes and image editor integration.

[blobfolio]

Files for unit testing.

[blobfolio]

The 35725.diff patch adds full WebP support to WordPress:

• Whitelists webp files for upload;
• Adds webp to the list of image formats for admin display, thumbnail generation, etc.;
• Provides numerous workarounds for environments where WebP support exists in a partial state;
• Supports VP8, VP8L, and VP8X container formats;
• GD handling (PHP5.6+ for VP8, PHP7.0+ for the rest);
• ImageMagick handling (works as long as the system's binary was compiled with WebP support);

This patch introduces one new function:

/**
 * Wrapper for getimagesize()
 *
 * The native PHP function might not support newer formats.
 *
 * @since 5.0
 *
 * @see {https://core.trac.wordpress.org/ticket/35725}
 *
 * @param string $file Full path to the file.
 * @param array $info Additional metadata to pull.
 * @return array|false An array containing width, height, type constant, attributes, and media type.
 */
function wp_get_image_size( $file, &$info = array() ) { ... }

All calls to the native getimagesize() function have been redirected to this wrapper to ensure that WebP dimensions are properly reported. This also fixes the inconsistent use of error suppression that existed previously.

This wrapper can later be expanded to account for other new formats, such as #42775.

A few other things to note:

• Hosts that do not support WebP through GD or ImageMagick will still allow files to be uploaded, they just won't get intermediate sizes.
• There was once a bug in GD that confused ARGB with RGBA, causing colors to shift. This has been fixed upstream, but some unsupported distributions (like Debian Squeeze) might still be using it.
• ImageMagick on Arch Linux is currently causing a segfault when dumping a WebP via the getImageBlob() method. As a workaround, stream previews (when e.g. editing an image) output png instead. This doesn't affect the saved results, so seems safe to keep.

One final note:

WebP browser support (​https://caniuse.com/#search=webp) is not universal.

This patch restricts its focus to backend handling, but there is opportunity for a future frontend-focused patch to provide jpg/png fallbacks. The use of the HTML5 <picture> element seems like the best approach for such work. As it happens, @desrosj is currently working on general <picture> support for WP, so if/when that lands, a frontend WebP enhancement should be easy. :)

[blobfolio]

Just a refresh :)

[micasuh]

With Firefox 65's WebP support and Edge adopting Chromium and Blink, the end of 2019 could be close to 80% WebP support unless Webkit surprises us. Browsers that don't support WebP will be outliers.

@blobfolio's patches (which I assume can easily be updated again) and @desrosj's work on <picture> would give WP devs an excellent avenue to use WebP in production today and help reduce load times in non-trivial ways.

I think 2019 is the right time for this to move to core.

[desrosj]

Looks like 35725.2.diff​ is no longer applying cleanly to trunk.

[desrosj]

This ticket was discussed briefly in the weekly media office hours this morning.

Because Safari ​still does not support WebP, this seems like plugin territory until there is a way to specify multiple sources for an image in core.

[pmsanz]

Replying to desrosj:

This ticket was discussed briefly in the weekly media office hours this morning.

Because Safari ​still does not support WebP, this seems like plugin territory until there is a way to specify multiple sources for an image in core.

I'm sorry, but 13 browsers does support it, and only 4 does not (Apple is always late). Anyway, there is a solution for displaying WebP in any browser with a piece of Js: ​https://webpjs.appspot.com/

It would be interesting to offer a config option in WordPress to convert uploaded files to .jpg or .webp, so user can decide. In my case, media is 80% of the site, so .webp would be great to trim disk storage.

[themefour]

After more than 8 months, this format is still not supported! I don't know, is this a difficult task? Or politics behind the scenes!

​https://wordpress.org/support/topic/add-support-webp-format-imge/

[spacedmonkey]

As of safari 14.0, safari on iOS, iPadOS, and MacOS will support WEBP natively. See the ​dev notes of first beta.

These new versions of the OS will not ship until September, but we can start working on patch that could land as soon as WordPress 5.6.

[spacedmonkey]

Related: #35726 #24718