Title: WordPress 5.8 adds WebP support Author: Adam Silverstein Published: June 7, 2021 Last modified: November 9, 2021 --- [ ](https://profiles.wordpress.org/adamsilverstein/) [Adam Silverstein](https://profiles.wordpress.org/adamsilverstein/) 8:22 pm _on_ June 7, 2021 Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/), [core-images ( 9 )](https://make.wordpress.org/core/tag/core-images/), [dev-notes ( 648 )](https://make.wordpress.org/core/tag/dev-notes/), [images ( 10 )](https://make.wordpress.org/core/tag/images/)    # WordPress 5.8 adds WebP support [WebP](https://developers.google.com/speed/webp) is a modern image format that provides improved lossless and lossy compression for images on the web. WebP images are around 30% smaller on average than their JPEG or PNG equivalents, resulting in sites that are faster and use less bandwidth. WebP is supported in all modern browsers [according to caniuse](https://caniuse.com/webp). From WordPress version 5.8 forward, you can upload and use WebP images in WordPress like you would a JPEG or PNG image today (as long as your hosting service supports WebP). Switching to the WebP format for your images will improve your site’s performance and your site visitor’s experience.  ## How WebP Helps You WebP images are significantly smaller than their JPEG equivalents, so visitors to your site will see the complete page loaded more quickly. Smaller images take less bandwidth to transmit, and your images still get all of the responsive benefits of `srcset` and lazy loading by default. Finally, WebP is supported in all major browsers, so most sites can start using them today. ## Creating WebP images Image editing tools support exporting in WebP, or you can also use command line [conversion tools](https://developers.google.com/speed/webp/docs/precompiled) or web based tools like [Squoosh](https://squoosh.app). Once you save your images as WebP, upload them to WordPress and use them like you would any other image.  ## Using WebP images WebP images work like any other image in WordPress with some small caveats.  WebP images support lossy and lossless compression, as well as an animated format and support for transparent images. In WordPress, the _lossless WebP_ format is only supported when the hosting server uses Imagick (the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher library) until LibGD [adds support](https://github.com/libgd/libgd/pull/698). In addition, animated and alpha formats are not yet supported for resized images( lossy images are created instead when you upload in these formats). WebP support in the media library requires that your web server’s image processing library (WordPress supports both Imagick and LibGD) supports the WebP format. Fortunately these libraries have supported WebP for quite a while so support is widely available. If your web server does not support WebP, you will see an error message when you try to upload a WebP image. If your audience includes a significant number of users on an unsupported browser( IE11 for example), either avoid using WebP images, or  enqueue a [browser polyfill](https://github.com/chase-moskal/webp-hero). ## Plans for the future The media component team is also exploring the option of having WordPress perform the image format conversion on uploaded images – using WebP as the default output format for sub-sized images. You can track progress and test this feature on the [trac ticket](https://core.trac.wordpress.org/ticket/52867). We are also keeping our eyes on even more modern formats like AVIF and JPEGXL that will both improve compression and further reduce resources required for compression. ## FAQ ### How can I fine tune the compression quality setting used for WebP images? Developers or plugins can use the `wp_editor_set_quality` filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks). They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to set the quality setting. The passed mime type enables setting by type, for example: ```notranslate // Use a quality setting of 75 for WebP images. function filter_webp_quality( $quality, $mime_type ) { if ( 'image/webp' === $mime_type ) { return 75; } return $quality; } add_filter( 'wp_editor_set_quality', 'filter_webp_quality', 10, 2 ); ``` ### What happens if I enable the filter to use WebP sub-sizes, but upload JPEG? Do the sub-sizes have to match the original? By default, WordPres creates the sub-sized images of the same type as the uploaded file, so uploaded WebP files to get WebP files on your site. If you want to experiment with uploading JPEG and having WordPress auto-convert these to WebP for your sub- sized images, check out this [plugin](https://github.com/adamsilverstein/wordpress-modern-images)( related [trac ticket](https://core.trac.wordpress.org/ticket/52867)). ### If I use WordPress multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also **network**, **blog**, **site**, will all my sites work with WebP images? No. Multisite stores the file types that users are allowed to upload when a site is created. We are working on improving this in [#53167](https://core.trac.wordpress.org/ticket/53167). In the meantime, to ensure all existing sites on a networknetwork (versus site, blog) allow WebP files, you can use the `site_option` filter in a network mu-pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. to add `webp` to the allowed file types for all network sites: ```notranslate // Ensure all network sites include WebP support. add_filter( 'site_option_upload_filetypes', function ( $filetypes ) { $filetypes = explode( ' ', $filetypes ); if ( ! in_array( 'webp', $filetypes, true ) ) { $filetypes[] = 'webp'; } $filetypes   = implode( ' ', $filetypes ); return $filetypes; } ); ``` [#5-8](https://make.wordpress.org/core/tag/5-8/), [#core-images](https://make.wordpress.org/core/tag/core-images/), [#dev-notes](https://make.wordpress.org/core/tag/dev-notes/), [#images](https://make.wordpress.org/core/tag/images/) ### Share this: * [ Threads ](https://make.wordpress.org/core/2021/06/07/wordpress-5-8-adds-webp-support/?share=threads) * [ Mastodon ](https://make.wordpress.org/core/2021/06/07/wordpress-5-8-adds-webp-support/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/core/2021/06/07/wordpress-5-8-adds-webp-support/?share=bluesky) * [ X ](https://make.wordpress.org/core/2021/06/07/wordpress-5-8-adds-webp-support/?share=x) * [ Facebook ](https://make.wordpress.org/core/2021/06/07/wordpress-5-8-adds-webp-support/?share=facebook) * [ LinkedIn ](https://make.wordpress.org/core/2021/06/07/wordpress-5-8-adds-webp-support/?share=linkedin) 1. ![](https://secure.gravatar.com/avatar/18f4f7ebdcd48383951a52a88f401bd6460ae74b626016010b1f0604cac90826? s=32&d=mm&r=g) 2. [Jonathan Desrosiers](https://profiles.wordpress.org/desrosj/) 11:14 pm _on_ June 7, 2021 3. Thanks for this, [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/)! 4. Could a brief clarification be added to explain the difference between ImageMagick( the image manipulation software installed on the server) and Imagick (the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher interface to interact with ImageMagick)? It’s not uncommon for the two to be misunderstood. 5. Also, it’s worth mentioning that 5.8 also adds new fields to Site Health to help determine if a site is capable of processing WebP format image files. Before WordPress 5.8, the following information was displayed: 6. * ImageMagick version number * ImageMagick version string * Imagick resource limits 7. The following fields are new in WP 5.8: 8. * Imagick version * ImageMagick supported file formats 9. When WebP is not listed as a supported file formats, the site owner will need to reach out to their hosting provider. The Imagick will come in handy as more sites upgrade to PHP 8. There are currently no publicly releases of Imagick that support PHP 8. When there is, this can be used to identify why GD is being used in favor of Imagick. These changes were added in [#53022](https://core.trac.wordpress.org/ticket/53022)/ [[50817]](https://core.trac.wordpress.org/changeset/50817). 10. * ![](https://secure.gravatar.com/avatar/82e095c8bc229017b128e53940ea534aa31f6624431bedee24c7e8756e42dd1c? s=32&d=mm&r=g) * [Adam Silverstein](https://profiles.wordpress.org/adamsilverstein/) 2:08 pm _on_ June 8, 2021 * I added a line clarifying that it is Imagick the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher library I am referring to. * Nice to see the image file support added to site health, I missed that effort! It would be good to support GD format listing there as well, especially since GD is now bundled with PHP. - ![](https://secure.gravatar.com/avatar/18f4f7ebdcd48383951a52a88f401bd6460ae74b626016010b1f0604cac90826? s=32&d=mm&r=g) - [Jonathan Desrosiers](https://profiles.wordpress.org/desrosj/) 4:13 pm _on_ June 28, 2021 - Just in case someone is looking at this in the future, a new field listing the image formats supported by GD was also added to Site Health in [[51143]](https://core.trac.wordpress.org/changeset/51143). 11. ![](https://secure.gravatar.com/avatar/cf5254e4ef941be0309816c0f93995341208786750e4c9baadbf0567a6ec2cc1? s=32&d=mm&r=g) 12. Anonymous User 8:02 am _on_ June 8, 2021 13. Awesome – it is great to see that WordPress will natively support the WebP format in the future! Thank you for that. 14. If I understood this post correctly, the approach regarding image format will be either / or. Meaning that basically we will have to decide whether we want to use JPEG or WebP as a default image format. 15. What about an additional approach: Already today, WordPress uses the picture element together with srcset to let the browser select the best picture size. Would it be possible to simply extend the srcset to also include WebP versions? This would not even require a polyfill, further enhancing browser compatibility. 16. * ![](https://secure.gravatar.com/avatar/82e095c8bc229017b128e53940ea534aa31f6624431bedee24c7e8756e42dd1c? s=32&d=mm&r=g) * [Adam Silverstein](https://profiles.wordpress.org/adamsilverstein/) 2:10 pm _on_ June 8, 2021 * Good suggestion Robert and something we plan to explore. The picture element is perfect for using newer formats like AVIF where browser support isn’t complete. * With WebP most sites can just switch because all modern browsers support the format. One advantage of this approach is we avoid having to recompress each image into both formats. If you use AVIF with the picture element, you will need AVIF and JPEG versions of each image size. - ![](https://secure.gravatar.com/avatar/cf5254e4ef941be0309816c0f93995341208786750e4c9baadbf0567a6ec2cc1? s=32&d=mm&r=g) - Anonymous User 3:11 pm _on_ June 8, 2021 - Thank you for the reply Adam. I am just trying to look ahead – as you mentioned in your article, there will be other image formats like JPEG-XL. The picture element is perfect for adopting whatever future image formats the web will support. - What would be very helpful is a filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks). They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. for the **wp_image_add_srcset_and_sizes** function, so people who generate their own WebP (or whatever future format) images can modify the output of the srcset directly, instead of having to filter the whole post content. - To go even further, something like: - ```notranslate add_theme_support( 'image_format', array( 'jxl', 'webp', 'jpeg' ) ) ``` - to indicate which image formats are supported – the order would determine the order in the picture / srcset element. - Anyway, thank you for listening. It is very encouraging that you guys listen to user feedback. * ![](https://secure.gravatar.com/avatar/82e095c8bc229017b128e53940ea534aa31f6624431bedee24c7e8756e42dd1c? s=32&d=mm&r=g) * [Adam Silverstein](https://profiles.wordpress.org/adamsilverstein/) 7:58 pm _on_ June 8, 2021 * > What would be very helpful is a filterFilter Filters are one of the > two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks). > They provide a way for functions to modify data of other functions. > They are the counterpart to Actions. Unlike Actions, filters are meant > to work in an isolated manner, and should never have side effects such > as affecting global variables and output. for the wp_image_add_srcset_and_sizes > function, so people who generate their own WebP (or whatever future > format) images can modify the output of the srcset directly, instead > of having to filter the whole post content. * looking at the code i’m not sure that is directly possible, the filter would need to be added at a higher level to be able to wrap the img tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.). * > to go even further, something like: > add_theme_support( ‘image_format’, > array( ‘jxl’, ‘webp’, ‘jpeg’ ) ) to indicate which image formats are > supported – the order would determine the order in the picture / srcset > element. * Great suggestion – I like the idea of building a more generalized APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. like this. We are discussing adding a picture element in [https://core.trac.wordpress.org/ticket/42920](https://core.trac.wordpress.org/ticket/42920), can you please add your suggestion there so we don’t lose it? * ![](https://secure.gravatar.com/avatar/79377f5a28d52191c201373f8cef961c304d81496f7211f28d1d8475785ea838? s=32&d=mm&r=g) * [dirkbeckersbe](https://profiles.wordpress.org/dirkbeckersbe/) 7:02 pm _on_ July 8, 2021 * The OG property does not support WebP. In other words, we cannot use this format for the moment … 17. ![](https://secure.gravatar.com/avatar/e48e95eba4f298f73069e3545b63f3e6ac6c20104ff14e664afa6d787625918a? s=32&d=mm&r=g) 18. [Hristo Pandjarov](https://profiles.wordpress.org/hristo-sg/) 7:24 am _on_ June 9, 2021 19. I think we need to add fallback to GD no matter it doesn’t support lossless yet and even to cwebp through exec. 20. 1. WordPress already does compress images when they are uploaded – the standard extensions are set to 85 (correct me if I am wrong but that’s not really the importnat part here). So, loading this bloat just for the lossless option which we don’t use so far is kinda pointless. 21. 2. Imagick is HUGE memory consumer and loading it by default will signifficantly increase the load caused by WordPress. Especially on hosts that run threads lets’s say mod_php 22. 3. The official binaries can be used through exec ([https://developers.google.com/speed/webp/docs/cwebp](https://developers.google.com/speed/webp/docs/cwebp)) I know it is used only in the FTPFTP FTP is an acronym for File Transfer Protocol which is a way of moving computer files from one computer to another via the Internet. You can use software, known as a FTP client, to upload files to a server for a WordPress website. [https://codex.wordpress.org/FTP_Clients](https://codex.wordpress.org/FTP_Clients) class and it’s not a super great solution but it’s worth doing it. 23. When introducing such changes it is really important to consider the impact they have on hosting companies and users around the world and their memory/cpu consumption. There is a reason we don’t load imagick by default as well as many others as far as I know. If it is already there – ok, but let’s at least work on some fallbacks here! 24. * ![](https://secure.gravatar.com/avatar/e48e95eba4f298f73069e3545b63f3e6ac6c20104ff14e664afa6d787625918a? s=32&d=mm&r=g) * [Hristo Pandjarov](https://profiles.wordpress.org/hristo-sg/) 7:26 am _on_ June 9, 2021 * To add, it’s about defaults, since classic formats aren’t lossless when resized, then maybe webp should not be too. I.e setting it to lossy 85 by default would be better than lossless. - ![](https://secure.gravatar.com/avatar/ae4a4e54f58de7f040c1caef738bb56f5ccaf16b0eed9b2304df92826609d3ca? s=32&d=mm&r=g) - [Mike Schroder](https://profiles.wordpress.org/kirasong/) 7:42 am _on_ June 9, 2021 - Ah! I forgot to answer this one in my other comment, sorry! - It only saves lossless if the file being loaded is lossless: [https://github.com/WordPress/wordpress-develop/blob/630399eb20f25285563415151dc4b80edf7e5029/src/wp-includes/class-wp-image-editor-imagick.php#L208](https://github.com/WordPress/wordpress-develop/blob/630399eb20f25285563415151dc4b80edf7e5029/src/wp-includes/class-wp-image-editor-imagick.php#L208) - And only this on Imagick not by choice, but because it’s only supported in Imagick. * ![](https://secure.gravatar.com/avatar/e48e95eba4f298f73069e3545b63f3e6ac6c20104ff14e664afa6d787625918a? s=32&d=mm&r=g) * [Hristo Pandjarov](https://profiles.wordpress.org/hristo-sg/) 7:27 am _on_ June 9, 2021 * And some data to add regarding the memory consumption: * ```notranslate ps_mem -p 40610 Private + Shared = RAM used Program 4.3 MiB + 5.8 MiB = 10.0 MiB httpd --------------------------------- 10.0 MiB ================================= ``` * ```notranslate ps_mem -p 40495 Private + Shared = RAM used Program 20.4 MiB + 7.1 MiB = 27.5 MiB httpd --------------------------------- 27.5 MiB ================================= ``` * ![](https://secure.gravatar.com/avatar/ae4a4e54f58de7f040c1caef738bb56f5ccaf16b0eed9b2304df92826609d3ca? s=32&d=mm&r=g) * [Mike Schroder](https://profiles.wordpress.org/kirasong/) 7:35 am _on_ June 9, 2021 * > the lossless WebP format is only supported when the hosting server uses Imagick( > the PHPPHP The web scripting language in which WordPress is primarily architected. > WordPress requires PHP 7.4 or higher library) * A couple of things here. * In my experience with benchmarking and profiling, Imagick and Imagemagick are faster, and use less memory than GD usually does with the same loads. * I’d be interested to know more specifics on what you’ve learned here! * Second, I think there is some confusion here. So, the important word here is *lossless* is only supported with Imagick. This is not a decision that WordPress is making, but just the nature of the tools available at the moment. * WordPress does prefer Imagick when making image transformations for various reasons, but 5.8, like earlier versions of WordPress, will automatically pick whichever backend (Image Editor in WP parlance) supports that image format. * So: - If WebP is supported by Imagick on the system, Imagick will be used. - If It’s not, and GD supports WebP, GD will be used. - If only GD supports WebP, then GD will be used. - If neither supports the format uploaded, then there is an error message. * Hopefully this helps! 25. ![](https://secure.gravatar.com/avatar/cf5254e4ef941be0309816c0f93995341208786750e4c9baadbf0567a6ec2cc1? s=32&d=mm&r=g) 26. Anonymous User 9:46 am _on_ June 9, 2021 27. > > What would be very helpful is a filterFilter Filters are one of the two types > > of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks). > > They provide a way for functions to modify data of other functions. They are > > the counterpart to Actions. Unlike Actions, filters are meant to work in an > > isolated manner, and should never have side effects such as affecting global > > variables and output. for the wp_image_add_srcset_and_sizes function, so people > > who generate their own WebP (or whatever future format) images can modify > > the output of the srcset directly, instead of having to filter the whole post > > content. > looking at the code i’m not sure that is directly possible, the filter would > need to be added at a higher level to be able to wrap the img tagtag A directory > in Subversion. WordPress uses tags to store a single snapshot of a version ( > 3.6, 3.6.1, etc.), the common convention of tags in version control systems.( > Not to be confused with post tags.). 28. Hmmm… in line 1713 it looks like the complete tag with the added srcset is returned. I would be happy to modify the output and wrap it in a element… am I missing something here? 29. > Great suggestion – I like the idea of building a more generalized APIAPI An > API or Application Programming Interface is a software intermediary that allows > programs to interact with each other and share data in limited, clearly defined > ways. like this. We are discussing adding a picture element in [https://core.trac.wordpress.org/ticket/42920](https://core.trac.wordpress.org/ticket/42920), > can you please add your suggestion there so we don’t lose it? 30. [Done](https://core.trac.wordpress.org/ticket/42920#comment:9). 31. * ![](https://secure.gravatar.com/avatar/cf5254e4ef941be0309816c0f93995341208786750e4c9baadbf0567a6ec2cc1? s=32&d=mm&r=g) * Anonymous User 9:49 am _on_ June 9, 2021 * Sorry, the preview didn’t work for me – this should read: * In line 1713 it looks like the complete tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) with the added srcset is returned. I would be happy to modify the output and wrap it in a element… am I missing something here? - ![](https://secure.gravatar.com/avatar/cf5254e4ef941be0309816c0f93995341208786750e4c9baadbf0567a6ec2cc1? s=32&d=mm&r=g) - Anonymous User 9:51 am _on_ June 9, 2021 - Final attempt: - complete **img** tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) with the added srcset is returned. I would be happy to modify the output and wrap it in a **picture** element * ![](https://secure.gravatar.com/avatar/82e095c8bc229017b128e53940ea534aa31f6624431bedee24c7e8756e42dd1c? s=32&d=mm&r=g) * [Adam Silverstein](https://profiles.wordpress.org/adamsilverstein/) 9:12 pm _on_ June 9, 2021 * Right, so if you look at where the `wp_image_add_srcset_and_sizes` function is called in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., it is part of a chain of transformations that are applied to **img** tags, additional transformations happen after this that might fail if the filtered value was different. * To clarify, I agree a filtered approach could work, just that we would want to filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks). They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. the **img** tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version( 3.6, 3.6.1, etc.), the common convention of tags in version control systems.( Not to be confused with post tags.) at the last possible moment which would be later than in “`wp_image_add_srcset_and_sizes`“. - ![](https://secure.gravatar.com/avatar/cf5254e4ef941be0309816c0f93995341208786750e4c9baadbf0567a6ec2cc1? s=32&d=mm&r=g) - Anonymous User 7:25 am _on_ June 10, 2021 - Thank you for the clarification, that makes sense. 32. ![](https://secure.gravatar.com/avatar/9149875a8cf2875474223005576f7c412e7b4d07df82160adc687a8252227a5d? s=32&d=mm&r=g) 33. [Hareesh](https://profiles.wordpress.org/hareesh-pillai/) 6:28 am _on_ June 12, 2021 34. This is a nice addition to WordPress. Look forward to using it in my projects. 35. ![](https://secure.gravatar.com/avatar/6bc4cf658fe07c0292e1d3bb16d7ac7df84e5c8b875eb916bc17ca83dfb040f6? s=32&d=mm&r=g) 36. [Jani Uusitalo](https://profiles.wordpress.org/jani-uusitalo/) 11:26 am _on_ June 15, 2021 37. The function given to filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks). They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. upload_filetypes on multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog( wp_posts becomes wp_0_posts). See also **network**, **blog**, **site** returns the exploded array if the option already contains webp. Shouldn’t it be imploded back into a string before returning (i.e. unconditionally, outside the if condition)? 38. ![](https://secure.gravatar.com/avatar/f01ed007772a0e3d7d5c5867d393f4d62aff74c5208f8ddd1b428eca50cefc99? s=32&d=mm&r=g) 39. [mhamoser](https://profiles.wordpress.org/mhamoser/) 12:34 pm _on_ July 9, 2021 40. I’m trying WordPress 5.8 rc2 and I have webp created from jpg files. All the exif data are the same in jpg and webp, but after regular upload all the metadata is gone from the webp, while uploading jpg is working with metadata (as it did before). I am on a shared host with only cli imagemagick (no php extension). Might gd cause the stripping of the metadata? What can I do to preserve the metadata with WordPress native webp support? 41. ![](https://secure.gravatar.com/avatar/b28bc9e76bed4e88be5187691970c1a5c3bd6fa1d5b10e3fa78d2cf88b5069c1? s=32&d=mm&r=g) 42. [mmxxi](https://profiles.wordpress.org/mmxxi/) 8:11 am _on_ July 13, 2021 43. Hi, there seems to be an issue with the compression setting being ignored described in this topic here: [https://wordpress.org/support/topic/webp-very-large-filesize-5-8-rc2/](https://wordpress.org/support/topic/webp-very-large-filesize-5-8-rc2/) 44. ![](https://secure.gravatar.com/avatar/5783a2d9b93f04f6d0a1ddabddcfd71f15136d7eaea7a87f9962d3f93f780224? s=32&d=mm&r=g) 45. [Ian Dunn](https://profiles.wordpress.org/iandunn/) 2:58 pm _on_ August 13, 2021 46. To enable uploads in Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also **network**, **blog**, **site** without code, you can go to `https://example.org/wp-admin/network/settings.php`, and add `webp` there. 47. ![](https://secure.gravatar.com/avatar/8629e252ff9b8c3bbb8cbac077d04b52d6e134db61ca01bdeaaeb2e90add87d0? s=32&d=mm&r=g) 48. [benmorss](https://profiles.wordpress.org/benmorss/) 5:48 pm _on_ August 17, 2021 49. Note that PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8.1, out in the Fall, [will now support lossless webp](https://github.com/php/php-src/pull/7348)! 50. * ![](https://secure.gravatar.com/avatar/82e095c8bc229017b128e53940ea534aa31f6624431bedee24c7e8756e42dd1c? s=32&d=mm&r=g) * [Adam Silverstein](https://profiles.wordpress.org/adamsilverstein/) 4:51 am _on_ August 18, 2021 * Excellent, we’ll make sure to add support for that in WordPress! Comments are closed. # Post navigation [← Editor Chat Agenda: 10 June 2021](https://make.wordpress.org/core/2021/06/07/editor-chat-agenda-9-june-2021/) [Upgrade/Install component meeting agenda for June 8th, 2021 →](https://make.wordpress.org/core/2021/06/08/upgrade-install-component-meeting-agenda-for-june-1st-2021-2/)