How to make an image smaller depends on which kind of smaller you need. If a photo is too many bytes for an upload limit, compress it at quality 80, typically 60 to 80 percent smaller with nothing visible. If it displays too big on a screen, resize the pixel dimensions first, since that shrinks bytes too. Do both when you need to hit a strict target.
Most people asking this question have not noticed which problem they actually have, and fixing the wrong one wastes a step. Image size, the width and height in pixels, and file size, the bytes it occupies on disk, move together loosely but are not the same measurement, as the next section covers. This guide covers every real way to shrink an image file, on every device, plus two questions most pages skip: how the two levers interact, and how to hit an exact KB target. It is part of our complete guide to compressing an image.
| What's actually wrong | Pull this lever | What changes |
|---|---|---|
| Too many bytes for a limit (email, upload form) | Compress (quality) | Bytes drop, pixels stay the same |
| Looks huge or slow on a screen | Resize (dimensions) | Pixels drop, bytes drop as a side effect |
| Both at once | Resize, then compress | Removes pixels the page never shows, then re-encodes what's left |
What's the difference between image size and file size?
Image size is the picture's width and height in pixels; file size is how many bytes it takes up on disk, and the two are related but not identical (CZUR). That's the real gap in image size vs file size: one counts pixels, the other counts bytes, and compression is the bridge between them.
A 4000 by 3000 photo is twelve million pixels no matter how it's saved. Save those twelve million pixels as a well-compressed JPEG at quality 80 and the file drops to roughly 900 KB from an original around 4.5 MB, nothing visibly different, because compression throws away redundant byte patterns, not pixels. Crop the same twelve million pixels down to six million and the file shrinks too, but for the opposite reason: there is genuinely less picture left to store.
Someone hitting a 2 MB upload limit has a bytes problem. Someone whose photo displays oversized and slow on a page has a pixels problem. Fixing the wrong one wastes a step: resizing a photo that already clears the limit does nothing for the limit, and compressing a photo at the wrong dimensions does nothing for how large it displays.
How to make an image smaller online, step by step
The fastest fix for most bytes problems is the browser compressor: drop the file in, keep quality at 80, and download, typically 60 to 80 percent smaller with nothing you can see.
- Open the free image compressor and drop your file on it. Nothing installs; the file is processed in your browser.
- Leave quality at 80 to start. Check the after-size shown on the card. For most bytes-limit problems, that alone clears it.
- If it's still too big, pull the quality slider down. At 60 the file gets meaningfully smaller again; web.dev measured a 79 percent cut at quality 60 on a sample JPEG with no dimension change.
- If quality alone doesn't get you there, or the picture is visibly larger than where it's shown, resize the dimensions next (the next section covers how) and run the result back through the compressor.
- Download. The original stays untouched on your device, and anything you upload to compress it is deleted within the hour.
That covers most cases in one pass. The sections below are for when one pass isn't enough, or when the problem is pixels, not bytes, to begin with.
How do you make an image smaller on Windows, Mac, iPhone, and Android?
Every major platform has a built-in resize tool, though none offer a true quality slider, so treat these as the pixel-dimension half of the fix and compress afterward if bytes still matter.
| Device | Built-in method | What it does |
|---|---|---|
| Windows | Photos app, the three-dot menu, Resize image | Writes a smaller copy at a chosen pixel width |
| Mac | Preview, Tools, Adjust Size | Resamples to fewer pixels, or cuts file size directly via Resolution |
| iPhone | Adobe Lightroom Mobile, Export, Small | Downsizes on export, original stays untouched |
| Android | Gallery app edit, or a resize app | Removes pixels from the saved copy |
Reduce image dimensions 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 or enter a custom pixel width, then Save to create a smaller copy alongside the original.
Resize on a Mac
Open the file in Preview, click Tools, then Adjust Size. Make sure Scale proportionally is checked so the picture doesn't distort, enter a smaller width or height, and click OK. Preview can also cut file size directly: in the same dialog, check Resample image and lower the Resolution field, and the new size shows at the bottom before you save (Apple Support).
On iPhone
Download Adobe Lightroom Mobile, import the photo, tap Export, and choose Small under the dimension options, which downsizes the exported copy without touching the original in your camera roll.
On Android
Open the photo in your phone's Gallery app, tap edit, and use the crop or resize option to save a smaller copy, or install a dedicated app like Snapseed if your Gallery doesn't offer one.
The quick email trick
If you only need a smaller file for one email, most desktop mail clients offer a resize option in the attachment menu itself, Outlook included, that shrinks the copy actually being sent without touching the file on your device.
Does cropping make an image smaller?
Cropping removes pixels, so it can shrink a file, but only if it removes a meaningful share of them; trimming a thin border barely moves the number (Cloudinary).
Cutting a small border off a 4000 by 3000 photo removes a few hundred thousand pixels out of twelve million, and the byte savings are barely measurable, because almost all the original detail is still there. Cropping the same photo down to a tight square can cut the pixel count by more than half, and the file size drops with it.
The mistake is treating any crop as a size fix. A light crop for framing is not doing the job compression or a real resize would do. Crop for composition when the goal is composition, and reach for compression or a dimension resize when the goal is a smaller file.
How much smaller can you go before it looks bad?
Quality 80 is visually lossless for a photograph and quality 60 still holds up on most screens; below about 50 you start to see blocking in flat areas like sky.
| Quality | File size (same 4.5 MB photo) | What you'll notice |
|---|---|---|
| Original | 4.5 MB | Full detail, unnecessarily large for a screen |
| 80 (default) | 0.9 MB | Visually lossless |
| 60 | 0.47 MB | Still hard to tell apart from the original |
That's the bytes lever, pixels held constant. The pixels lever works independently of it: fewer pixels compress to fewer bytes at the same quality setting, because there is objectively less data to encode. web.dev found that serving oversized dimensions can waste two to four times the data a page actually needs, and the same relationship holds in reverse when you resize down before compressing.
Does the file format change how small it can get?
Format is the third lever, after quality and dimensions, and it stacks with both rather than replacing either. JPEG and WebP are lossy: they throw away detail to save bytes. PNG is lossless: it keeps every pixel exactly, which is why a photo saved as PNG is routinely five to ten times larger than the same photo as a JPEG nobody could tell apart. WebP typically runs 25 to 35 percent smaller than a JPEG at similar visual quality, and AVIF often saves 50 percent or more, though it takes longer to encode.
If the image is a photograph, format usually matters more than people expect: switching from PNG to JPEG or WebP can shrink the file dramatically before the quality slider even moves. If it's a screenshot, logo, or anything with sharp text and hard edges, keep it lossless; a lossy save at those edges shows compression artifacts a photograph would hide.
How do you hit an exact KB or MB target?
Start with quality 80, check the after-size, and if you need it smaller than quality 60 can comfortably get you, add a dimension resize on top, since the two levers compound rather than substitute for each other.
Getting to an exact KB target is the one part of how to make an image smaller that most guides skip entirely, so here's the arithmetic worth knowing. The 4.5 MB photo above lands around 900 KB at quality 80. Cut the quality to 60 and it drops to roughly 470 KB. Neither clears a strict 100 KB limit, the kind some passport-photo or government-form uploaders enforce.
That's where dimensions have to join the fight. Pixel count drives byte count roughly in proportion at a fixed quality, so halving both the width and height, a quarter of the original pixels, should land in the neighborhood of a quarter of the quality-80 size, close to 225 KB, and noticeably less again at quality 60, likely near 100 to 120 KB. This is a proportional estimate to plan from, not a guarantee; check the actual after-size once you've resized and compressed, since the picture's own content, not just its pixel count, affects how well it compresses.
| Target | Usually needs |
|---|---|
| Under 1 MB | Quality 80 alone, for most phone photos |
| Under 200 KB | Quality 60 to 70, no resize needed for most photos |
| Under 100 KB | Quality 60 or lower, plus resizing to roughly half the original width and height |
| Under 20 KB | A real resize to small dimensions; quality alone rarely gets there |
When should you not make an image smaller?
Don't resize or heavily compress the file you're keeping as your master copy. Both are one-way changes: a resized image can't regain the pixels you cut, and a compressed JPEG can't regain the detail thrown away at a low quality. Shrink a copy and keep the original at full size, especially if you might crop, print, or reuse it larger later.
Upscaling works against you the same way in reverse. Adding pixels a photo doesn't have, through resampling to a larger size, doesn't add real detail; it inflates the file while making the image look softer, not sharper. If you need a bigger image, start from a higher-resolution original rather than stretching a small one.
Don't resize down for print, either. A screen only needs enough pixels to fill the display, commonly under 2000 pixels wide even on a large monitor, but a printed photo needs far more, roughly 300 pixels per inch at the final print size, so an image sized for the web is often too small once it's sized for paper.
And don't compress an image that's already small. A screenshot or icon at 40 KB isn't worth running through a compressor for a few kilobytes of savings, and compressing a PNG with fine text or hard edges at a lossy setting can visibly soften it for a saving nobody will notice.