Re-encode a JPG as WebP so the same photo downloads faster on every page.
Swap: WebP to JPGPhotos are what makes a page heavy, and WebP stores the same photograph in noticeably fewer bytes than JPG does.
At a comparable visual quality, a photo encoded as WebP usually comes out 25–35% smaller than the JPG it was made from. On a gallery of twenty product shots that is hundreds of kilobytes saved per visit, on every visit, without touching the layout or the markup.
Some platforms generate WebP copies on the fly, but plenty do not: a hand-built site, an email template, a static folder of images, a shop migration. Converting the files yourself works everywhere, including places where nothing rewrites your uploads afterwards.
WebP files keep the same pixel dimensions and the same aspect ratio as the JPG, so they drop into the same spot in a layout. Only the file name extension changes — swap the source in your image tag or media library and the page is done.
Two lossy formats in a row: the settings decide how much the picture pays for the saving.
The JPG you start with has already been through a lossy encoder. Encoding it again as WebP adds a little more softness, so keep the quality at 82 or above — and if the original camera file or PNG master still exists, export the WebP from that instead. Going back with the WebP to JPG converter cannot recover what the second pass removed.
JPG never had an alpha channel, so the WebP is fully opaque and the Background field makes no visible difference. That also means the cut-out trick does not work here: a JPG of a logo on a white box stays a white box. If transparency is needed, start from a PNG with the PNG to WebP converter.
WebP can hold an animation, but this page writes a single frame — and a JPG source has only one frame to begin with, so nothing is lost. An animated source, such as an animated WebP fed through another tool, would arrive as its first frame.
A photo that relies on an EXIF orientation tag is turned upright on the way through, with width and height swapped to match, so it does not appear sideways once the tag is gone. Shooting details, GPS position, thumbnails and edit history are not copied into the WebP, which also trims a few kilobytes.
Three steps, no account and nothing to install.
Drag the photo onto the box, click to browse, or paste it with Ctrl+V (Cmd+V on a Mac). One file per run, up to 25 MB.
Leave quality at 82 for photos, or drop to 78 if the saving matters more than the finest detail. Set the width to about twice the size the image is displayed at; leaving it empty keeps the original dimensions and whatever file they came with.
The result shows the old and new weight side by side. Download the .webp, upload it where the .jpg was, and compare the page load — the picture itself should look unchanged.
Where the saving comes from, and where it does not.
A 4000 px photo shown in a 600 px slot is wasting data whether it is JPG or WebP. Halving both sides removes three quarters of the pixels before the encoder runs, so resize first and then choose a quality — or let the compressor cap the width and re-encode in one pass.
Skies, studio backdrops, skin and shallow depth of field are where blocky patches appear. If the photo is mostly a smooth gradient, keep quality at 82–85; for a busy texture shot, 75 is often indistinguishable and considerably smaller.
WebP is read by every current browser, but a file that also has to open in an old desktop app or reach a print service is safer as a JPG. Keep the original next to the WebP — it costs nothing on disk and saves a re-download if the compatibility question comes back.
Yes. Convert as many files as you like: no account, no payment, no watermark, no cap on conversions. A short rate limit keeps one visitor from occupying the server for everyone else.
For photographs, usually 25–35% at a quality that looks the same on screen, and sometimes more when the JPG was saved at a high quality. The result panel shows the exact before and after weights, so you can try quality 78 and 85 and keep whichever balances size and detail for your images.
Each pass through a lossy encoder costs a little sharpness, and the JPG has already had one. Keep quality at 82 or higher and the second pass is hard to see; repeat it on the same file and softness starts to build up. Export the WebP once from the best source you have and publish that copy.
A JPG has no transparency, so the WebP is opaque and the Background field changes nothing. Orientation stored in EXIF is applied so the photo comes out upright, and camera details, GPS position and other metadata are dropped rather than copied. The output is a single still frame.
Up to 25 MB per file, and 50 megapixels per image. Files are processed on our server and not stored — only the finished WebP travels back to your browser.
