WordPress Ideas » Topic: Native WebP https://wordpress.org/ideas/topic/native-webp WordPress Ideas » Topic: Native WebP en-US Mon, 12 Jun 2017 01:07:24 +0000 http://bbpress.org/?v=1.1 premier69 on "Native WebP" https://wordpress.org/ideas/topic/native-webp/page/2#post-31401 Sat, 04 Feb 2017 06:47:53 +0000 premier69 31401@https://wordpress.org/ideas/ I as web store owner would love webp for my Woocommerce shop.

]]> ramonjosegn on "Native WebP" https://wordpress.org/ideas/topic/native-webp#post-30808 Sat, 01 Oct 2016 13:02:36 +0000 ramonjosegn 30808@https://wordpress.org/ideas/ I agree, in fact Photon already used or not?

]]> Saumya Majumder on "Native WebP" https://wordpress.org/ideas/topic/native-webp#post-30659 Wed, 17 Aug 2016 21:45:40 +0000 Saumya Majumder 30659@https://wordpress.org/ideas/ @wordpress dev team, please make it happen please... wp-webp has been dead for years now. It's time to put it inside native wp.

]]> tosunkaya on "Native WebP" https://wordpress.org/ideas/topic/native-webp#post-30588 Tue, 26 Jul 2016 13:29:26 +0000 tosunkaya 30588@https://wordpress.org/ideas/ we want webp support.

]]> Saumya Majumder on "Native WebP" https://wordpress.org/ideas/topic/native-webp#post-28919 Tue, 29 Sep 2015 11:04:31 +0000 Saumya Majumder 28919@https://wordpress.org/ideas/ Yah! This would be nice to see native WebP support in WordPress. But WP devs barely take any few feature request and add it immediately so I guess though it's a nice thing to have, it's not gonna happen. And I'm saying this on a feature request which has been posted 1 year before.
Even after all these year I still dont see any good webp solution for wordpress.

]]> ConcertPass on "Native WebP" https://wordpress.org/ideas/topic/native-webp#post-26960 Fri, 01 Aug 2014 15:16:06 +0000 ConcertPass 26960@https://wordpress.org/ideas/ I agree with tenoch89; the WebP native support into wordpress would be a really useful feature.
However I installed the plugin on wordpress 3.9.1 (mac localhost) and it works fine.

]]> Ipstenu (Mika Epstein) on "Native WebP" https://wordpress.org/ideas/topic/native-webp#post-26497 Wed, 23 Apr 2014 22:34:37 +0000 Ipstenu (Mika Epstein) 26497@https://wordpress.org/ideas/ Why Jetpack? If you wanted to whip up a plugin that did this, with more recent webP bits added, go for it :) Jetpack is mostly about bringing features from wordpress.com to wordpress.org

(And the answer would probably be stability over speed)

]]> J.N. Squire on "Native WebP" https://wordpress.org/ideas/topic/native-webp#post-26496 Wed, 23 Apr 2014 21:48:39 +0000 J.N. Squire 26496@https://wordpress.org/ideas/ Actually, the wp-webp plugin just adds WebPJS (http://webpjs.appspot.com/) to the site. This project has not been updated since December 2012 (see http://webpjs.appspot.com/Changelog.txt), so the wp-webp plugin doesn't have the most recent specifications.
Since last December,the libwebp version is 0.4.0 (see the download repository on the website) and now supports transparency and much faster decoding (I'm talking from seconds to milliseconds), and is of course less buggy (and it ends the choice to make between WebP v0.2.1 and v0.3.0 that was problematic before).

So now that even Google considers WebP stable enough to use it for Youtube previews, should WordPress supports it natively? I'd say it depends of what it the priority.
_If the priority is to make a much faster WordPress, then the current specs are just fine since WebP images. For example, I converted a 820 KB transparent PNG comic image already compressed (with TinyPNG, if you want to compare with my results) I posted on WordPress to a 222 KB WebP image. While WebP is currently only supported by Chrome/Chromium, Opera and Android Browser, that would be enough for significantly saving bandwidth and speeding webpages loading and display, which is very interesting for websites managers willing to save as much costs as possible (maybe even for Wordpress.com for the same images of the website side only if some converter is developed).
_But if the policy is to support natively a much stabler version, then I think we need to wait before deciding if it's worth to implement WebP native support on WordPress. Or to bring it as an optional and experimental feature in Jetpack so developers could decide.

There, my 2 cents about this. :)

]]> tenoch89 on "Native WebP" https://wordpress.org/ideas/topic/native-webp#post-25747 Sat, 07 Dec 2013 09:04:24 +0000 tenoch89 25747@https://wordpress.org/ideas/ It is in terms of constant Wordpress updates, meaning the developer would need to consistently update in order to be compatible with updates from Wordpress. Hence why I think it should be core, also the technology has been around a while and by that I mean a few year. If it's core, then it would obviously get updated as new Wordpress releases come, no?

For example, the plugin works fine on my 3.6.1 localhost based WP install, however, if I try it on the same localhost on a 3.7.1 install, the posts do not show up, which will most likely be sorted with the next plugin update, hence, why can't this format be core?

]]> Ipstenu (Mika Epstein) on "Native WebP" https://wordpress.org/ideas/topic/native-webp#post-25745 Fri, 06 Dec 2013 16:53:04 +0000 Ipstenu (Mika Epstein) 25745@https://wordpress.org/ideas/ Updated 6 weeks ago is 'a while' for you?

http://wordpress.org/plugins/wp-webp/

]]>