Image Compressor & Resizer

Shrink photos to a file size you choose, resize them, or convert HEIC, PNG and JPG to WebP, AVIF or JPG. Work on several at once and compare the result with the original before you download.

Output format

JPEG stays JPEG, PNG stays PNG. HEIC becomes JPEG, because browsers cannot write HEIC.

Compression
75

Applies to JPEG, WebP and AVIF output. Left alone, each format uses its own default (75, or 50 for AVIF). Most photos look the same down to about 60.

Keeps the proportions and never enlarges: a smaller image stays its own size.

JPEG, PNG, WebP, GIF, AVIF, BMP or HEIC, up to 100 MB each. Your images stay on your device. The compressed copies carry no location or camera details.

Runs entirely in your browser. Nothing you type or upload is sent to a server.

How image compression works

A photo straight from a phone is millions of pixels, each with a red, green and blue value. Stored raw, a 12 megapixel picture would take about 36 MB. Image formats shrink that in one of two ways. Lossless formats such as PNG find patterns and store them more compactly, so every pixel comes back exactly; that works well for screenshots and logos with large flat areas, and poorly for photos, where neighbouring pixels are rarely identical. Lossy formats such as JPEG, WebP and AVIF throw away detail the eye is unlikely to miss, which is how a 36 MB photo becomes a 3 MB file that looks the same.

JPEG, the oldest of the three, shows the idea clearly. It first stores color at half the resolution of brightness, because the eye is far more sensitive to light and dark than to hue. It then cuts the picture into 8 × 8 pixel blocks and describes each block as a mix of simple wave patterns, from smooth gradients to fine stripes. The quality setting controls how coarsely those patterns are rounded off. At high quality the fine stripes survive; at low quality they are rounded to nothing, and the blocks begin to show as visible squares, with halos around sharp edges and bands in smooth skies. WebP and AVIF use more flexible block sizes and better prediction from neighbouring blocks, which is why they reach the same look in fewer bytes.

Which format to choose

FormatBest forTransparencySize against JPEG
JPEGPhotos that must open anywhere: email, forms, printingNoBaseline
WebPPhotos and graphics for websitesYesAbout 25 to 35 percent smaller
AVIFThe smallest files, when the receiver supports itYesOften around half
PNGScreenshots, logos, diagrams, anything with textYesLarger for photos, smaller for flat graphics

The encoders here are the ones Google’s Squoosh app uses: MozJPEG, which squeezes more out of JPEG than most cameras and editors do, libwebp, libavif with the AV1 codec, and OxiPNG, which rewrites a PNG as small as it can go without changing a pixel.

Dimensions matter more than quality

File size grows with the number of pixels, so resizing is the strongest lever there is. A phone photo of 4032 × 3024 pixels holds 12.2 million of them. Resized to 1920 pixels on its longest side it holds 2.8 million, less than a quarter, and the file shrinks by roughly the same factor before quality is touched at all. A typical laptop screen is under 2000 pixels wide and a phone screen is narrower, so for anything that will be looked at on a screen, 1600 to 2560 pixels on the long side is plenty. Keep the full size only for printing or for cropping later.

Hitting a target file size

Job portals, visa applications and school forms often set a hard limit such as 200 KB. In target mode the tool encodes the image at its everyday quality, checks the size, then narrows in on the highest quality that fits, usually in three to five attempts. If even the lowest quality is too big, or the only fit is a blurry one, it says so and offers to reduce the dimensions instead, which almost always looks better than a heavily compressed full-size image. Forms disagree about whether a kilobyte is 1,000 or 1,024 bytes, so the tool uses 1,000, the stricter reading.

What re-compressing changes

  • Metadata is not carried over. The new file is built from pixels, so GPS location, camera details and dates are gone. To remove those without re-compressing, use the Photo Metadata Remover.
  • Colors are converted to sRGB. Recent phones shoot in the wider Display P3 color space. The browser converts to standard sRGB when it draws the image, so the most saturated reds and greens can look very slightly flatter.
  • Animation is lost. Animated GIF, WebP and PNG files keep only their first frame.
  • Quality loss adds up. Each lossy save discards a little more. Compress from the original file, not from a copy that was already compressed.

HEIC, the iPhone’s default format, is efficient but awkward to share, because many websites and Windows apps cannot open it. Converting to JPEG fixes that for good. If your scans are already PDFs, the PDF Merge & Split tool combines them into one document, also in your browser. To embed a small image directly in HTML or CSS, compress it here first, then turn it into a data URI with the Base64 converter.

Frequently Asked Questions

No. The images are decoded, resized and compressed inside your browser, using compression engines that are downloaded to the page as WebAssembly. Nothing you choose is sent to a server.
For JPEG and WebP, 75 is a good default and most photos look identical to the eye down to about 60. Below 40, blocks and color smudges start to appear, first in smooth areas like skies and skin. AVIF uses a different scale: 50 is already high quality, and trouble starts below about 30. Use the Compare view at actual size to judge your own photo.
The original was already compressed at a lower quality than the one you chose, so re-encoding it spends more bytes, not fewer. It also happens when a photo is saved as PNG, which is lossless and much larger for photographs. Choose a lower quality, a smaller size, or WebP or AVIF instead. The tool marks every file that came out larger so you can keep the original.
Choose JPEG as the output format, or leave it on Same as original, which turns HEIC into JPEG because browsers cannot write HEIC. Then drop the photos in. In Safari the browser decodes HEIC itself; in Chrome, Edge and Firefox the tool loads a HEIC decoder the first time it needs one. Photos come out upright, at the quality you set.
Choose Aim for a file size and type the limit. For a 12 megapixel phone photo, a small target usually needs fewer pixels as well as lower quality, so also set Resize to a longest side of 1600 or 1200 pixels, or tick the option to reduce the dimensions instead of dropping to a low quality. The tool reads 1 KB as 1,000 bytes, so its result passes both kinds of size check forms use.
Both are smaller than JPEG at the same visual quality: WebP by roughly a quarter to a third, AVIF often by half. Every current browser displays both, and so do recent versions of Windows, macOS, iOS and Android. Some upload forms, older photo apps and print services still accept only JPEG or PNG, so use JPEG when you do not know what will receive the file.
Yes. The compressed copy is built from the pixels alone, so GPS coordinates, the camera model, the date taken and other EXIF details are not carried over. If you want to keep the original quality and only remove the metadata, use the Photo Metadata Remover, which strips it without re-compressing.
AVIF compresses by searching many ways to predict each block of the picture, which is what makes its files small and its encoding slow. In a browser the encoder runs on a single processor core, so a full-size phone photo can take several seconds, and aiming for a file size multiplies that by the number of attempts. Resizing first speeds it up a lot.
The Internet Omni-Tool