Prepare a JPEG photograph for a WebP workflow
This workspace accepts a static JPEG and preselects WebP output. It is useful when a website accepts WebP and you want to compare a new file with the JPEG you already have. Load the photograph, retain its dimensions or change them explicitly, then choose quality and generate the image. Fine textures and low-light photographs may behave differently from simple pictures, so do not assume a fixed saving.
A JPEG may already contain losses from earlier compression. Re-encoding it as WebP cannot recover that information. Keep the best original available, especially if you expect to edit the image again; repeatedly using the last compressed output can accumulate damage. Check edges, lettering and blocks of colour in the comparison view, then open the download in the target system before adopting it.
Worked example
If a 1280 by 720 JPEG is converted without changing the pixel fields, its WebP output remains 1280 by 720. The file size depends on the source and selected encoding settings. A change in format alone is not a resize. If a receiving form rejects WebP, keep the JPEG or choose a format that form explicitly permits.
Local processing and limits
One supported static image is processed at a time. The general input limit is 10 MiB and twelve million pixels; AVIF processing is limited to four million pixels. Unsupported animation, image sequences, HDR and unverified container features are refused. Large images need more memory even when their compressed file is small. A failed operation does not switch to a server-upload fallback.
The browser downloads its own application and codec resources from the same host. Your selected image, result, filename and metadata are not sent to an upload service. Images are not written to localStorage, IndexedDB or a service-worker recovery cache. Reloading the page leaves the image workspace empty. Downloaded files remain under your control; inspect them before sharing.