{"id":26278,"date":"2022-04-08T10:00:16","date_gmt":"2022-04-08T07:00:16","guid":{"rendered":"https:\/\/vipestudio.com\/?p=26278"},"modified":"2022-04-04T08:48:20","modified_gmt":"2022-04-04T05:48:20","slug":"viptor-says-will-webp-be-enabled-by-default-in-wordpress-6-0","status":"publish","type":"post","link":"https:\/\/vipestudio.com\/en\/viptor-says-will-webp-be-enabled-by-default-in-wordpress-6-0\/","title":{"rendered":"Viptor Says: Will WebP Be Enabled by Default in WordPress 6.0?"},"content":{"rendered":"

Hi, everyone! Viptor here! I recently found out that the WordPress Performance Team has proposed a feature<\/a> that would enable WebP pictures by default. This will bring core support for the modern image format<\/strong> to the next level.<\/p>\n

Everyone at our WordPress agency for enterprise<\/a> is interested in this proposal, so I decided to tell you more about it in today\u2019s article. Let\u2019s go and see if the WebP format will be enabled by default in WordPress 6.0!<\/p>\n

\"\"<\/p>\n

WordPress WebP Support<\/h2>\n

I remind you that WordPress 5.8<\/a> added WebP<\/a> functionality in July 2021. This novelty allowed users to upload and use WebP pictures in their content.<\/p>\n

Now, with the new proposal by the Performance Team, the WebP image format has a chance of becoming a default option<\/strong> in the upcoming WordPress 6.0 release. If the proposal is approved, WebP images will be generated by default for new JPEG uploads.<\/p>\n

Additionally, our enterprise WordPress agency has come to understand that if the proposal gets accepted, WebP images will be used by default for website content<\/a>.<\/p>\n

In the feature proposal, WordPress core developer Adam Silverstein stated that WebP was designed as a new picture format that delivers improved compression on the web.<\/strong> You probably know that images<\/a> are among the largest resources utilized by websites. This is exactly where the WebP format can come in handy.<\/p>\n

Our WordPress Agency for Development believes that adopting the WebP format can result in lighter and faster<\/a> websites. After all, WebP photos generated by WordPress are nearly always smaller than JPEG images, with an average file size decrease of 30%<\/a>. The best part, however, is that the visual quality of the images isn\u2019t compromised in any way.<\/strong><\/p>\n

\"\"<\/p>\n

Will WebP Change the Image Upload Workflow in WordPress?<\/h2>\n

If the proposal is approved and the WebP format is enabled by default, WordPress users<\/a> would not experience any changes to their normal picture upload routine. As our WordPress development agency understood, the CMS would automatically convert JPEG files to WebP<\/strong>, and the new format will be used on the website.<\/p>\n

By the way, I was curious to find out that according to Can I Use<\/a>, 94.25% of web browsers support the WebP picture format. As it turns out, WebP is not supported by a very tiny number of browsers, including Internet Explorer 11 and Safari on MacOS < v11 Big Sur.<\/p>\n

\"\"<\/p>\n

Default WebP Images in WordPress: The Debate<\/h2>\n

The suggested feature by the Performance Team would include two filters for controlling or disabling WebP uploads, as well as a user-friendly plugin.<\/strong> However, despite the huge performance advantages, the feature request is not without opposition.<\/p>\n

Our WordPress development company learned that several forum participants raised concerns regarding email clients and social media<\/a> sites that do not support WebP.<\/p>\n

Kaspars Dambis remarked that he doesn\u2019t believe WebP is ready to be a \u2018hardcoded default\u2019 in the post_content<\/em> for all of the reasons outlined by other contributors in prior comments.<\/p>\n

Dambis noted that many web clients do not support WebP formats, including those who use eBook readers, RSS<\/a> clients, desktop picture viewers, open graph parsers, email<\/a> clients, smart TVs, and so on. Dambis stressed that these are all important online users.<\/p>\n

Silverstein responded to these concerns by clarifying that WordPress will continue to generate JPEG image sub sizes<\/strong> in the same manner as before.<\/p>\n

Our WordPress agency for enterprise appreciates this clarification. All WordPress users can rest easy now, knowing that JPEG sub sizes are still generated and saved in the same meta fields, as Silverstein explained. This practically means that users of RSS<\/a> feeds, REST media endpoints, and OG tags will continue to use the JPEG sub-sized versions.<\/p>\n

\"\"<\/p>\n

What Does the Future Hold for Default WebP Images in WordPress?<\/h2>\n

And so, contributors from the Performance Team are pushing for WordPress 6.0 to enable WebP by default. They are currently seeking authorization from the image component\u2019s maintainers. The experts from our enterprise WordPress agency will be sure to keep a close eye on the progression of the proposal.<\/p>\n

Anyone may try out the feature by installing the Performance Lab plugin<\/a> I recently covered in one of my previous posts<\/a>. If you want to test the proposed feature, you\u2019ll have to turn on the \u201cWebP Uploads\u201d module within the plugin.<\/strong> Our WordPress Agency for Development will make sure to test it out.<\/p>\n

One last thing \u2013 testers are encouraged to leave feedback on the Trac ticket<\/a> or Pull Request<\/a>, so don\u2019t forget to do that \u2013 it will help the Performance Team resolve any issues that may occur.<\/p>\n

That was it for this week\u2019s news, folks! I\u2019ll see you very soon. Until then, don\u2019t forget to stop by Vipe Studio\u2019s blog<\/strong> if you want to find high-quality resources about everything WordPress-related.<\/p>\n

And if you\u2019re on the lookout for a first-class WordPress website development<\/a> service, don\u2019t hesitate to contact us! We offer solutions for businesses of all shapes and sizes, including Enterprise<\/a>. Send us your inquiry<\/strong>, we can\u2019t wait to learn everything about your project!<\/p>\n","protected":false},"excerpt":{"rendered":"

Hi, everyone! Viptor here! I recently found out that the […]<\/p>\n","protected":false},"author":1,"featured_media":26279,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[113],"tags":[2034,618,2032,2035,2029,2030,2031,2033,1971],"class_list":["post-26278","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-website-wordpress-development","tag-feature-proposal","tag-image-compression","tag-image-format","tag-upcoming-release","tag-webp","tag-webp-images","tag-webp-pictures","tag-wordpress-6-0","tag-wordpress-performance-team"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/posts\/26278","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/comments?post=26278"}],"version-history":[{"count":6,"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/posts\/26278\/revisions"}],"predecessor-version":[{"id":26294,"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/posts\/26278\/revisions\/26294"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/media\/26279"}],"wp:attachment":[{"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/media?parent=26278"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/categories?post=26278"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/tags?post=26278"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}