Photo and Signature Upload: Fix the KB and Pixel Limits

You have filled in a long application form, you are on the last step, and the portal says the file is not accepted. It does not say why. A photo and signature upload fails in a handful of predictable ways, and almost all of them come down to numbers: kilobytes, pixels and file type. This guide answers the questions people actually ask when that happens, with the arithmetic shown so you can check it yourself.

Everything below was worked out for the situation where you are holding a phone photo of a few megabytes and the form wants something tiny. The steps use the Image Compressor, the Image Resizer and the Image Cropper, which process the picture on your own device rather than uploading it.

Why does my photo and signature upload keep getting rejected?

There are four usual reasons, and portals rarely tell you which one applies.

1. The file is too big. A phone photo is typically several megabytes. A form that asks for 50 KB wants a file roughly sixty times smaller than a 3 MB original (3 MB is 3,145,728 bytes, 61.4 times 51,200).
2. The file is too small. Many forms give a range, not just a maximum. One state recruitment portal's upload guide, which we downloaded and read on 28 October 2026, asks for a photo between 50 KB and 100 KB and a signature between 20 KB and 50 KB. A file of 30 KB can be rejected as too small as surely as one of 3 MB is rejected as too big.
3. The pixel size is outside the range. The same guide asks for a photo of at least 240 x 320 pixels and at most 480 x 640 (it describes this as 0.3 megapixels), and a signature of at least 280 x 80 and at most 560 x 160.
4. The format is wrong. The same guide says only JPEG is accepted for the signature, and that a photograph of a signature taken with a mobile phone will not be accepted. Phone photos from some devices are saved as HEIC, which many portals do not take.

Those numbers belong to one portal and differ for every exam and recruitment body, so always read the guide on your own form. The pattern, however, is common: a range in KB, a range in pixels, a format and a rule about how the picture was produced.

Is 1 KB 1,000 bytes or 1,024 bytes?

Both are used, and a portal does not tell you which one it uses. The standards bodies treat them as different units. NIST's page on binary prefixes explains that the prefix kilo means 1,000 and that the binary prefix kibi, with the symbol Ki, was approved in 1998 to mean 1,024 bytes. In everyday computing, though, "KB" is used for either.

The safe habit is to aim below the limit by a margin, so that the file passes whichever way the portal counts. The compressor does this: in Target size mode it aims for 97 percent of the number you choose, using 1 KB as 1,024 bytes. The table shows what that does to the common limits.

The 3 percent margin means a file produced for a 50 KB limit comes out around 48.5 KB when measured in 1,024-byte units and around 49.7 kB when measured in 1,000-byte units, so it clears the limit under both readings. If your portal also has a minimum, remember that the compressor aims just under the limit you choose, not at the middle of a range.

In what order should I fix the picture?

Do things in this order, because each step changes what the next one has to do.

1. Convert the format if needed. If the photo is HEIC, convert it with the HEIC to JPG tool first. The compressor's own error message notes that some browsers cannot open HEIC.
2. Crop to the right shape. Passport-style photos are usually portrait, not square. Use the Image Cropper in Free mode and drag the box around the face and shoulders. Crop before you shrink, so you do not spend pixels on a background you will throw away.
3. Resize to the pixel range. The compressor in Target size mode does not let you type exact dimensions, so use the Image Resizer in Exact px mode if the form asks for specific pixels. With the lock on, typing a width works out the height from the picture's shape.
4. Compress to the KB limit. Open the Image Compressor, choose Target size, pick a preset such as 50 KB or 100 KB, or type a custom size between 5 and 5,000 KB, and press the button. The tool also has per-size pages, such as the one for compressing an image to 50 KB, which open with that target already selected.
5. Check the result against the form. Look at the size and pixel line shown under the result, then open the file on your device and look at the face.

Doing it the other way round, compressing first and resizing afterwards, can waste effort: shrinking pixels after compression changes the file size again, and you are back at the start.

How many pixels can a small file hold?

This is the question behind most failures. A file limit is a budget; the pixel count decides how far the budget stretches. The table shows the bytes available per pixel when the compressor aims for the 100 KB and 50 KB limits at the sizes from the portal guide above, next to a typical phone photo. The figures are our own arithmetic.

A 12-megapixel photo is 39 times larger than a 480 x 640 image in pixels, which is why quality sliders alone cannot get a phone photo down to 100 KB. The picture has to lose pixels too. That is also why the compressor reduces the dimensions when lowering the quality would not be enough.

What if the form asks for a minimum size?

Then aim high within the range. The compressor only ever makes a file smaller or leaves it as it is. If your picture is already under the number you choose, the page says so and notes that it probably needs no compression, though you can still re-encode it to change the format or the dimensions.

If a photo comes out smaller than the minimum, there are three honest options. Choose a larger target, for example 100 KB for a 50 to 100 KB range, so the encoder keeps more quality. Start from a bigger or sharper original, such as a fresh photo in good light. Or enlarge the picture with the Image Resizer before compressing. Enlarging adds no real detail, so use this only as a last resort, and keep within the pixel range the form allows.

