Why a byte limit is not the same as a dimension limit
Forms that ask for an image rarely describe it in pixels. They describe it in bytes: "between 20 KB and 100 KB", "maximum 50 KB", "not larger than 200 KB". That range is about how much data the file contains — not how big it looks. A 3000 × 4000 photo saved at low quality can be smaller than a 600 × 600 logo saved at maximum quality, because what each pixel stores matters as much as how many pixels there are.
This is why resizing alone often fails. Changing 3000 px to 1000 px helps, but if the encoder still writes every pixel at near-lossless quality the file can remain far over the limit. Conversely, lowering quality on a huge image usually works but can leave visible mush in the details. The reliable approach is to change one variable at a time and check the result after each change.
The order of changes that works
Try these in order and stop as soon as the file lands inside the range. Each step costs less visual quality than the one after it.
- Strip what is not needed. Re-encoding an image to JPEG or WebP drops metadata such as EXIF, which can be a meaningful share of a phone photo's size. See Image Metadata first if you want to know what is being carried.
- Lower the quality, not the size. In Compress Image move the quality slider down in steps of 5–10 and watch the reported size. Quality 80 is usually indistinguishable from 95 on a screen; quality 50 rarely is.
- Switch format if you have not already. WebP at a given quality is normally smaller than JPEG at the same quality. Image Converter can make the swap in a batch.
- Reduce dimensions only if the requirement allows it. If the form also states a pixel size, use Resize Image to hit it — but remember the resulting byte size will change again, so re-check after resizing.
- Use the targeted tool when the range is tight. Exact KB Photo Compressor re-encodes repeatedly against a target and only downscales when it truly cannot reach it, which is much faster than guessing.
If a limit is stated as "maximum 50 KB" with no lower bound, aim for roughly 40–45 KB. Landing at 49.9 KB leaves no room for a different encoder, a different browser or an upload system that counts bytes slightly differently.
A worked example
Suppose a portrait arrives at 3024 × 4032 and 4.2 MB. Halving the dimensions to 1512 × 2016 cuts the pixel count to a quarter and often lands around 400–700 KB at quality 85 — still far too big. Dropping to quality 65 might reach 180 KB. Converting to WebP at quality 70 might reach 90 KB. One more modest resize to 1000 px wide, still comfortably larger than most photo requirements, plus quality 65, commonly lands in the 30–60 KB zone — then a final quality nudge finishes the job. These intermediate numbers are illustrative: real images vary enormously depending on detail, noise and lighting. The point is the order, not the exact figures.
If you need to verify the final file really is inside the range, Image Metadata prints the exact byte size read from the file header.
What usually goes wrong
- **The file is still over after resizing a lot.** The quality setting is probably still high, or the format is PNG. PNG stores detail losslessly, so a photograph in PNG can stay enormous at any dimension. Convert to JPEG or WebP first.
- **The image looks blotchy or soft.** Quality went too far in one jump. Back the slider up until the artefacts stop being visible at 100% zoom, then reduce dimensions slightly instead — halves the data again with far less visual damage.
- **The file is under the lower bound.** Increase quality or dimensions a step at a time rather than restarting from the original.
- **The size reported by the tool differs from what the form says.** Some forms count KB as 1000 bytes and some as 1024 bytes. Aim slightly below the limit to be safe either way.
Common questions
Does lowering dimensions always lower file size?
Practically yes — fewer pixels means less data to encode — but the quality setting and the file format have a larger effect per change than most people expect. Dimensions are the last thing to change, not the first.
Is WebP always smaller than JPEG?
At the same perceptual quality, WebP is usually smaller, but not always and not by the same margin on every image. If a form rejects WebP, convert to JPEG instead — many upload forms accept JPEG and PNG only.
Will the tool keep my exact pixel dimensions?
The exact-KB compressor keeps dimensions while it can, and only downscales when it cannot reach the target at the current size. Resize Image is the tool to use when you must change dimensions deliberately.