The reason for shrinking an image is almost always imposed from outside: a 2 MB upload cap, a page that needs to load faster, an attachment limit. So the requirement is not "somewhat smaller" but "under this specific number" — without visibly wrecking the picture.
OFFiler offers both directions: set a quality level, or set a target size and let the tool find the quality that hits it. You can compare before and after with a slider, and everything runs in your browser. Below: why the mechanism differs per format, why EXIF disappears as a side effect, and how to process a whole folder at once.
The mechanism differs by format
JPEG and WebP are re-encoded at a chosen quality
JPEG and WebP are lossy formats — they are built around discarding information. Compression redraws the image onto a canvas and re-encodes it in the same format at the quality you choose. Around quality 70 is the region where photographs lose a lot of weight without visibly losing anything.
Pixel dimensions are unchanged, so the image occupies the same space on screen. When a picture simply has far more pixels than it will ever be displayed at, resizing removes far more bytes per unit of visible quality than lowering the quality does.
PNG is shrunk by reducing its palette
PNG is lossless, so "lower the quality" is not an available operation. Instead the tool builds a palette of representative colours and maps every pixel to the nearest one. You can choose 64, 128, or 256 colours.
This works remarkably well on screenshots, logos, illustrations, and diagrams — images built from a limited set of colours shrink dramatically with no visible change. On smooth gradients or photographs stored as PNG, it can produce visible banding; in that case, convert to JPEG or WebP rather than fighting to keep PNG.
Target-size mode searches for the quality
When the constraint is a hard ceiling like "under 2 MB", set a target size in kilobytes instead. The tool searches for a quality level that lands under it, so you are not nudging a slider and re-checking the file size by hand. For upload limits, this is the reliable path.
Side effects and limits
Compression strips EXIF
Because compression redraws through a canvas, the original EXIF — capture time, camera model, GPS coordinates — does not survive into the output. If dropping location data is all you wanted, that is enough on its own; if you did not want to compress, use the EXIF remover instead. Equally, be aware that compressing a photo whose capture date you wanted to keep will discard it.
ICC colour profiles are dropped for the same reason, so images authored in a wide colour space can shift slightly in appearance.
JPEG, PNG, and WebP only
The tool compresses JPEG, PNG, and WebP. Formats the browser cannot decode directly, such as HEIC, need converting to JPEG first. Files are handled up to 50 MB each.
Batches and chaining
Compress a whole folder in one pass
Drop in many images and they are compressed in sequence with identical settings, then returned as one ZIP. Preparing a batch of blog photos or a folder of screenshots becomes a single operation, and since the ZIP is assembled in the browser, nothing leaves your device no matter how many files you add.
Compress before building a PDF
When images are combined into a PDF, they are stored without re-compression — so the PDF weighs whatever the images weighed. Compressing first and then handing the results to image-to-PDF produces a submittable file in one pass.
Specs and limits
- Input formats
- JPEG, PNG, WebP
- Size limit
- 50 MB per file
- JPEG / WebP
- Re-encoded at the chosen quality; pixel size unchanged
- PNG
- Palette reduced to 64 / 128 / 256 colours
- Target size
- Specify KB and the quality is found automatically
- Discarded
- EXIF, ICC colour profile
- Batch
- Multiple images supported; output as ZIP
- Network
- No file upload; all processing in-browser