Re-encode a JPEG or WebP in this tab so a phone photo usually gets smaller. EXIF is stripped as a side effect. Already-tiny PNG icons often barely shrink, and there is no exact 100 KB promise.
A job portal rejected the headshot, or the CMS said the hero image is too heavy. That is the job: make a photo fewer bytes without handing the camera roll to an upload compressor.
This page re-encodes JPEG and WebP in the current tab with a quality slider. It is not lossless “smart compression,” not a CDN, and not a promise that the picture will look identical at 80% smaller. Phone photos usually drop a lot. A 24 KB UI icon usually does not.
When re-encoding actually helps
- A 4–12 MB iPhone or Pixel JPEG that a form, WordPress media library, or email still treats as “too large.”
- Product shots you will not drop on a site that uploads every file, even if they advertise a one-hour delete.
- Web pages where you want a smaller JPEG/WebP in the same format, not a new extension.
It is the wrong first tool if the form asked for 1920 px wide — that is pixels, not kilobytes. Use image resizer first, then come back. If the file is HEIC, convert HEIC to JPG before you compress.
How to use it
- Drop a JPEG, PNG, WebP, or GIF from this device. Renaming the extension does nothing.
- Move the quality slider. Lower quality usually means a smaller file and softer edges.
- Compare the new size. Process in this tab, then download.
Typical ceiling is about 32 MB. Compressing the same file twice rarely helps and often just adds more JPEG generation loss.
Limits worth reading
- We do not guarantee 100 KB, 200 KB, or “no visible difference.”
- GIF animation is not a serious compression path here; frames can flatten depending on how the browser decodes it.
- For WebP/PNG as a format change, use image format converter.
- A PDF full of scans belongs on compress PDF, not this page.
This is a local utility, not prepress or a page-speed audit.