JPG to WEBP Converter

Why WEBP

WEBP was built by Google to make web images smaller without making them look worse. At the same visual quality, a WEBP is usually 25-35% smaller than the equivalent JPG. For a site with a lot of photos, that adds up. Every modern browser supports it.

What this does

• The browser decodes your JPG.
• The same pixels get re-encoded as WEBP at the quality you pick.
• One file in, one file out. Multiple files come back zipped.

Picking a quality level

The Standard preset (0.85) is the safe default. High keeps almost all the detail and is worth it for big hero images. Compact strips more aggressively and is fine for thumbnails or social posts where nobody zooms in.

Nothing leaves your browser

The work happens locally in this tab. Disconnect from the internet after the page loads and you'll see the conversion still completes.

About the JPG format

JPEG was finalized in 1992 by the Joint Photographic Experts Group, an ISO/IEC working group. The .jpg short extension exists because old Windows insisted on three-letter file extensions; .jpeg is the same file. JPG uses discrete cosine transform compression — fantastic for photographs, lossy by design, and bad for sharp lines. The format has been the universal photo standard for three decades. Every camera, browser, social network, and print service handles JPG without question. Its weaknesses are also well known: no transparency, visible compression on flat colors, and degradation every time the file is re-saved.

About the WEBP format

WEBP came out of Google in 2010. The format was adapted from the VP8 video codec Google acquired with On2 Technologies that year, with lossless and animated modes added later. WEBP achieves roughly 25-35% smaller files than JPG at the same visual quality, and supports a full alpha channel. Adoption was slow at first because Safari and older browsers held out, but every modern browser ships WEBP support today. Google built WEBP specifically to cut page weight on the web, and that's still where it shines.

When to use JPG to WEBP (and when not to)

Good cases:

• You're optimizing images for a website and want page weight to drop.
• You're storing a personal photo archive and want it to take less disk space.
• You're sending photos through an app that supports WEBP natively (Discord, modern messengers).
• You're prepping assets for an Android or web app where WEBP is the recommended format.

Don't convert if:

• The photos are going somewhere with iffy WEBP support — older email clients, certain photo printers, legacy CMSes.
• You're sending to recipients on Windows 7 or Office versions that won't preview WEBP.

Common problems and how to fix them

• WEBP files came out bigger than the JPG. Rare, but it happens when the source JPG was already very heavily compressed. The encoder has nothing to gain. Stick with the JPG in that case.
• Visible smearing on faces or skies. Drop the quality setting one notch up, from Compact to Standard or High. Aggressive compression hits gradients first.
• Older software won't open the WEBP. WEBP support landed in Windows in 2018 and macOS in 2020. Anything older needs a viewer like XnView or IrfanView.
• Sideways photo. EXIF orientation should carry through. If it doesn't, rotate-save the JPG first in any image viewer.
• Wrong file extension after download. Browsers occasionally save .webp as .webp.jpg on certain mobile configurations. Rename the extension manually if needed.
• Color shift on saturated images. WEBP uses YUV color space internally, same as JPG, so this is rare — but on wide-gamut sources it can clamp. Use the High preset if it matters.

Frequently asked questions

Related converters