How to get a photo under a KB limit

A phone photo is often several megabytes. An application form, exam registration or job portal may accept 100 KB or less. That gap sounds huge, but closing it is usually easy once you know which settings actually control file size and in which order to use them.

The three things that decide file size

1. Pixel dimensions

The number of pixels is the biggest factor. A typical 12 megapixel phone photo is 4032 x 3024 pixels, which is about 12.2 million pixels. If you resize it to 1200 x 900, you have about 1.08 million pixels, roughly 11 times fewer. The file shrinks dramatically, and for a photo that will be viewed on a screen or printed small, 1200 pixels across is usually plenty.

A useful rule: halving both the width and the height leaves a quarter of the pixels.

2. Compression quality

JPG and WebP have a quality setting. Lower quality means the encoder throws away more fine detail. Between about 75 and 90 the difference is hard to see in normal viewing, while the file size changes a lot. Below roughly 60, artifacts start to appear: blocky skies, smudged edges and noise around text.

3. Format

For photos, use JPG (or WebP if the form accepts it). PNG is lossless, which is great for screenshots and logos but makes photos several times heavier. If a form says JPG only, it means JPG; WebP will often be rejected even though it is smaller.

The same settings do not give the same size for every photo. A plain portrait against a white wall compresses far better than a busy street scene or a grainy photo taken in low light, because detail and noise cost bytes.

KB is not always the same KB

Size limits are written in KB or MB, but there are two ways to count them:

• Binary: 1 KB = 1024 bytes, 1 MB = 1024 KB. Windows File Explorer counts this way.
• Decimal: 1 KB = 1000 bytes, 1 MB = 1000 KB. macOS Finder and many websites count this way.

Here is where it causes trouble. A file of 101,000 bytes shows up as about 99 KB on Windows, which looks fine for a 100 KB limit. If the form counts 1 KB as 1000 bytes, the same file is 101 KB and gets rejected. You rarely know which method a form uses, so aim about 5 to 10 percent under the limit. For a 100 KB limit, target around 90 to 95 KB.

The right order of steps

Doing things in the right order keeps quality as high as possible.

1. Start from the original file. Not a screenshot, not a copy that went through a messaging app, which has usually been compressed already.
2. Crop and rotate first. Remove what the form does not need. A tightly cropped photo has fewer pixels to store. The crop tool is exact to the pixel.
3. Resize to sensible dimensions. If the form states pixel dimensions, use exactly those. Otherwise 1000 to 1600 pixels on the long side is a good starting point for most uploads. Use the image resizer.
4. Save as JPG at quality 80 to 85. Check the size.
5. If it is still too big, lower the quality gradually, down to about 70.
6. If that is not enough, reduce the dimensions further rather than going to very low quality. A smaller sharp photo looks better than a large blocky one.
7. Check the result at 100 percent zoom before uploading.

Let the target-size tool do steps 4 to 6

Trying quality values by hand is tedious. The compress to target size tool automates it:

1. Choose a preset (20, 50, 100, 200, 300 or 500 KB, or 1 MB) or type a custom value in KB or MB.
2. Choose JPG (default) or WebP output.
3. Optionally set a maximum width or height if the form also has dimension rules.
4. Drop in your photos.

The tool searches for the highest quality that still fits under the target, trying values between 30 and 95 on the quality scale. If even the lowest quality is too big, it reduces the pixel dimensions step by step, by 15 percent each time, and tries again. It then shows the final size, the quality it used and the dimensions, so you can judge whether the result is good enough. It counts 1 KB as 1024 bytes, so for strict forms set a target slightly below the official limit.

For general compression without a strict target, the image compressor keeps the original format where it can and shows how much you saved. Everything runs in your browser, so your photos are not uploaded anywhere while you work on them.

Common mistakes that waste kilobytes

• Uploading a screenshot of a photo. It includes parts of the screen, has a lower resolution than the original and is often saved as PNG, which makes it heavier.
• Saving photos as PNG. A photo in PNG format can easily be several times larger than a good JPG with no visible benefit.
• Converting JPG to PNG to improve quality. It cannot restore lost detail and makes the file bigger. The PNG vs JPG guide explains why.
• Compressing the same JPG again and again. Every save at lossy quality adds new artifacts. Go back to the original instead.
• Going too small. Some forms also have a minimum pixel size or reject blurry photos. Read every requirement, not just the KB limit.
• Renaming instead of converting. Changing photo.heic to photo.jpg does not change the data. See the guide on file extensions.
• Ignoring the photo itself. Noise from a dark room costs a lot of bytes. A photo taken in good light compresses better.

If the form needs an ID photo of a specific size, set the size first with the passport and ID photo guide, then bring the file under the limit.