How to reduce image file size comes down to two moves: re-encode the image at a lower quality, and shrink its pixel dimensions if it is headed somewhere with a display width smaller than the original. A phone photo saved at quality 80 typically drops 60 to 80 percent with nothing you can see. Drop it into the compressor, pull the quality slider if you need it smaller, and download.
Most images are two to four times larger than they need to be, and that is not your fault. A camera does not know whether the photo will be printed at poster size or attached to an email, so it saves at a quality far above what any screen shows. Reducing the file size undoes that one decision, and every method below, in the browser, on your phone, on your desktop, in the command line, is really just a way to shrink image file size without throwing away what actually matters in the picture. This guide covers all of them, in the order that saves you the most, as part of our complete guide to compressing an image.
Three moves cover almost every situation: change the quality setting, change the pixel dimensions, or change the format entirely. Our compressor handles the first and third, quality and format, right in your browser. The second, resizing, lives in your OS or an editor for now, and the sections below cover all three.
| Method | What it changes | Where you do it |
|---|---|---|
| Quality slider | Re-encodes pixel data at a lower setting | This compressor |
| Resize dimensions | Removes pixels outright | Your OS or an editor |
| Switch format | Uses a more efficient codec, WebP or AVIF | This compressor |
Why is your image file so large?
A 4.5 megabyte phone photo is large for two independent reasons, and only one of them is really about the picture. The pixel count is the first: a typical phone shoots around 12 megapixels, four thousand by three thousand pixels, and every one of those twelve million pixels needs data. The quality setting is the second: a camera has no idea whether you will print the photo at poster size or send it in a text message, so it saves at a quality far above what a phone or laptop screen actually shows.
Metadata adds a smaller but real third piece. Every photo carries EXIF data, the hidden information a camera writes into the file describing the shot: GPS coordinates, camera model, lens, and exposure settings, often with a small embedded thumbnail. That block alone can run 200 kilobytes or more on a smartphone photo (DigitalOcean). On a 4.5 megabyte file, 200 kilobytes is a little over 4 percent, gone before a single visible pixel is touched, which is why stripping metadata is close to a free win.
The other 96 percent, the roughly 4.3 megabytes left, is pixel data saved at a quality level built for a use case, printing, that most images never see. That is the part our quality slider and the OS-native resize methods below both go after, and between the two of them they account for nearly all of what makes the file the size it is.
How to reduce image file size in your browser
The fastest method is to re-encode the image at quality 80, which cuts most photos roughly in half with nothing you can see. If you just need to reduce image size right now, this is the whole process.
- Open the free image compressor and drop your image on it. Nothing installs, and the file is processed in the browser.
- Leave the quality at 80 to start. Look at the after size shown on the card. For most photos that alone clears the limit.
- If you need it smaller, pull the quality slider down and watch the after size drop. At 60 the file roughly halves again and most photos still look fine. Below about 50 you start to see softness in skies and skin.
- Download the result. The original is untouched, and your uploaded file is deleted within the hour.
A phone photo straight off the camera typically comes back 60 to 80 percent smaller, so a 4.5 megabyte photo lands around 900 kilobytes, and five of them now fit in one email with room to spare.
How to reduce photo file size on your phone or computer
Every phone and desktop OS has a built-in way to shrink a photo's dimensions, which is the resize half of the two-lever split above. None of them offer a true quality slider the way a dedicated compressor does, so treat these as the resize step, then compress afterward if bytes still matter.
| Device | Built-in method | What it does |
|---|---|---|
| iPhone or iPad | Settings, Camera, Formats, High Efficiency | Saves future photos smaller by default |
| Android | Gallery app edit, crop or resize option | Removes pixels from the copy you save |
| Windows | Photos app, the three-dot menu, Resize image | Writes a smaller copy at a chosen dimension |
| Mac | Preview, Tools, Adjust Size | Resamples the image to fewer pixels |
On an iPhone or iPad
Go to Settings, Camera, Formats, and choose High Efficiency to save future photos as HEIC instead of full-size JPEG, smaller by default with no visible difference. For a photo you already have, the Mail app offers a smaller image size option in the attachment menu when you go to send it, which resizes the copy that actually gets attached without touching the original in your camera roll.
On Android
Open the photo in your phone's Gallery app, tap the edit icon, and use the crop or resize option to save a smaller copy. When sending through Gmail, the attachment menu offers a smaller image size option before you hit send, which downsizes the attached copy the same way the iPhone's Mail option does.
On Windows
Open the photo in the Photos app, click the three dots in the top menu, choose Resize image, and pick a smaller preset like Medium or Small, or set a custom width. Photos writes a new file at that size and leaves the original alone.
On a Mac
Open the photo in Preview, click Tools, then Adjust Size, and lower the width and height, or pick a smaller preset from the dropdown. Preview shows the new pixel dimensions as you adjust and resamples the image when you export it.
How to reduce file size in Word or PowerPoint
Office documents balloon in size because Word and PowerPoint embed images at their original resolution and quality by default, even when the image displays at a fraction of that size on the page.
In either app, click an image to select it, open the Picture Format tab, and choose Compress Pictures. Pick a target resolution, Web is usually plenty for anything not being printed, and choose whether to apply the change to just the selected image or every picture in the document. Compress Pictures re-samples every embedded photo down to that resolution in one pass, often cutting a document with a dozen photos from tens of megabytes to a few.
This is a resize operation dressed up as a compression setting, the same resize lever covered above, just scoped to what is already inside the file rather than a photo on its own.
Compression and resizing are two different fixes
Compression re-encodes the image at a lower quality, throwing away detail your eye is unlikely to miss. Resizing removes pixels by making the image physically smaller. They solve different halves of the same problem, and the fastest way to make an image file smaller without hunting through settings is still the browser tool covered above: quality 80, download, done.
But the biggest saving on most web images is resizing, and almost nobody does it. Serving a desktop-sized image to a page that displays it at a fraction of that width can waste two to four times the data actually needed (web.dev). If your page displays an image 800 pixels wide, a 4000-pixel-wide photo is carrying five times the pixels it will ever show. Resize it to 1600 pixels first, using your OS's resize tool from the section above, plenty for a high-resolution screen, and then compress it here. Compression alone cannot fix pixels the page never displays.
For anything that is not a web page, an email attachment, a form upload, a scanned document, leave the dimensions alone and just compress. Those destinations care about bytes and megabyte limits, not display width, so compression is the whole job.
How small can you go before it looks bad
Quality 80 is visually lossless for photographs, and quality 60 is where most people should stop when they need more. Independent testing at web.dev found that dropping a sample JPEG to quality 60 cut its file size by 79 percent, with the difference invisible at normal viewing size (web.dev). It is below about 50 that a JPEG starts to show its hand, with blocking in flat areas like a clear sky and softness on skin, because JPEG compresses in 8 by 8 pixel blocks and low settings make the block edges visible.
| Quality | What you get | Use it when |
|---|---|---|
| 80 (default) | Visually lossless, about half the size | Almost always |
| 60 | Roughly half again, still hard to tell | You need to clear a tight limit |
| Below 50 | Visible blocking and softness | Rarely, only for a small thumbnail |
The same photo used throughout this guide makes the point in bytes rather than words.
| Version | File size |
|---|---|
| Original | 4.5 MB |
| Quality 80 | 0.9 MB |
| Quality 60 | 0.47 MB |
If you need to hit an exact number instead of eyeballing it, move the slider and watch the after size rather than guessing at a quality value; both sizes are shown for every file, so you can stop at the smallest one that still looks right.
Switch to a smaller format: WebP and AVIF
Changing format is the third lever, and it stacks with the other two rather than replacing them. Lossy WebP images run 25 to 35 percent smaller than a JPEG at similar visual quality, and lossless WebP is typically 26 percent smaller than the equivalent PNG (MDN). AVIF goes further still, often saving more than 50 percent versus JPEG, though it takes longer to encode and the exact savings depend on the image and the settings used (web.dev).
| Format | Typical size vs JPEG | Lossy or lossless |
|---|---|---|
| WebP | 25 to 35% smaller | Both, your choice |
| AVIF | Often 50%+ smaller | Both, your choice |
| PNG | Larger for photos | Lossless only |
Our compressor writes WebP and AVIF as an output option alongside JPEG and PNG, so switching format costs nothing extra, one dropdown instead of a separate conversion step. PNG remains the right call for anything that is not a photograph, a logo, a screenshot, or line art, since lossy compression smears the sharp edges those images depend on.
Browser support is the one catch. Older browsers, some image editors, and plenty of internal tools still expect a JPEG or a PNG, so if the image needs to work everywhere, including inside an email client or an aging CMS, keep a JPEG copy around rather than only ever exporting WebP or AVIF. A modern web page can serve the smaller format to browsers that support it and fall back to JPEG for the rest with a handful of markup, which is exactly what our compressor's format dropdown makes easy to produce on your end: export the same photo as WebP and JPEG in two clicks and keep both on hand.
Which lever saves the most, ranked
Not every lever pulls the same weight, and doing them in the wrong order wastes time. Ranked by typical impact on a phone photo, based on the numbers above:
- Resizing to display width, when the image is going on a web page, cuts two to four times the data of an oversized original, and it is the one step most people skip entirely.
- Dropping quality from the camera's default to 80 recovers most of the rest: 60 to 80 percent smaller with nothing visible at normal size.
- Switching format from JPEG to WebP or AVIF adds another 25 to 50-plus percent on top of whatever quality setting you land on.
- Stripping metadata is the smallest lever on its own, worth roughly 4 percent on a typical phone photo, but it costs nothing and our compressor does it automatically on every file.
For an image headed to a web page, do all four in the order above. For an email attachment or a form upload, skip the resize step, since display width does not apply, and go straight to quality and, if the destination allows it, format.
A worked example: 4.5 MB down to under 1 MB
Say you have a 4.5 megabyte photo from your phone and a form that will not take anything over 1 megabyte. Drop it in at quality 80 first. A typical phone photo comes back around 900 kilobytes on that setting alone, already clear of the limit, so you download it and you are done.
Now say the same photo is unusually detailed and lands at 1.3 megabytes at quality 80, still over. Pull the slider to 70 and watch the after size fall past the megabyte line, usually to somewhere around 800 kilobytes, with no difference you would notice on a screen. You did not have to guess a magic number, you watched the real one drop until it fit, and that works the same on a laptop or a phone, because the tool runs in the browser either way.
When reducing file size is the wrong move
Do not compress the file you plan to keep as your master, and do not save a photograph as a PNG. Compression cannot be undone, so keep your original and compress a copy, especially if you might crop deeply or print later.
PNG stores every pixel exactly, which is right for a logo or a screenshot and wrong for a photograph. A photo saved as PNG is routinely five to ten times larger than the same photo as a JPEG nobody could tell apart, because PNG's lossless compression cannot throw away the gradients and noise a lossy format is built to discard. If your file is large because it is a photograph in the wrong format, the fix is the format, not the quality slider.
There is also a compounding cost to compressing the same file more than once. Every lossy re-save throws away a little more detail on top of what the last save already discarded, so a JPEG that has been opened, edited, and re-exported five times looks noticeably worse than one exported once at the same quality setting. Always compress from the original, never from a copy that has already been through a lossy save, or the damage stacks in a way a single quality-80 pass never would.