Choose between JPEG, PNG and WebP for your next export
Published and reviewed · Based on the current LocalShift implementation
Choose the format based on the receiving application and the image's needs. JPEG is useful for opaque photographic content, PNG for lossless decoded pixels and transparency, and WebP for compatible workflows that benefit from its encoding options.
Start with the destination
An upload form that accepts only JPG determines your output choice even if another format could be smaller. If you control a website, you can compare file variants and check the browsers your audience uses.
Changing a filename extension is not conversion. The bytes inside a file must be encoded in the format that the extension claims.
Compare the tradeoffs
LocalShift's PNG export is lossless for the decoded pixels. JPEG and WebP quality controls are encoder settings; the 100% option does not promise lossless WebP or an identical copy.
The tools support still images. Animated WebP and PNG inputs are rejected instead of being silently turned into one frame.
| Format | Transparency | What to check |
|---|---|---|
| JPEG | No | Lossy artifacts around text and edges; selected background |
| PNG | Yes | File size for photographs; no recovery of earlier lossy detail |
| WebP | Yes | Destination support; selected quality and browser output |
Compare a real output, not a generic percentage
Convert a copy, then compare the downloaded file size and inspect it at its actual display size. Text, gradients, photographic noise and transparent edges can respond differently to encoding.
No universal size reduction applies to every image. A small JPEG might get larger as PNG; a WebP result may not beat an already optimized JPEG. Keep the version that meets your quality and compatibility needs.
Retain an original for editing
Repeated lossy re-encoding can change image detail. Keep the highest-quality source and derive delivery formats from it rather than repeatedly converting delivery files.
These image tools preserve dimensions by default and also support resizing and rotation. Check the final pixel dimensions if your destination has a width or height requirement. Images are limited to 20 MB and 24 million pixels each.
References
General format references; LocalShift-specific behavior is documented and tested separately.