How to Reduce Image File Size Without Losing Quality

To reduce image file size without visibly losing quality, first resize the image to the largest size it will actually be shown at, then save it in a suitable format (JPG or WebP for photos, PNG or WebP for graphics) at a moderate quality setting, and strip the metadata. Resizing does most of the work: in our tests, scaling sample photos to 1920 pixels wide cut them by 56% to 74% before any other change. A free in-browser tool such as our image compressor does all of these steps in one go.

Why image files get so big

Three things decide how big an image file is:

• Pixel count. A modern phone photo can be 4000 pixels or more across. Every pixel has to be stored, so doubling the width and height roughly quadruples the data.
• Format and compression. The same picture can be a few hundred kilobytes as a JPEG or several megabytes as a PNG. Formats compress in different ways, and some compress much better than others for a given kind of image.
• Detail and noise. Busy scenes (foliage, gravel, crowds) and grainy low-light photos are harder to compress than clear skies and flat colours.

Extra data such as camera metadata and colour profiles adds a little on top. The good news is that most images are far bigger than they need to be for screens, so you can usually shrink them a lot with no visible change.

How much each step saves

We ran sample photos through our own upload pipeline (sharp/libvips) with different settings. These are measurements on our sample files, not promises for every image, but the pattern is consistent:

Resizing beat every quality and format change on its own. Combining a sensible size with a modern format gave the smallest files.

1. Resize to the size you need

This is the single most effective step. If a photo will be viewed on a phone, in a chat window, in an email or in a blog post, it never needs the full resolution your camera captured.

Useful sizes for the longest side:

• 1920 px: fills a typical laptop or desktop screen. A safe choice for photos people may open full-screen.
• 1280 px: plenty for images inside articles, emails and forum posts.
• 800 px: thumbnails, small inline images, product photos in narrow layouts.

Keep the original. Resizing down is permanent for that copy, and you may want the full-resolution version for printing or cropping later.

Resizing also helps with the quality trade-off. A smaller image at quality 80 usually looks better at a given file size than a huge image squeezed down to a very low quality setting.

2. Choose the right format

The wrong format can make a file many times larger than it needs to be:

• Photos: JPG or WebP. Saving a photo as PNG keeps every pixel of noise losslessly and produces a big file.
• Screenshots, logos, diagrams: PNG or WebP. JPEG blurs text and sharp edges.
• Animations: animated WebP or a short video rather than GIF.

Our sample screenshot (1366 × 900) shows how much format matters for graphics: 2.3 MB as the original PNG, 712 KB re-saved as an optimised PNG with identical pixels, and 126 KB as WebP at quality 80. Our guide to image file formats explains when to use each one.

3. Lower quality a little

JPEG and WebP have a quality setting, usually on a scale of 0 to 100. The relationship between quality and size is not linear: the top few points cost a lot of bytes and add little that anyone can see.

In the table above, dropping from quality 80 to 68 roughly tripled the saving on both photos. Whether that is acceptable depends on the picture. Check the result at the size people will see it, and watch smooth areas such as skies and skin for blockiness or banding. If you see it, go back up a step.

A practical approach:

1. Start at a quality around 80.
2. Compare with the original at 100% zoom on the parts that matter.
3. Lower the quality step by step until you notice a difference, then go back one step.

Lossy compression discards detail permanently, so always work from the original. Our explainer on lossy vs lossless compression covers why repeated re-saving degrades images.

4. Strip metadata

Photos from phones and cameras carry metadata: camera model, date and time, settings and often GPS location. It is usually small compared with the image data itself, so the main reason to remove it is privacy rather than size. Still, there is no reason to ship it with every copy you share.

Most compression tools remove metadata when they re-encode. Every upload to PictureToLink has all metadata discarded, and the image is rotated the right way up first so it does not end up sideways. To strip metadata and keep the file on your device, use our EXIF remover.

5. Use WebP or AVIF where supported

WebP and AVIF are newer formats that usually produce smaller files than JPEG and PNG. The MDN image format guide recommends preferring them for raster images on websites, with a JPEG or PNG fallback where older browsers matter.

Where they make sense:

• Your own website or blog: yes, ideally WebP or AVIF with a fallback.
• Sharing by link: WebP works in all current major browsers.
• Email attachments, online forms, printing: stick with JPG, because many apps and form validators still expect it.

The saving varies with the image. In our tests, WebP at quality 80 was 48.1% smaller than the original JPEG for one photo but only 13.9% smaller for another. Screenshots gained the most.