JPG / PNG to WebP Converter (and WebP to JPG)
Convert JPG and PNG images to WebP (or WebP back to JPG/PNG) in your browser with a quality slider and before/after file sizes — batch up to 20 files, nothing uploaded.
In short
WebP compresses photos about 25–35% smaller than JPG at the same visual quality and supports transparency, and every current browser displays it; quality 80–85 is the usual sweet spot. Convert WebP back to JPG or PNG when a portal, form or older application rejects it — JPG for photos, PNG where transparency must be kept.
Who this is for: Website owners, designers and anyone who needs smaller images for the web — or a JPG/PNG copy of a WebP that a form or app will not accept.
Why WebP, and when to convert back
- WebP (Google, 2010) compresses photos about 25–35% smaller than JPG at the same visual quality and supports transparency like PNG at a fraction of the size. Every current browser displays it, and Google's PageSpeed flags JPG/PNG images as "serve images in next-gen formats" — which is why site owners convert.
- Quality: WebP at 80–85 is the usual sweet spot; below 60 you will see smoothing in skin and gradients. PNG → WebP of logos and screenshots keeps sharp edges even at 80.
- Convert WebP back to JPG or PNG when a system rejects it — most government portals, job boards, visa forms, Microsoft Office before 2020, older printers and WhatsApp Web uploads accept only JPG/PNG. Choose PNG if the image has transparency; JPG otherwise (transparency is flattened on white).
- Resize on the way: a 4000-px phone photo is rarely needed on the web; 1920 px for full-width images and 1200 px for content images are common targets.
Conversion uses the browser's built-in canvas encoder, so quality and size match what Chrome itself would produce. Metadata (EXIF, GPS location) is removed in the process — usually a privacy benefit.
See also: HEIC to JPG Converter.
Assumptions
- Decoding and encoding use the browser's canvas; WebP encoding needs Chrome, Edge, Firefox or Safari 17+.
- JPG output is flattened on white; PNG output is lossless; optional resize scales the longest side.
- EXIF and other metadata are not carried over; up to 20 files per batch, processed on the device.
Worked example
Converted to WebP at quality 82 with the longest side resized to 1920 px → about 210 KB at 1920 × 1440, visually identical on screen — a 93% reduction, most of it from the resize. The same conversion without resizing gives roughly 1.9 MB (−40%).
Frequently asked questions
Does converting to WebP lose quality?
WebP is lossy like JPG, but at quality 80+ the difference is not visible at normal viewing sizes. Converting a JPG to WebP cannot improve it; it re-encodes what is there.
Why is my WebP bigger than the JPG?
Very small or already heavily compressed JPGs sometimes grow slightly; try quality 75, or keep the original — there is no gain in converting a file under 30 KB.
Can I convert WebP to JPG on iPhone?
Yes — this page works in Safari for WebP → JPG/PNG. WebP encoding in Safari needs iOS 17 or later.
Is there a file size limit?
Only your device's memory; up to 20 files at a time, and very large images (over about 50 megapixels) may fail on phones.
How do I convert JPG to WebP for free?
Choose the files above, set quality (82 is a good default) and click Convert — the WebP files are created in your browser and downloaded; nothing is uploaded.
Which is better, WebP or JPG?
WebP for the web: smaller files and transparency support. JPG for compatibility with forms, portals, printers and older software.
Related calculators
Found an error? Report it — tell us the inputs, the result you got, what you expected and the rule or source. Confirmed corrections are published within a week.
Ready to build your next digital solution?
Send the brief and you get a scoped response with approach, milestones and a fixed price range. Not a sales call.
A 30-minute call with the engineer who would run your project
Within 2 business daysA written scope: approach, module breakdown, milestones, fixed price range
Within 5 business daysYou decide. No retainer, no obligation, and the scope document is yours to keep either way
Your timelineSend your brief
Three fields to start. Add project details if you have them.