Skip to content
PicBulk
TR EN

Lossless Image Compression

Lossless compression does not re-encode your image: pixels stay bit-for-bit identical and only unnecessary data (EXIF, comments, inefficient tables) is removed. Typical savings are about 5–12% for photo JPGs, 10–50% for PNG and 20–60% for SVG; already lossy WebP and AVIF files usually cannot be shrunk this way.

Files are never uploaded

Drag your images or folders here

WEBP, PNG, JPG, AVIF, GIF, BMP, SVG, ICO · Ctrl+V to paste from the clipboard

Drop, choose or paste files above to get started.

You can set a separate format, quality and size for each file.

What does lossless compression mean?

“Shrinking without quality loss” can mean two different things. With lossless methods the image data is not changed; the same pixels are written more efficiently or redundant data is dropped, so the result looks identical to the original. With lossy methods (such as setting JPG quality to 80) some detail is deliberately sacrificed; the savings are much larger but the image is no longer identical.

What happens to each format, and what to expect

FormatMethodTypical saving
PNGFilters and deflate are re-optimised (oxipng); unnecessary embedded chunks are removed.10–50%
JPGThe image is not re-encoded; only the Huffman tables are optimised and EXIF/GPS, comments and thumbnails are removed. Orientation and colour profile are kept.5–12%
WebPLossless WebP is re-encoded with more effort and checked pixel by pixel; for lossy WebP only EXIF/XMP chunks are removed.5–15% for lossless, very little for lossy
AVIFOnly lossless (identity-matrix) AVIF files are re-encoded and verified; lossy AVIF is left untouched.Mostly none
SVGComments, editor metadata (Inkscape etc.), whitespace and unused namespaces are removed; the drawing is unchanged.20–60%

Why WebP and AVIF often cannot be shrunk

These two formats usually arrive already lossy. Rewriting a lossy file “losslessly” does not shrink it, it normally makes it bigger: the lost detail does not come back, yet the encoder now tries to store every resulting pixel exactly. In that case this tool leaves your file alone and tells you so. If you need a smaller file, pick the “Original” format and lower the quality, or use compress to a target KB; those methods accept a small quality loss.

Safety: is the result really identical?

Every re-encoded file (JPG, WebP, AVIF) is opened in your browser and compared pixel by pixel with the original. If anything differs, or if no saving is possible, the original file is returned unchanged. So the output is never larger than the input.

Good to know

Frequently asked questions

Does lossless compression really not affect quality?
Correct. The image data is not changed; for JPG, WebP and AVIF the result is verified against the original pixel by pixel in your browser.
Why did my file not get smaller?
Most likely it is already well optimised (for example a JPG saved with mozjpeg) or a lossy WebP/AVIF. Lossless methods cannot shrink such files; you would need to lower the quality.
How much can I save on a JPG?
Usually 5–12% for photo JPGs. A big reduction (say, half) is only possible with lossy methods: lowering quality or resizing.
Does it optimise progressive JPGs?
For progressive JPGs only embedded metadata is removed; they are usually already optimised, so the saving is small.
Are my files uploaded?
No, everything is processed in your browser.

Other converters

Guides

Last updated: