JPEG and JPG are the same file — different extension, same mozjpeg bytes. This page covers the JPEG spelling; the workflow is identical to JPG → WebP.
JPG and JPEG are the same format — this page and /jpg-to-webp/ cover the same workflow. Start there if you prefer the JPG spelling.
No separate engine, no separate steps. Compressy treats .jpg and .jpeg as the same when converting to WebP.
Pick JPEGs, choose WebP output, pick quality 40–95 — same as JPG → WebP.
JPEG is just the four-letter extension for JPG. Select a folder — both .jpg and .jpeg are found as JPEG and converted to WebP with the same quality control. Keep EXIF or strip it, downscale or keep dimensions — all local. No upload, no account. If you landed here from a search for JPEG, you can follow the JPG → WebP workflow below — every step applies.
Identical to JPG → WebP.
Drop a folder — .jpg and .jpeg together. Keep subfolders.
Quality 75–85 for photos, alpha stays. Preview per file.
Batch locally on all threads. No cloud.
Because the engine is the same, savings match JPG → WebP.
Numbers from JPG → WebP at quality 80 — JPEG behaves identically.
No. Same format — JPG is three letters, JPEG is four. Compressy treats both as JPEG and converts to WebP the same way. Use either page.
Yes. Drop a folder — both extensions are found and converted to WebP together, keeping subfolders.
No. All JPEG → WebP is local. No upload, no account.
JPEG to WebP offline — identical to JPG → WebP.