Ready to get started?Download WordPress


Native WebP

  1. tenoch89


    Hey, it would be great if WordPress natively supported WebP without plugins, is this possible, as .htaccess wise i t's really only a few lines and servers can support it, so I don't think that would be an issue if users wanted to implement it. There is currently a plugin for WebP for WordPress, but it hasn't been updated in a while and as this is an emerging technology format that's been around a while, I think it's time it gets added to WordPress natively.

    Posted: 1 year ago #
  2. Ipstenu (Mika Epstein)

    Updated 6 weeks ago is 'a while' for you?


    Posted: 1 year ago #
  3. tenoch89


    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?

    Posted: 1 year ago #
  4. J.N. Squire

    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. :)

    Posted: 10 months ago #
  5. Ipstenu (Mika Epstein)

    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)

    Posted: 10 months ago #
  6. ConcertPass

    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.

    Posted: 7 months ago #

RSS feed for this topic


You must log in to post.

  • Rating

    1 Vote
  • Status

    This is plugin territory