9 ms·
Facebook tries Google's WebP image format; users squawk
- dz0ny 14y agoChanging user-agent as article suggest is a little too extreme. Looks like no one knows about download link under options, that link servers jpg.
- pyre 14y agoTo be fair, "options" isn't where I would expect a download link to be.
- chrisfarms 14y agoObligatory: http://xkcd.com/1172/ http://xkcd.com/1172/
- ihuman 14y agoWhen I saw that link, I was expecting to open this one: http://xkcd.com/927/ http://xkcd.com/927/
- omarrr 14y agoJust have Facebook add a "Download as JPEG" button and let us all go back to more important things.
- grecy 14y agoBut then Facebook have to store two formats, something I'm sure they don't want to do.
- apendleton 14y agoThey're doing that anyway because they serve non-webp images to users with non-webp-supporting browsers. Anyhow, this is the image that's for display, which is resized/compressed; they store and allow you to download the original no matter what. I'm skeptical of this solution for other reasons, though (like that it assumes users know what JPG means).
- grecy 14y ago> They're doing that anyway because they serve non-webp images to users with non-webp-supporting browsers. For now, yes, but I doubt that's their long-term plan here.
- apalmer 14y agoUsers who don't know what JPG means are not going to be attempting to edit the images in photoshop. Although perhaps they are saving the files to their local windows machine.
- dvhh 14y agoBut then the jpg file will be optionally downloaded, thus reducing the bandwith usage (desired effect), and accelerating the page-load (another desired effect).
- Too 14y agoOr just have the browser add a "Save Image as JPEG" button that does automatic conversion. I don't know if jpg can reuse the information from webp or if you have to do full uncompression and then recompression but if you care about that you probably wouldn't have this problem in the first place.
- NelsonMinar 14y agoThe primary complaint here is users don't know what to do with a .webp when they download their photos. And support does seem limited; it looks like Photoshop needs a plugin, for instance. But Facebook could solve that specific problem by having a real "Download as JPG" button while still using WebP for inline images.
- wmf 14y agoExcept Facebook officially does not want people to export anything from Facebook. The ability for browsers to save images was a "bug".
- Total_Meltdown 14y agoThey seem OK with downloading to me... http://i.imgur.com/wVZCFLm.png http://i.imgur.com/wVZCFLm.png Edit: And if it was a bug, they've taken their sweet time fixing it. I can still right click -> Save Image As.
- jrockway 14y agoIndeed. If Facebook is trying to lock users in, a non-patent-encumbered format with a free BSD-licensed reference implementation seems like the wrong way to do it.
- oomkiller 14y agoThere is a download link under options for pictures in "theater" mode. I haven't run into any WebP images yet, so I'm not sure if it downloads as jpg or not, but I've read it gives you the jpg link.
- tnorthcutt 14y agoIn the case of the images linked in the CNet article (https://www.facebook.com/photo.php?fbid=457095677701847&set=a.457095547701860.1073741825.120666121344806&type=3&theater https://www.facebook.com/photo.php?fbid=457095677701847&...), it gives you a download link for the jpeg. However, the images in that album are displayed as jpeg (for me), and the only way to view the .webp image is to open in a new tab and add the .webp extension in the url myself.
- jrockway 14y agoI'm not sure if one user's ungrammatical post to a mailing list means much. These are the people that post angry comments on readwriteweb when they search for "facebook login" and click through to an article instead of Facebook: http://readwrite.com/2010/02/10/facebook_wants_to_be_your_one_true_login http://readwrite.com/2010/02/10/facebook_wants_to_be_your_on...
- kozikow 14y agoSolution: Someone write chrome plugin that will let people convert from webp to jpeg when downloading from chrome: https://groups.google.com/a/chromium.org/forum/?fromgroups=#!topic/chromium-discuss/oUBhAMDX17U https://groups.google.com/a/chromium.org/forum/?fromgroups=#... . Just add option "Save and convert webp to jpeg" next to "save as" if plugin detects it may be webp.
- paulbeattie 14y agoWhy is this even a news story? Surely if anything we should be praising the use of a new and arguably beneficial image format rather than complaining about some users incompetence to grab a view to open it on their computer. It really seems such a bizarre thing to be complaining about. Facebook could make it a little easier by having a download as jpeg image option as well. The world is always moving forward, why don't we just go back to bitmaps!
- smackfu 14y agoNot sure why it's news, but it is definitely an interesting thing to consider for web developers. Serving people WebM in contexts where they might want to save the file will be surprisingly problematic.
- acdha 14y agoPeople care about pictures which are important to them. They don't care about the encoding scheme currently in vogue or reducing Facebook's bandwidth bill by a small percentage at a significant interoperability and thus usability hit. The average computer user has been able to use “Save As” on images for every image they've every seen online with little question that the result will work with their local applications – until now. The most charitable way I can describe your decision to blame the user is poorly considered. I would like to see new formats catch on but early adopters have to assume responsibility for the growing pains – Facebook making the trivial effort required to make their download link more prominent is about as easy as it gets.
- snogglethorpe 14y agoWebP is a pretty "meh" format. The improvements it offers are, at best, very marginal. Given the large amount of work required for widespread adoption of new image formats, the effort would be better spent on better formats. [E.g. (and I'm no fan of MS) MS's new image format, JPEG XR†, which seems vastly superior to WebP in almost every way—it actually does have compelling new features.] † http://en.wikipedia.org/wiki/JPEG_XR http://en.wikipedia.org/wiki/JPEG_XR
- cromwellian 14y agoIs this really happening via the "Download" link, or is this being caused by people right clicking and saying "Save Image As..." because if you want to preserve or work with images, you probably should not be saving images from the context menu, which are often scaled and processed, and instead be asking for the original/raw/high resolution upload.
- pixelcort 14y agoDo images on Facebook even have a download link? Edit: Why yes they do! It's in a drop down menu.
- twerquie 14y agoYes
- smackfu 14y agoThat's nice in theory, but for years, Facebook photos had no download link, and the only option was to Save As the one you could see. It's very confusing for people when the only way to do something suddenly becomes the wrong way to do it, for no reason they can see.
- alexwright 14y agoSo we should all stand still in time because current tech is understood by this generation? You have to draw a line somewhere. The download has in fact been there for years now, at least since late '09. I only remember because we had to download a bunch of images and our only source without giving away a surprise was FB. I was given a bunch of crappy 70% 800x600 .jpgs and I had to show the person getting the images the download like, which at the time wasn't even in the Options menu. Users...
- liveaxle 14y ago"In my testing, I found only subtle differences between the original JPEGs I uploaded and the WebP versions Facebook created from them." LOL! Upload a JPEG, expect better quality from the transcoded WebP output. Yeah, someone needs to teach the writer about generation loss.
- six 14y agoThe funniest thing about this article was the image comparison between JPG and WebP, saved as JPEG-vs-WebP.jpg. Nice one CNET.
- lttlrck 14y agoPar for the course...
- dvhh 14y agoI'm somewhat curious of the reason of why some users would like to download images from facebook.
- Terretta 14y agoI was struck by the supposed reluctance to update the browser's accept header to specify that the browser now accepts this image type. It's what it's for. The "every time you add a byte it stays" argument is specious -- how often have we added an image format to the web? http://en.wikipedia.org/wiki/Content_negotiation http://en.wikipedia.org/wiki/Content_negotiation
- niels_olson 14y agoGimp has a plugin for WebP support http://registry.gimp.org/node/25874 http://registry.gimp.org/node/25874 http://ubuntuforums.org/showthread.php?t=1809284 http://ubuntuforums.org/showthread.php?t=1809284 Apparently Photoshop does too: https://groups.google.com/a/webmproject.org/forum/?fromgroups=#!topic/webp-discuss/QU9xSMZO-A4 https://groups.google.com/a/webmproject.org/forum/?fromgroup...
- Lewisham 14y agoI think this kerfuffle does point at something that would be nice to have ratified in the HTML spec somewhere: the idea that content exists in different qualities and formats, and that when the user requests to download the content, she's presented with the different options possible. Content negotiation still only has one chosen format come down the pipe; a decision that the user probably hasn't made. Right now, we're stuck with everybody doing something different in the page design to do something that's pretty important and fairly intrinsic to much of what happens on the web. And so users just default to the thing they know works everywhere, which is Save As... It's not surprising some of them are upset. The only issue I can see with this is that there are security concerns with being able to override what is actually downloaded when Save As is used.
- kalleboo 14y agoThe article touches upon the HTTP Accept header which does just that. Most browsers haven't implemented it properly for images yet though. https://developer.mozilla.org/en-US/docs/HTTP/Content_negotiation https://developer.mozilla.org/en-US/docs/HTTP/Content_negoti...
- ElliotH 14y agoI always wish HTTP Accept was widely used to present alternate formats and presented to users in a nicer way. It basically solves all this kerfuffle, it seems oft forgotten outside of XML/JSON/HTML in api's though sadly.
- igrigorik 14y agoWe just landed "image/webp" in Accept header in Chrome, behind a flag.. Opera already advertises WebP support in their Accept header. So, with that in place, it should make things a lot simpler (although it doesn't solve the Save As case).
- paulirish 14y agoIn Chrome, it looks like we're going to register as the default handler for webp images, so they're viewable post-download, similar to what's done with PDFs: https://code.google.com/p/chromium/issues/detail?id=234275 https://code.google.com/p/chromium/issues/detail?id=234275
- username3 14y agoIn Chrome, right click, copy image, paste in Paint.
- pornel 14y agoIt is a symptom of lack of interoperability. People do share images. They link them. They save them. They e-mail them. They mix and edit. They re-upload them to other sites. JPEG has such a broad interoperability that we don't even notice just how incredibly many sites/apps/libraries/OSes/devices support it. Having WebP support only in Chrome is not enough for it to be 1st class citizen. Just think how many apps and services need to adopt the format before you'll able to upload your avatar in WebP without worrying it won't work.
- jedberg 14y agoI remember this exact same argument about 20 years ago when JPG started getting popular. "I need a special program to see it?" The viewers and OSs and browsers will catch up soon enough.
- vlasta2 14y agoBut JPG was like 10x better than the other image formats available at that time for photographs. WebP hardly delivers 1.2x improvement... This is virtually unnoticeable.
- acdha 14y agoJPEG was an enormous improvement, particularly given the far slower connections in use at the time: waiting minutes rather than hours to download an image over my 2400bps modem was huge. In contrast, WebP offers marginal compression improvements, significantly increased hardware requirements and only a few technical improvements (e.g. alpha channels & lossless, although since the latter is so much slower and less effective than PNG I'm not sure there's much of a point). For many users, this simply isn't enough to justify pushing it through the toolchain.
- ZeroGravitas 14y agoIt may be slower but why do you think its less effective? http://extrememoderate.wordpress.com/2011/11/28/a-web-centric-image-compression-benchmark/ http://extrememoderate.wordpress.com/2011/11/28/a-web-centri... And that's not counting the benefits of when PNG is used for alpha in otherwise photorealistic images where you can get 70% benefits at web sizes.
- acdha 14y agoLess effective = lower compression savings. I was testing with source lossless JP2s in the 6MB range: PNG was 14MB and WebP took at least 10x compression time to hit 20MB (tied with TIFF LZW for least savings).
- 14y ago
- DanBC 14y agoHas Google provided patches to all the open source image tools to handle WebP images?
- yebyen 14y agoThis can only be a troll... 'all the open source image tools'? That seems like an intractable set to me. They shouldn't need to. I see there's an imlib2 webp loader. It is BSD licensed. I don't see that it came from Google. So what's your point? We're supposed to be hating Facebook anyway, not Google in this article.
- DanBC 14y ago"Some of the most popular open source tools" would have been better. Google is a huge company, with many good programmers. A reference implementation is great. Provide patches to some of the most used open source products just helps Google spread their tech, and helps all those open source products. My post wasn't meant to be a dig at Google. Re-reading it I see that it could be read that way, and I apologise for that.
- yebyen 14y agoI understand. https://developers.google.com/speed/webp/download https://developers.google.com/speed/webp/download There is a set of command-line utilities, a library with source, and a codec for Windows Imaging Component which has no parallel in Linux that I am aware of. (save imlib2 and friends) I don't know any project that uses image formats in any way and does not link directly with libpng, libjpeg, lib(un)gif, or other directly supporting libraries that are tied to individual formats. There is an evas webp loader on eina, which is no help to Gnome or KDE users, and there are dozens if not hundreds of projects that probably need support to be added. Don't know how ubiquitous Windows Imaging Component is in MS-land, but it seems like a much easier problem to have solved.
- Steko 14y agoMy understanding is that WebP is superior to Jpeg when encoding from a lossless image but: (1) if I upload a lossy jpeg what gains is FB really getting by using WebP? (2) Or am I taking a quality hit on what they serve? Let's say there's no quality hit and somehow they make a lossless WebP version of my lossy jpeg that still fits in 20% fewer bytes. Define X as the dollar savings gained by delivering these images scaled up to quadrillions of images served. My understanding is that WebP makes it's gains by a 10x longer encode. Define Y as the dollar cost of encoding and storing trillions of images in WebP. (3) What are the odds X is actually greater than Y?