Photo export guide
JPG vs WebP for Photos: Which Should You Export?
JPG and WebP can both make good photo derivatives. The deciding question is not a codec slogan but who will open the file next, and whether you have measured the result on your own image.
One-line answer
- Use WebP when you control every app that will open the file and size matters.
- Use JPG when a form, print shop, older app or unknown recipient enters the workflow.
- Both are lossy photo exports; keep the editor's original as the master.
The two contenders
JPEG is old, broadly supported, lossy and has no transparency. WebP is newer, supports lossy and lossless modes plus alpha, and is designed to deliver similar visual quality in fewer bytes. For photographs, compare at matched visual quality rather than trusting equal slider numbers.
Quality behaviour
JPEG around 75–85 is a practical sharing range; below roughly 60, blocking and banding become easier to see around edges and gradients. WebP has a similar quality-size trade-off, but its numeric quality value is not directly comparable to JPEG's. Encode both, inspect the same detailed area at 100%, and use the measured output size.
Google's published WebP study reports broad codec-level savings, but this page does not present that percentage as a FitMyPic measurement. Subject matter, dimensions, encoder and quality-matching method move the result.
What we can measure here
The current FitMyPic corpus publishes JPEG quality measurements, but it does not contain a matched JPEG/WebP visual-quality sweep for the four photo categories in the draft. We therefore remove the draft's unmeasured portrait/landscape/ISO table rather than inventing values. The reliable conclusion is qualitative: WebP often produces a smaller file at comparable appearance, while JPG remains the safer interchange format.
For a measured target-size workflow, use the FitMyPic compressor; for the published JPEG curve, see the JPEG quality benchmark.
Compatibility is the tiebreaker
| Destination | Safer choice | Why |
|---|---|---|
| Modern browser you control | Either | Current browsers generally render both |
| Online form or portal | JPG | Whitelists commonly name JPG/PNG |
| Screenshot, text or transparency | PNG | Lossless pixels and alpha matter |
| Print workflow | Ask first; usually JPG/TIFF/PDF | Acceptance depends on the shop |
| Unknown recipient or older app | JPG | Fewer decoder surprises |
For a deeper compatibility discussion, read PNGToolbox's WebP compatibility guide. Its Microsoft 365 section deliberately avoids an unsupported version claim because an official source could not be verified on 2026-11-07.
Editing and re-saving
Both lossy JPEG and lossy WebP lose information each time they are re-encoded. Keep the editor's native project or a lossless master, then export once at the end. Neither JPG nor WebP is a good working format for a photo you expect to edit repeatedly.
How to choose
FAQ
Is WebP quality really the same as JPEG?
At visually matched settings, ordinary photos can look equally good, but no universal slider mapping exists. Compare the preview and measured size for your image.
How much smaller is WebP?
The answer varies by content and encoder. This repository's current benchmark does not contain the matched-quality photo sweep needed for a defensible percentage, so this guide does not publish one.
Should I convert my whole library?
Only if storage pressure is real and you retain originals. Check that every future recipient or app can open WebP before replacing a broadly supported derivative.
Why did a form reject my WebP?
The form likely enforces a JPG/PNG whitelist. Convert locally and retry; the form rejection checklist covers the other checks.