Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics. If you need to do this, try [email protected]
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Formats are chosen by the uploaders and hosts, not the end user.
For easy conversion of images from the web, I recommend the FF addon Save webP as PNG or JPEG. Anytime you open an image in its own tab, it pops up with a menu that gives you a quick button to choose the format you'd like to save it in.
In some cases it’s chosen by a third party.
My employer uses Akamai for CDN, security, etc. One of the optional services they offer is called Image and Video manager (IVM). One of the things IVM does is analyze image files and converts them to multiple target formats based on how you set it up.
Suppose you have an image on your website that is a 1000x1000 pixel PNG file that’s 500k in size. The first time a client fetches it Akamai will serve it as-is but will also hand off its URL to an image processing server. That server will analyze the image, and based on how you configure it, might create multiple JPEG & WEBP formats that are 250x250, 500x500, and 750x750 in size, as well as 1000x1000. The new images are highly optimized without impacting the perceptual quality, and all smaller than the original images size.
Once these images are created Akamai adds them into their CDN cache alongside the original image. Now when a client requests the original PNG file they may actually serve one of the other versions based on the browser being used and device characteristics like viewport size, etc. But it’s all 100% transparent to the end user.
https://www.akamai.com/products/image-and-video-manager
You're not wrong of course, but I really need people to understand that this level of detail is not what a top-level reply to a lower-end technical question is aiming for. Maybe this will be helpful to someone, but I already knew it and didn't need it sent to me, and it's going to go above OP's head. For the average end user, this is abstracted somewhere in the "host stuff" layer, and that's fine.
I just change .webp to .jpg and it works fine. I'm not sure what that does though or even if it's necessary.
Yeah, doing that does absolutely nothing. Your image viewer still reads it as the webp it is, and it knows to do so seamlessly because it's reading the file header (the first few bytes of the file) instead of the file extension.
For an analogy, you're basically just putting a wig on it and pretending it's your girlfriend from the next school over when everyone in the room knows it's your skeezy neighbor and is just humoring you.
If it tells you it doesn't accept webp and you change it to jpg and it works, I guess it's doing something, lol. I'm sure it doesn't change the file type, it's a loophole.
fair but "it" here is pretty vague. my guess is that, in your case, whatever part of "it" that processes the image handles webp files just fine but for some reason the devs made "it" reject file extensions that don't match ".jpeg", ".png", ".whatever_else" for some reason before the file gets handled further.
Even if a webp is still accepted, I still have that distrust though. The marketing people should have let everyone who works with pics know what they are. I use non-standard software so maybe that's why I'm clueless as to what it actually does. Again, I've got a lot on my plate so it never really comes up as first priority to figure out what it is.
Edit: I thought you were someone else, sorry about that. Still leaving it since it's still valid, lol.
It would be helpful for the discussion if you would tell us what the mystery program is, that is handling images in this strange way and what operating system you are on.
I don't remember, it was a while ago. I'm on windows 10 and I use Affinity for all photo editing. I think it had something to do with a header for a site, that's the distant memory anyway. That's kind of my point, I remember the distrust but not the circumstances. As I told someone else, I'm not trying to bust anyone's balls, feel free to ignore me. I'm just trying to give you the every man perspective. It is just mine and only one perspective.