Convert WebP to JPG

Transparency survives when going to PNG, WebP, TIFF, GIF, ICO, PSD or SVG. Converting to JPG / JPEG / JFIF flattens the alpha channel against a white background — if you need transparency, target a transparency-aware format instead of JPG.

Embedded ICC color profiles are read from the source WebP and re-attached to the JPG output where the format supports it (JPG, PNG, TIFF, WebP, PSD). Formats without profile support (GIF, BMP, ICO, SVG) fall back to sRGB.

Camera EXIF (ISO, shutter, lens, GPS) is preserved by default during WebP → JPG conversion when both formats support metadata (JPG, TIFF, WebP, PSD). Use the privacy option to strip metadata before download if you want to share images without geolocation.

Yes — drag multiple WebP files into the upload zone and we queue them in parallel. Free users get 100MB per file; Premium has no per-file cap and runs more parallel workers, so a 200-image batch typically finishes in under two minutes.

For straightforward format conversion we run the same libpng / libjpeg-turbo / libwebp / ImageMagick pipelines a desktop editor uses, with the same output quality. The difference is that desktop tools open one file at a time; jpg.to accepts a batch and runs them in parallel.

Default behaviour is 1:1 — your JPG output has the same pixel dimensions as the source WebP. ICO output is the exception (it produces a multi-resolution stack: 16/32/48/64/128/256). If you need to resize as part of the conversion, use /resize/ after conversion.

For JPG / JPEG / WebP, quality 75-85 typically gets the file 60-80% smaller than the source WebP with no visible difference at normal viewing distance. For lossless targets (PNG, TIFF, BMP), expect smaller savings — usually 5-30% via better deflate / LZW compression.

Yes — uploaded WebP files are processed in isolated workers and deleted within minutes. We never read, store, or share the pixel data. The full privacy policy and retention window are documented at /privacy/.

Yes for free up to 100MB. Premium handles larger inputs (300MB+) and exotic per-pixel depths (16-bit PNG, 32-bit float TIFF, multi-layer PSD). The pipeline streams pixel rows, so memory use scales with the row count not the total pixel count.

Size is decided by the two compression models, not by the converter. Remember that WebP carries both a lossy VP8 mode and a lossless mode plus full alpha, typically landing 25-35% under a JPG of matching visual quality, whereas JPG stores 8-bit RGB through a lossy DCT with 4:2:0 chroma subsampling by default, so fine red text and hard edges are the first things to soften — so a heavily-compressed WebP usually GROWS when re-encoded into a lossless JPG, and a bulky lossless WebP usually shrinks sharply going the other way. Image content matters too: photographs and flat line art compress very differently.

Yes. The conversion is a format change — copyright on the image content stays with you (or whoever held it on the source WebP). We add no watermark, no metadata stamp, and claim no licence over the output.