Image Converter, Resizer & Compressor
- No Sign-up
- 100% Free
- Zero Server Data
Convert between WebP, JPEG and PNG, set a maximum width or height, and choose a quality. The picture is decoded, resized and re-encoded by your own browser, so it never leaves your machine. This matters more here than with text, because a photograph carries a date, a camera and often a location.
JPEG has no transparency. The background will become white.
Drag the divider to compare. The left is the original, the right is the result. Move the quality slider and the right side updates as you go.
Which format for which picture
| Format | Best for | Transparency | Size vs JPEG |
|---|---|---|---|
| WebP | Almost anything on the web | Yes | 25-35% smaller |
| JPEG | Photographs, and anything old that has to read it | No | baseline |
| PNG | Logos, screenshots, diagrams: sharp edges | Yes | far larger for photos |
The split is not about quality, it is about what each format was built to compress. JPEG and WebP throw away detail the eye is bad at noticing, which works beautifully on a photograph and badly on a line drawing: a hard black edge on white comes back with a grey smudge around it. PNG keeps every pixel exactly, which is right for that logo and enormous for a beach.
What re-encoding costs you
Every pass through a lossy format discards detail permanently. Opening a JPEG and saving it again at the same quality does not preserve the image, it degrades it slightly. The loss compounds, and no later step recovers it.
- Work from the original where you have it, rather than from a copy that has already been through a chat app.
- Resize once, to the size you actually need. Resizing down and then back up is the most expensive way to soften an image.
- PNG survives repeated saves because it is lossless. That is the one thing it is unambiguously better at.
This tool always works from the file you chose, never from its own previous output, so changing the quality after a conversion re-encodes the original rather than compounding.
The metadata goes too
Re-encoding through a canvas keeps only the pixels. The EXIF block (camera model, lens, exposure, the timestamp and, on a phone, often the GPS coordinates) does not survive.
That cuts both ways and is worth stating plainly rather than selling as a feature. It is genuinely useful before posting a picture publicly, because a holiday photo can carry a home address. It is a loss if you were keeping a photo library organised by capture date, and there is no way to get it back afterwards.
Frequently asked questions
Is my photo uploaded anywhere?
No. Your browser decodes the file, draws it to a canvas and encodes it again, all locally. The site’s security policy sets connect-src ‘none’, so the browser blocks network requests from these pages, meaning a photo could not be sent even if the code tried.
Which format should I pick?
WebP for almost anything on the web: it is usually 25 to 35% smaller than JPEG at the same quality and it keeps transparency. JPEG when something old has to read it. PNG only for images with sharp edges (logos, screenshots, diagrams) where JPEG leaves smudges around the lines.
Why did the file get bigger?
Usually because the source was already compressed harder than the settings you chose, or because a photograph was saved as PNG, which does not compress photographs well. The change is reported either way, including when it is negative.
Does it remove EXIF data?
Yes, as a side effect. Re-encoding through a canvas keeps only the pixels, so the camera model, the timestamp and any GPS coordinates are dropped. That is worth knowing in both directions: it is good for a photo you are about to post, and it is a loss if you wanted the metadata kept.