Convert image formats
Pick a target format, then add images. Converting to a heavier format can grow the file; the result view reports the byte change either way.
- Up to 50 files
- 40 MB each
- Deleted after 2 hours
Two things JPG cannot keep
First, JPG has no transparency. Any alpha channel in your WebP is flattened during conversion, so cutouts and overlays gain a solid background. If transparency matters, convert to PNG instead.
Second, JPG encoding is lossy, and your WebP was likely lossy already. One conversion at sensible quality is normally invisible; repeated round-trips between lossy formats are not. Keep an original and convert once.
Size can go either direction
A lossy WebP re-encoded as JPG often grows somewhat, because JPG needs more bytes for the same quality. A lossless WebP converted to JPG usually shrinks. Rather than promising either outcome, the result view shows the exact byte change per file and labels increases as increases.
When this conversion makes sense
Reach for JPG when a recipient or platform demands it: email attachments, older CMS uploaders, print shops, marketplaces with strict format lists. For your own website, the arrow points the other way — modern formats first with JPG as the fallback. Convert up to 50 files per batch; everything is deleted after two hours.