JPG to WebP — Convert JPEG Images to WebP
Convert JPG images to WebP for smaller file sizes at the same visual quality. Lossy and lossless modes, runs in your browser. No uploads, no limits.
Drop your JPEG image here
or click to browse (max 50MB)
WebP was introduced by Google in 2010 as a modern replacement for the JPG/PNG pair, and over the past decade it has become the default image format for the web. The argument is straightforward: at equivalent visual quality, WebP produces files 25-35% smaller than JPG for photos, and the same files are typically smaller than PNG for graphics too. The format also adds features JPG cannot match — an alpha channel, lossless mode, animation — all in one container. Every modern browser supports it; the only audience that cannot render WebP is users on Safari 12/13, which is a shrinking fraction of web traffic but still exists in locked-down enterprise environments.
The conversion from JPG is one-directional in a specific sense. JPG is always lossy — every save drops pixels. Converting a JPG to WebP at lossy quality 80 produces a WebP that is visually equivalent to the JPG but cannot be losslessly restored to the original JPG. The conversion is not a re-wrap; it is a re-encode through a different (and better) compression algorithm. The output is smaller, but the JPG’s original compression artifacts (blocking, ringing) are not preserved — they are subsumed into the WebP’s own (smaller) artifacts. For archival workflows where the original JPG must be recoverable bit-for-bit, this is the wrong conversion.
For a final hand-off: if the destination is a modern website, WebP is the right pick — <picture> with WebP and JPG fallback handles the Safari 12/13 audience while serving WebP to everyone else. If the destination is email, JPG is still the safer choice because many email clients (Outlook on Windows, older Gmail renderers) do not support WebP. If the destination is a CMS that already optimizes images server-side, check whether the upload pipeline converts to WebP automatically — adding the conversion manually may be redundant.
How to use
Drop one or many JPGs
Drag .jpg or .jpeg files into the drop zone, or paste from clipboard. Batch conversion processes each file independently and the queue shows progress per item.
Choose lossy or lossless
Lossy (default) is smaller and visually equivalent for most photos at quality 80. Lossless preserves every pixel exactly — useful for editing or pixel-perfect comparison.
Download the WebPs
Each file converts in under a second on a modern device. Downloads are individual by default; switch to zip mode for batches above a dozen files.
Frequently asked
How much smaller is WebP than JPG?
At equivalent visual quality, WebP is roughly 25-35% smaller than JPG for photos. The exact saving depends on image content — photos with smooth gradients benefit the most, photos with hard edges benefit less. WebP uses the same general approach as JPG (DCT-based lossy compression) but with better entropy coding and the ability to use lossless mode on parts of the image.
Will all browsers open WebP?
Chrome, Edge, Firefox, and Safari 14+ all support WebP. Safari 12 and 13 cannot decode WebP. If the audience includes those versions (rare today but still possible in locked-down enterprise environments), fall back to JPG instead.
Is lossy WebP visually identical to the JPG?
At quality 80, the difference is below the threshold of perceptual diff tools (DSSIM, butteraugli) on most photos. For pixel-perfect comparison, use lossless mode — the output is bit-identical to the source at the cost of a larger file.
Does WebP support transparency?
Yes — WebP supports an 8-bit alpha channel, same as PNG. JPG cannot carry transparency, so the source has no alpha to preserve. The output WebP is RGB-only unless the source had alpha (rare for JPG) or the 'force alpha' toggle is enabled.
Will the EXIF data survive?
By default EXIF is stripped to maximize the size saving. Toggle 'preserve metadata' to keep the EXIF block — useful for archival workflows but adds 5-15% to the output size on photos.
Limitations
- Limited legacy supportWebP requires Safari 14+ on Apple platforms and modern versions of Chrome, Edge, and Firefox. For audiences on older browsers (Safari 12/13, IE 11), JPG is the safer pick — it has been universally supported since the 1990s.
- Lossy is still lossyLossy WebP re-encoding drops information that cannot be recovered. Photos soften slightly at quality 80; quality 95 is visually indistinguishable from the source for most purposes. Use lossless mode if pixel-perfect output is required.
- No animation from JPGJPG is always static, so the output is a static WebP. WebP supports animation, but the source has no frames to animate. For animated images, start from an animated GIF or APNG source.
Platform notes
- macOS
- Safari 14+ on macOS Big Sur and later renders WebP inline. Earlier versions need a Quick Look plugin. The browser tool is the right pick for converting JPGs from a designer's working folder or a stock photo download that need to land as WebP for a modern web project.
- Windows
- Microsoft Edge and Chrome have supported WebP since 2014. Windows 11's Photos app opens them; Windows 10's older Photos app may need the Webp Image Extension from the Microsoft Store for full preview support.
- Linux
- Most distros include libwebp in their default image stack. For command-line work, `cwebp -q 80 input.jpg -o output.webp` is the closest CLI equivalent. The browser tool is the right pick for batch conversion of images pasted from a chat or email.
- Web
- Runs entirely client-side. Works offline once the page has loaded. Useful for ad-hoc conversion in restricted environments where command-line tools are not available.