Make a WebP image usable in a JPG-only workflow
Some forms and older workflows accept JPG but do not accept WebP. This page converts a supported static WebP to JPEG rather than merely changing its filename extension. JPG is preselected, and you can adjust quality, dimensions and the fill colour for transparent areas. Check the receiving system for any separate size or dimension limits: a correct format does not mean every upload will be accepted.
JPEG cannot represent transparent pixels. Choose a background that matches the intended use and confirm that choice in the controls before generating the image. A white website may need a white fill, while other designs may need another colour. Animated WebP is not supported; silently exporting its first frame would discard content. Keep the source WebP for any later use requiring transparency.
Worked example
For a transparent icon intended to sit on a white page, choose white and explicitly confirm the background. The JPEG will contain that fill instead of alpha transparency. A 160 by 100 source remains 160 by 100 if the dimensions are unchanged. The resulting file may increase in size; this task is about the receiving format rather than a guaranteed reduction.
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.