>>105701861Yes, they are saving bandwidth. Google also gives you better SEO if you use webp due to better lighthouse metrics. As for .jpeg images turning out to be .webp images, I don't fully understand why they do this. In some cases, it is ".jpeg.webp", in which case it's just a result of them appending the ".webp" extension without removing the ".jpeg". this makes sense because removing the old extension can be error prone and is also non-reversible because .jpg and .jpeg are both used for some reason. It's much easier to just add ".webp" to it and be done with it. In the other cases, while I'm not exactly sure, one possibility is that again it (perhaps?) makes it easier from the server side. These dynamic image delivery systems an be pretty complex. For example they can server either webp or avif depending on if your device supports it. With this said, when the server sends you the initial html file with the <img> tags in it, how should it know what URL to put in the href? It is much easier (perhaps) to send the source URL and when the users GETs the URL, the server can decide what to actually send back. After all a URL doesn't actually mean anything. A server can send back whatever result it wants, it's not a file system.