A flat, simple picture such as a signature on white paper can come out well below the limit even at high quality, because large flat areas compress very efficiently. If the form wants at least 20 KB for a signature and yours is 8 KB, a slightly larger scan at a bigger pixel size is the usual fix. Padding a file with noise to reach a minimum is not a good idea, because the picture still has to be clear.

Why is a signature different from a photo?

A signature is mostly white paper with a thin dark line. That is easy to compress, so it usually passes the KB limit without effort and fails on something else: the pixel size, the format, or how it was captured. In the guide we read, the signature is to be signed within a rectangular box on white paper with a black or dark blue pen, scanned, and uploaded as a JPEG, and a signature photographed with a mobile phone is rejected. Other portals ask for similar things.

The practical points are these:

• Scan or photograph in even light, with no shadows across the paper.
• Crop tightly to the signature box so little of the picture is blank.
• Keep the signature in the pixel range, then compress.
• Match what you will sign on the day. The same guide warns that a mismatch between the uploaded signature and the one at the examination can lead to disqualification, so use your usual signature.

How low can the quality go before the photo is unusable?

The compressor does not push the quality down blindly. For a target size it looks for the highest quality that fits, up to 95 percent, and 35 percent is the lowest it accepts while keeping the resolution. If even 35 percent does not fit, it shrinks the dimensions in steps and tries again. It will not shrink the longest side below 160 pixels unless the original is already smaller. Only at that floor does it allow quality below 35 percent, as a last resort. If it still cannot reach the limit, it says "Couldn't reach" and shows the closest result, with a suggestion to crop the image first or choose a larger size.

That behaviour has a consequence for faces. The first lever is quality and the second is pixel size, so a face photo will usually lose sharpness before it loses size. Zoom to 100 percent on the result and check the eyes and any text. If it looks too soft, crop closer to the face so those pixels are not shared with the background, or choose the next size up if the form allows it.

The output is a JPEG by default, which is accepted almost everywhere. WebP is offered too, but the page marks it as less widely accepted, so for a form portal stay with JPEG. PNG cannot be squeezed to a KB target, and the tool says so.

Is my photo uploaded when I use these tools?

No. The compressor, resizer and cropper run in your browser, using the canvas feature that browsers provide. The picture is decoded, redrawn at the new size and encoded again on your device. MDN's documentation of the canvas toBlob method explains how the quality value from 0 to 1 controls JPEG and WebP output and that an unsupported type falls back to PNG; the tool checks the type it gets back and reports an error rather than quietly handing you a different format. Resizing redraws the picture from its pixels, so details stored in the original file, such as location data, are not copied to the resized file. For anything as personal as an ID photograph, that is a better place to start than a website that asks you to upload it.

Common mistakes

• Compressing a screenshot or a scan of a screenshot. Text and sharp edges in JPEG show artefacts quickly. Re-scan if you can.
• Sending the final file through a chat app. Many messaging apps recompress pictures, which changes the size you carefully reached. Copy it by cable or send it as a document instead.
• Renaming a file to .jpg. Changing the extension does not change the format. Convert it.
• Stopping at the KB limit and forgetting the pixels. A file can be 40 KB and still be 4000 pixels wide.
• Editing after the final compression. Cropping or rotating a finished file and saving it again re-compresses it, so the size changes. Do the edits first and compress last.
• Leaving it to the last hour. Prepare the photo and signature files before you open the form, so a rejected upload does not cost you time on a deadline day.

---

Sources and methodology

• Staff selection upload guide, Rajasthan government recruitment portal — the photograph is JPEG, 240 x 320 to 480 x 640 pixels, 50 to 100 KB; the signature is JPEG, 280 x 80 to 560 x 160 pixels, 20 to 50 KB; a signature photographed with a mobile phone is not accepted. Downloaded and read on 28 October 2026. Requirements differ for every exam and portal, so use your own form's guide.
• NIST, Prefixes for binary multiples — kilo means 1,000; the binary prefix kibi, approved in 1998, means 1,024.
• MDN, HTMLCanvasElement.toBlob() — the quality argument for image/jpeg and image/webp runs from 0 to 1; an unsupported type is exported as PNG.
• Tool behaviour (Target size mode, the 97 percent aim, the 35 percent quality floor, the 160 pixel floor, JPEG and WebP output, the already-smaller notice) was read from the Image Compressor's code on 28 October 2026.
• Calculations: 20 KB, 50 KB, 100 KB and 200 KB in both readings, with the aim being the limit in 1,024-byte units times 0.97, rounded down; bytes per pixel is that aim divided by width times height; a 3 MB photo is 3 x 1,048,576 bytes, and 61.4 is that divided by 51,200.

Last reviewed: 2026-10-28. Always follow the requirements printed on the form you are filling in.

---

Harshil writes about privacy-first tools, developer productivity, and the trade-offs between browser-based and uploaded utilities.