Most upload forms, email providers, and web applications cap how large a file you can send: under 2MB, sometimes as strict as 100KB for a profile photo. Modern phone cameras routinely produce photos 4 to 8MB in size, so hitting a specific target almost always means doing something to the file first, not just picking a smaller one.
In this article
This guide walks through what actually determines an image's file size, a practical process for hitting a target like 100KB, 200KB, or 1MB, and how to pick a format when size is the priority.
Key takeaways
- File size is set mainly by pixel dimensions and compression quality, not by the camera's megapixel count or by DPI, which only matters for print.
- Resizing to the dimensions you actually need almost always saves more than lowering quality alone.
- WebP and AVIF produce meaningfully smaller files than JPEG at the same visual quality, AVIF often by 30 to 50 percent.
- There's no single setting that reads "100KB" and gets you there. Resize, compress, then check the result.
What actually controls an image's file size
Three things set an image's file size: its pixel dimensions (width times height), its format, and how aggressively that format compresses the data. A photo's megapixel count, which really just describes its maximum dimensions, and its DPI, which only affects how large it prints, have nothing to do with the file you're trying to shrink for a screen or an upload form.
A 12-megapixel photo straight off a phone is typically 4000 by 3000 pixels, far larger than almost any screen it will actually be shown on. Resizing it down to the dimensions it's actually displayed at, for example 800 pixels wide for a web upload, usually cuts the file size dramatically before a single compression setting is touched.
How to hit a specific file size target
There's no slider that reads "100KB" and lands you there in one step, image formats don't work that way. The practical process is to resize first, compress second, and check the result, adjusting one or the other if it's still over target.
1. Resize to the dimensions you actually need
Work out roughly how large the image will actually display, then resize to that, not the camera's original dimensions. An avatar shown at 200 pixels doesn't need a 4000-pixel source; a blog header shown at 1200 pixels wide doesn't need 6000.
2. Pick a format suited to the content
Photos compress best as JPEG, WebP, or AVIF. Flat graphics, screenshots, and anything needing transparency compress best as PNG or WebP. PNG is lossless, so it never loses quality, but that makes it a poor choice for photographic detail specifically, where it produces far larger files than a lossy format at a visually identical result.
3. Adjust compression quality and check the result
Lower the quality setting and check the resulting file size. Most formats hold up visually well down to roughly 70 to 80 percent quality for a photo. Below that, compression artifacts, blotchy or blurred patches, especially around hard edges and text, start to show.
4. Repeat if it's still over target
If the file is still too large after resizing and compressing, go back and resize smaller rather than pushing the quality setting lower still. Smaller dimensions at a decent quality setting generally look better than the original dimensions compressed hard.
Choosing a format: JPEG, WebP, or AVIF
If getting the smallest possible file is the priority and the destination accepts the format, WebP and AVIF beat JPEG by a real margin at the same visual quality. WebP typically produces files 25 to 35 percent smaller than JPEG; AVIF tends to go further still, often 30 to 50 percent smaller than JPEG, though the gap narrows for photos with a lot of fine detail or visual noise.
JPEG remains the safest default anywhere compatibility matters more than the last few percent of file size. It's supported everywhere, including the handful of older systems and upload forms that still reject WebP or AVIF files outright.
Common mistakes
- Adjusting quality before resizing. Dimensions usually matter more than the quality setting. Resize first, then see how much compression is actually needed.
- Judging by dimensions alone. Two images at the same pixel size can differ in file size by 5x or more depending on format and compression.
- Re-compressing an already-compressed JPEG. Each re-save of a lossy format loses a little more quality. Work from the original file, not one that's already been compressed once.
- Uploading something private to a website just to shrink it. A web-based compressor has to receive the actual file to process it. A tool that runs locally never has that exposure to begin with.
FAQ
Does lowering DPI make a digital photo smaller?
No. DPI only controls how large an image prints; it has no effect on screen display or file size. Resizing the actual pixel dimensions is what reduces file size.
Is PNG or JPEG smaller?
For photos, JPEG is almost always smaller. PNG is lossless and wasn't designed for photographic detail. For flat graphics, logos, or screenshots, PNG is often the smaller, cleaner choice.
Can I hit an exact file size, like exactly 100KB?
Not precisely in one step. Compression settings control quality, not a target file size directly, so hitting a specific number takes a resize-compress-check cycle, usually two or three passes.
The bottom line
Hitting a specific file size target comes down to two levers: pixel dimensions and compression quality, with dimensions usually doing most of the work. Resize to what the image will actually be shown at, pick a format suited to the content, and adjust quality from there.
Image Tools does all three locally: resize, format conversion, and compression, without uploading the file anywhere to get it done. The free trial processes a limited number of images with no account needed.
