Here is how to reduce JPEG image size without wrecking it: lower the quality setting to somewhere between 60 and 85, resize the pixel dimensions first if the photo is bigger than it needs to be, and save the result as progressive JPEG. Those three moves are how you reduce JPEG size and recover most of the file weight a camera or phone adds by default, before the compromise becomes visible.
| Quality range | What you get | Watch for |
|---|---|---|
| 90 to 100 | Barely smaller than the source, sometimes larger than a well tuned 80 | Rarely worth it outside archival masters |
| 80 (our default) | Visually lossless at normal size, roughly 80 percent smaller than the camera original | Safe default for almost everything |
| 60 to 70 | Roughly half again, still hard to tell on a screen | Good for a size limited upload |
| 50 to 59 | First visible softness in skin tones and skies | Only when you must hit a strict cap |
| Below 50 | Visible 8x8 block seams and color banding | Resize instead of pushing lower |
How to Reduce JPEG Image Size in Under a Minute
The fastest route is a browser compressor: drop the file in, watch the output size update as you move the quality slider, and stop where the number and the picture both look right. The JPG compressor on this site opens at quality 80 and shows the after size live, no upload limit games and no signup, so if you need to land under a specific cap, like the 100 KB many upload forms still enforce, you can watch the number cross that line instead of guessing at a setting. Nothing installs and nothing leaves your machine unaccounted for: files are deleted from the server within the hour.
This is also the fastest way to reduce JPEG size when you only have one file, since it shows you the real tradeoff in real time. A desktop tool's quality slider is a number with no feedback until you export and check the file size by hand; a browser tool that recomputes the output live turns the same decision into something you can see, which matters because the JPEG quality setting for smaller files is not standardized between tools. What one program calls quality 75 is not guaranteed to match another program's 75, so watching the actual result beats trusting the label.
What Actually Shrinks a JPEG When You Lower the Quality?
Lowering the quality number tells the encoder to round off more detail during one specific step; everything else in the format stays the same. JPEG splits an image into 8x8 pixel blocks, converts each block into a set of frequency numbers, then divides those numbers by a table and rounds to the nearest integer. Quality controls how coarse that rounding is: high quality keeps almost all the numbers, low quality rounds most of them to zero, and long runs of zeros compress to almost nothing. Our JPEG hub guide walks through the full six stage pipeline behind that one slider; here, the only thing worth remembering is that it is a rounding knob, not a resolution knob, and rounding harder is what eventually makes a photo look wrecked.
JPEG also throws away color detail on purpose, through a step called chroma subsampling: it stores the color layers at a lower resolution than the brightness layer, because eyes are far more sensitive to brightness than to hue. That trade is usually invisible and it is where a meaningful share of the format's everyday saving actually comes from, before the quality slider does anything at all.
Resize the Dimensions Before You Touch Quality
If a JPEG is too big, the first question is not what quality to use, it is what size the image needs to display at. An oversized image wastes two to four times the data a compressor can ever claw back, because pixels nobody will ever see still cost bytes at every quality setting. A photo headed for a web page at 800 pixels wide gains nothing from staying 4,000 pixels wide; downscale first, and the quality slider then works on a much smaller photo instead of a twelve megapixel one.
Cropping does the same job from a different angle. If the frame includes a wall of empty background or a strip you do not need, cutting it out removes real pixels rather than compressing around them, which drops weight with zero quality cost, unlike anything the quality slider can offer. Resizing and quality are two separate levers solving two separate problems, and the single biggest mistake people make trying to reduce a JPEG's size is pulling the quality lever alone to fix what is actually a dimensions problem.
What Quality Setting Actually Keeps a JPEG Looking Right?
Why 60 to 85 usually looks fine
Quality 80 is where the web has landed as a default because it is visually lossless for a photograph at normal viewing size, and it is our tool's default for the same reason. web.dev's own test found that quality 60 cut a sample JPEG's size by 79 percent, with differences across most of the scale imperceptible even in a side by side comparison. That number lines up with what we see across the tool: most of the safe saving in a JPEG is available well before the format starts to show damage, so treating anything from 60 to 85 as the working range, rather than reaching for 100 out of habit, is where the real jpeg compression without losing quality actually happens.
When to go higher
Push toward 90 or above only when the file is a print master, a scan you may reprocess, or something you will re-edit later, since higher quality preserves headroom for a second pass. For anything that ends on a screen, a viewer cannot see past 80, so spending bytes above it buys nothing. And because the setting is subjective by the format's own design, do not assume a "75" in one tool matches a "75" in another; watch the actual result rather than trusting the number alone.
How Do You Reduce a JPEG's Size on Windows?
Windows has two built in routes, neither of which needs a download. Right-click the JPEG, choose Open with, and select Paint; inside Paint, the Resize command on the ribbon lets you drop the horizontal and vertical percentages, for example to 50 percent each, which quarters the pixel count and the file weight along with it, then save. The Photos app offers a lighter version of the same idea: open the image, use its resize option before saving a copy, and skip Paint's extra steps if you only need a quick dimension cut. Neither app gives you a quality slider the way a JPEG-aware compressor does, so Paint and Photos are the dimensions lever, not the quality lever; for the quality half of the job, the browser tool above is the faster, more precise route on Windows too.
How Do You Reduce a JPEG's Size on a Mac?
Preview is the native answer. Double-click the JPEG to open it in Preview, then use Tools, Adjust Size to change the pixel dimensions directly, which is the resize lever done natively. For the quality lever, use File, Export, choose JPEG, and drag the quality slider in the export dialog; Preview shows an estimated file size as you move it, similar to the live feedback a browser compressor gives you, just without the option to compare formats or strip metadata automatically. Between the two dialogs, Preview alone covers most of what this page recommends, dimensions first, then quality, without installing anything.
Reducing a JPEG on Your Phone
Phones are the weakest link in the native toolkit, because neither major mobile platform ships a real quality slider for JPEG export. On an iPhone, the closest built in lever is Mail's own attachment sizing: when you attach a photo, Mail offers Small, Medium, Large, or Actual Size before sending, and picking Small or Medium both shrinks the dimensions and cuts the file weight, though you only get that option inside Mail's send sheet, not as a general export tool. Android's stock gallery and Files apps are thinner still, with no built in resize-and-compress step at all on most devices.
Because neither platform gives you real control, a browser compressor is the more complete answer on a phone than on a desktop, not less: open the tool in Safari or Chrome, upload straight from your camera roll, and you get the same quality slider and live output size you would on a laptop, which is the one thing neither phone's native tools offer. This is also the gap in most JPEG advice you will find searching from a phone: the top results assume a desktop app is available, and mobile is treated as an afterthought if it is mentioned at all.
How Small Can the Same JPEG Get? Comparing the Levers
Every lever above moves the needle by a different, independently documented amount, and laying them side by side is more useful than any single number:
| Lever | Typical size change | Source |
|---|---|---|
| Resize to the size the image actually displays at | 2 to 4x smaller, before quality does anything | web.dev |
| Quality 80 versus the original file (our tool's default) | Roughly 80 percent smaller | canonical, this site |
| Quality 60 versus the same file's original | Roughly 79 percent smaller, independently measured | web.dev |
| Progressive versus baseline at the same quality | Slightly smaller, identical pixels | web.dev |
| Stripping EXIF and other metadata | Free bytes back, zero visual cost | DigitalOcean |
Our own canonical example is the one number on this page you can check against the live tool: a 4.5 MB phone photo compressed at quality 80 comes back around 900 KB. Switch the output format to WebP at the same visual quality and MDN's own comparison puts WebP 25 to 35 percent smaller than an equivalent JPEG, which on that same 900 KB file lands the WebP version somewhere around 630 KB, for no visible difference at normal size.
| Format and setting | Size | Basis |
|---|---|---|
| Original | 4.5 MB | Canonical phone photo example, this site |
| JPEG, quality 80 | 0.9 MB | Canonical phone photo example, this site |
| WebP, equivalent visual quality | about 0.63 MB | MDN's 25-35% smaller than JPEG, applied to the 0.9 MB result |
If you cannot switch formats, that same table is the argument for staying inside the 60 to 85 quality band: past that range you are trading bytes for damage instead of bytes for nothing, which is the whole point of finding the setting before you need it.
When Should You Crop Instead of Compress?
Crop when the frame holds pixels you do not need, a wall of ceiling above a portrait, a border of table around a product shot, dead space at the edges of a screenshot. Removing that area is not compression at all, it is just fewer pixels to encode, so it costs nothing in visible quality and stacks on top of whatever quality and resize savings you already have. It will not save a photo that is genuinely full of subject, but it is the first thing worth checking before you push the quality slider lower than you'd like to.
How Far Is Too Far? When JPEG Compression Starts to Show
The tell is not one thing, it is three, and they show up together once you cross roughly quality 50 on a normal photo. Flat areas like a clear sky show faint rectangular seams where the 8x8 blocks meet, because the rounding is no longer subtle enough to hide the grid the format encodes in. Skin and other smooth gradients go soft and slightly waxy, since quantization has thrown away the fine detail that sat between blocks of color. And saturated edges, a red logo against a blue sky, start to bleed slightly at the border, a side effect of the chroma subsampling covered above storing color at lower resolution than brightness.
None of this is a bug; it is the format's compromise becoming visible once you have spent it down. If you are already at 50 and still over your limit, resizing the pixel dimensions gets you further than pushing quality any lower, since dimensions and quality attack the file from two different directions rather than the same one twice.
Turn On Progressive JPEG and Strip Metadata for Free Savings
Progressive JPEG, on by default here
Progressive JPEGs store their data in passes instead of top to bottom, so the whole image appears at once, blurry, then sharp, instead of drawing one strip at a time. Outside the smallest images, a progressive file also comes out slightly smaller than the same photo saved baseline, at no cost to the pixels themselves. Our tool writes every JPEG progressive by default, so this is one saving you get without deciding anything.
Strip metadata for free bytes
A camera photo carries EXIF data, the metadata block recording the camera model, the exact timestamp, and often GPS coordinates, and none of it affects how the photo looks. Stripping it costs nothing visually and nothing you are likely to want kept, and our tool does it automatically on every file, no setting to find. On a desktop tool, the equivalent command is jpegoptim --strip-all or convert -strip, either of which removes EXIF, IPTC, and ICC data in one pass, all of it dead weight the photo never needed.
Tools If You Are Not in the Browser
For a batch or a pipeline, convert input.jpg -quality 85 output.jpg is ImageMagick's version of the quality lever, and jpegoptim --max=85 photo.jpg is a common default for photographic web content, dropping to 75 for thumbnails and rising to 90 or higher for anything archival. GIMP's File, Export As dialog shows an estimated size as you move its own slider, the same general approach whichever tool you reach for. For a one-off file with no software installed, the browser compressor above still covers it without a command line, watching the after size update live instead of guessing at a flag.
When Not to Touch the Quality Slider at All
Leave quality alone, or set it high, on anything you plan to edit again, print large, or keep as a master; JPEG compression is one way, and a second lossy save on top of the first stacks the damage, a real effect called generation loss. Do not use JPEG for a screenshot, a chart, or line art with hard edges and flat color, since the format's block based compression was tuned for photographic noise and shows on crisp edges as ringing and smudging; PNG is the right container for that content regardless of quality setting. And if the photo already looks soft or blocky from a prior save, a lower quality number will not fix what an earlier pass already threw away, it will only add a second round of the same damage on top.