Short answer: the website is probably sending WebP because your browser supports it. Chrome and Edge save the bytes they receive; they do not necessarily have access to the JPG or PNG that may have existed before the website optimised it.
WebP is usually chosen by the website
Sites use WebP to reduce bandwidth and improve loading speed. They may provide different formats through a <picture> element, responsive image markup, a content-delivery network, or server negotiation based on browser capabilities. Two visitors can therefore receive different file formats for what appears to be the same image.
Why changing .webp to .jpg fails
A filename extension is only a label. The internal encoding remains WebP until software decodes the image and encodes it again as JPEG. Some programs inspect the bytes and open the renamed file anyway; others reject it or behave unpredictably.
Should you keep WebP?
Keep WebP when the applications in your workflow support it. This avoids another lossy conversion and often keeps the file smaller. Convert a copy when an older editor, upload form, document workflow, or recipient specifically requires JPG or PNG.
Choose the destination format
Ways to convert safely
- Prefer local processing for private files.Use a trusted desktop editor or a documented local-only browser tool.
- Keep the original.Create a converted copy so you can return to the source if quality or transparency changes.
- Inspect the result.Check dimensions, transparency, file size, and visible quality before deleting anything.
ImageMemento offers original, JPG, PNG, and WebP commands directly in the image context menu. Conversion happens locally after your action; the extension has no upload service, analytics, account, or AI.
A WebP file can be the full-size original supplied to your browser, while a JPG can be only a thumbnail. Check pixel dimensions instead of judging by the extension alone.
A quicker local option
Use ImageMemento from the right-click menu
Save the best available original or convert the selected image to JPG, PNG, or WebP inside Chrome or Edge. There are no uploads, accounts, analytics, or AI.