Questions about JPG and WebP
Does converting a JPG to WebP lose quality?
A little, in principle — your JPG was already compressed once, and WebP compresses again. In practice the second pass is invisible at normal settings, because WebP throws away different information than JPEG does. If you are archiving originals, keep the JPG and publish the WebP; if you are publishing to the web, the difference will not survive a screen.
Should I delete the original JPG?
Keep it if it is a master file — a product shot you may re-crop, a photo you might print. Delete it if it was only ever a web copy. WebP is a publishing format, not an archival one.
Do all browsers show WebP?
Yes. Every browser in current use has supported it for years, including Safari since version 14 and every version of Chrome, Edge and Firefox people still run. You do not need a JPG fallback in 2026.
Are my images really not uploaded?
Correct. The conversion uses your browser's own image engine, so the file is read from your disk into the tab and never sent over the network. Open your browser's network panel and convert something — no request is made.
How does the target size work?
The converter encodes your image, checks the result against your target, and adjusts quality until it fits. If quality alone cannot get there, it reduces the dimensions in steps rather than destroying the picture. You always see what happened.
Is there a limit on how many files I can convert?
None from us — your computer does the work, not our server. The practical ceiling is around 40 megapixels per image, where browsers stop being reliable.