JPEG to WebP converter

JPG → WebP applied our EXIF orientation tag, turning a 96×64 portrait-flagged JPEG into a 64×96 WebP.

Converted with Image engine · nothing stored
Free: 5 conversions a day · 5 MB each
Higher limits →

From real runs

What you get — and what changes

Element	Result	What happens
EXIF orientation	Changed	The Orientation 6 test photo was transposed into upright pixels, so the output dimensions became 64×96.
Camera EXIF	Lost	Make, Software, Artist, and Orientation tags from the JPEG did not appear in the WebP output.
ICC profile	Lost	The sRGB ICC payload present in the input JPEG was not listed after opening the output WebP.
Compression	Changed	Our 3,044 byte JPEG sample became a 1,046 byte WebP at quality 90 after orientation was applied.
JPEG artifacts	Kept	Noise and block edges already baked into the source JPEG remain part of the pixels WebP encodes.
Transparency	Lost	A normal JPEG has no alpha channel, so the WebP output from a JPG source is fully opaque.

EXIF orientation Changed
The Orientation 6 test photo was transposed into upright pixels, so the output dimensions became 64×96.
Camera EXIF Lost
Make, Software, Artist, and Orientation tags from the JPEG did not appear in the WebP output.
ICC profile Lost
The sRGB ICC payload present in the input JPEG was not listed after opening the output WebP.
Compression Changed
Our 3,044 byte JPEG sample became a 1,046 byte WebP at quality 90 after orientation was applied.
JPEG artifacts Kept
Noise and block edges already baked into the source JPEG remain part of the pixels WebP encodes.
Transparency Lost
A normal JPEG has no alpha channel, so the WebP output from a JPG source is fully opaque.

Sample conversions

EXIF-rotated camera photo

Input: A 96×64 JPEG with Orientation 6, camera Make and Software tags, an Artist tag, and an sRGB ICC profile.
Output: A 64×96 WebP, 1,046 bytes at quality 90. The image was upright, but EXIF and ICC metadata were gone.

Noisy photographic test

Input: A 320×240 noisy JPEG, 74,881 bytes, created to make quality changes visible in output size.
Output: At quality 20 the API wrote a 17,484 byte WebP; at quality 90 it wrote a 51,758 byte WebP.

A real JPEG → WebP run

We converted our JPEG sample (42 KB) with Image engine on 2026-10-20. It took 92 ms and produced a 22 KB WebP file, 48% smaller than the input. The engine raised 1 warning, listed below.

Input · sample.jpg · 42 KB

1200 × 800 px, baseline

Width: 1,200
Height: 800
Encoding: baseline

Output · sample.webp · 22 KB

1200 × 800 px, lossy VP8

Width: 1,200
Height: 800
Encoding: lossy VP8

Image metadata stripped from output.

Is your file a scan?

If the JPEG is a photographed receipt or whiteboard, WebP conversion will not make the words searchable. Use image-table-to-excel or screenshot-to-text when the content needs extraction.

Options and when to change them

quality: Lower it for thumbnails and feeds; raise it when gradients, hair, or product edges show visible WebP artifacts.
width: Resize large camera JPEGs while converting so the WebP is sized for the actual display slot.
height: Use with width for exact crop boxes; omit one dimension when preserving the camera aspect ratio matters.
fit: Use cover for fixed cards, contain for full-photo previews, and fill only when geometric distortion is intended.

Do it yourself

cwebp

bash

cwebp -q 90 in.jpg -o out.webp

Run an EXIF transpose step first if your JPEG relies on orientation metadata rather than stored upright pixels.

Pillow 11

bash

from PIL import Image, ImageOps

im = ImageOps.exif_transpose(Image.open("in.jpg"))
im.save("out.webp", quality=90)

This mirrors the tested orientation behavior but does not preserve camera metadata.

JPEG to WebP by API or MCP

The HTTP API and the MCP server run the exact engine this page uses (Image engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=jpg&to=webp.

curl

curl -X POST https://filetypeconverters.com/api/v1/convert \
  -H "Authorization: Bearer $FTC_API_KEY" \
  -F "file=@input.jpg" -F "from=jpg" -F "to=webp" \
  -F 'options={"dpi":96}' \
  --output output.webp

Options this engine accepts for JPEG → WebP

Key	Applies to	Type	Default
dpi	Reading JPEG	number	96
width	Writing WebP	number	0
height	Writing WebP	number	0
fit	Writing WebP	contain · cover · fill	contain
quality	Writing WebP	number	90
background	Writing WebP	string	#ffffff
stripMetadata	Writing WebP	boolean	true

API reference

When this is the wrong conversion

Keep JPG if the target is an older email client, ad network, or image pipeline that does not accept WebP.
Use the original camera file rather than JPG → WebP if you need metadata as evidence.
Use AVIF when the destination supports it and smaller photo delivery is the main goal.

JPEG to WebP questions

Does JPG → WebP respect EXIF rotation?

Yes in the tested API path. The orientation tag was applied to pixels, and the output dimensions changed accordingly.

Will WebP keep my camera metadata?

No in our run. The resulting WebP did not expose the JPEG EXIF tags or the ICC profile we inserted.

How much smaller is WebP than JPG?

It depends on the image. Our small EXIF sample went from 3,044 bytes to 1,046 bytes, while a noisy photo at quality 90 kept more bytes to preserve detail.