How to get a file past a government portal's upload limit

A portal refuses your upload for one of four reasons: the file is over the stated size, under an unstated minimum, the wrong format underneath its extension, or the wrong pixel dimensions. Fix them in that order — dimensions, then bytes, then format — and almost everything goes through on the first attempt. Doing it the other way round, compressing before cropping, wastes the compression and usually leaves you re-doing the whole thing. If you are filling an SSC, IBPS, RRB or UPSC application, the exact pixel and KB bands for those are in photo and signature size rules for Indian exam forms; this article is about everything else that asks you to upload something.

Read the limit properly before you touch the file

The rule is almost never in one place. Check all five:

1. The instructions page or "guidelines for uploading" link, usually next to the Register button and usually the most complete statement.
2. The notification or information brochure PDF, if the process has one. This is authoritative when the web page and the PDF disagree, and they do disagree.
3. The tooltip or grey text beside the upload box. Often the only place a minimum is mentioned.
4. The error message itself. "File size should be less than 100 KB" is a real specification, even when the guidelines page said 200 KB.
5. The file picker. A field whose dialog only offers .jpg and .pdf is telling you the whitelist directly.

Then answer three questions that decide how much room you actually have.

Is the cap per file or for the whole application? A portal that allows 2 MB per document and 5 MB per submission will accept your fourth upload and then fail at Submit, with an unhelpful message.

Is there a minimum? This catches more people than the maximum. A clean signature scan at the right pixel size can land at 8 KB, and a form with a 10 KB floor rejects it as corrupt or empty.

Does it check pixels as well as bytes? Photo fields usually do. Document scans usually do not.

The shapes of limits you will meet

Numbers below are the caps these processes have commonly published. Treat them as the shape of the requirement, confirm the digits on the page in front of you, and assume they change between cycles.

Two patterns are worth internalising. Photo fields are small and dimension-checked. Document fields are larger and legibility-checked by a human weeks later. Optimising a document scan down to the byte is how you end up with an application rejected at verification for an unreadable certificate.

KB and pixels are two separate rules

They are related but independent, and confusing them is the most common mistake.

Pixel dimensions set a floor on how small the file can honestly get. A 200x230 photo is 46,000 pixels; as JPEG at high quality that is roughly 15–25 KB, and no setting takes it to 5 KB without visible damage. A 2480x3508 page scan is 8.7 megapixels; asking for 50 KB means throwing away almost everything.

So work out which constraint is binding:

• Dimensions stated, KB generous. Resize to the exact pixels with the Image Resizer and you will usually be inside the KB cap already.
• KB stated, dimensions not. You are free to reduce pixels. For a document scan, 1600 px on the long edge is readable on any screen and a fraction of the size of the original capture.
• Both stated and in conflict. Meet the pixel rule and get as close to the KB rule as quality allows. Then, if you must, drop the scan to grayscale, which removes two of three colour channels and typically 40–55% of the bytes on a black-ink document.

Formats: what portals actually accept

JPEG for photographs and scans. Spelled JPG or JPEG, and the extension normally has to match. Renaming photo.png to photo.jpg does not convert it: the server reads the first bytes of the file, sees a PNG header, and refuses. Convert properly with PNG to JPG.

PDF for documents. Almost always a single PDF per document, even when the document is three pages. Build it with Image to PDF rather than uploading page1.jpg, page2.jpg and hoping.

PNG is rarely on the whitelist. It exists for flat graphics and screenshots, and it is three to six times larger than JPEG for photographic content, which is exactly the wrong property here.

WEBP and HEIC are never accepted. HEIC matters in practice: an iPhone's default format, and the file your gallery shows as a photo arrives as IMG_4021.HEIC that no government upload widget can decode. Convert it before you start.

The order that works

1. Start from the original. The camera file or the scanner output, not the WhatsApp copy, which is already compressed to around 100 KB and softer than it looks on a phone.
2. Crop. Crop Image for the visual decision. On a document, crop to the paper edge: the tabletop and your fingers in a hand-held capture are typically 15–30% of the pixels and 100% wasted budget.
3. Set pixel dimensions. Type the numbers the portal gave; do not drag a handle and eyeball it.
4. Hit the byte target. Enter the maximum in Reduce Image Size in KB. It searches for the highest JPEG quality that still fits, and only reduces dimensions if quality alone cannot get there.
5. Check the floor. If the result is under the stated minimum, run it through Increase Image Size in KB with the minimum as the target.
6. Open the output and read it. The smallest print on the worst page. If you cannot read it, neither can the officer verifying it.
7. Name it plainly. photo.jpg, income_certificate.pdf. No spaces, brackets, second dots or non-Latin characters.

For PDFs the equivalent step 4 is Compress PDF, and the reasons an 18 MB scan got that big are worth understanding once: see why your PDF is 18 MB.

Why a correct-looking file gets rejected

• EXIF rotation. The phone stored the photo sideways with a "rotate me" tag. Your gallery obeys the tag; the portal often ignores it, so your upright photo appears on its side in the preview.
• CMYK JPEG. Anything that passed through a print workflow. Older upload widgets only decode baseline RGB and report "invalid image".
• Real format versus extension. Covered above, and it accounts for a large share of "please upload in correct format" errors.
• Base64 inflation. A few portals validate the encoded payload, which is about 33% larger than the file on disk. A 1.9 MB file then fails a 2 MB check.
• Password-protected or signed PDF. The validator cannot open it, or your changes invalidated the signature.
• Session timeout. The upload succeeded, the session behind it did not, and the page returns you to a form with empty file fields.

If it still fails

1. Re-read the error text literally and compare it with the guidelines page. When they differ, the error wins.
2. Upload a deliberately tiny, plainly valid file, a 30 KB JPEG photo of anything. If that fails too, the problem is the portal or the browser, not your file.
3. Switch browser. Chrome or Edge on a desktop. Several state portals still break on mobile browsers and on Safari.
4. Turn off ad blockers and extensions for that site; content blockers break upload widgets built on older JavaScript.
5. Re-export rather than re-compress. Open the image, save a fresh JPEG from the original, and strip metadata with Remove EXIF. Gallery apps embed a lot of junk, and metadata can be a surprising share of a small file.
6. Try off-peak. Last-date evening traffic causes upload failures that look like file problems.
7. Check the total, not just the file. Remove an optional attachment and try Submit again.
8. Keep a folder of the originals. The next form will want different numbers, and you cannot get quality back out of a file you already crushed to 20 KB.

Everything above runs inside your browser, which matters here more than on most tools: these are precisely the files you should not be emailing to a converter site.

Frequently asked questions

The portal says "maximum 100 KB" but rejects my 99 KB file. Check for a minimum, check whether the limit applies to the whole submission, and check that the file is really a JPEG rather than a renamed PNG. If all three are fine, upload a known-good 30 KB test image to find out whether the field is broken.

Should I reduce the pixel size or the JPEG quality? Quality first, down to about 70%, because that is invisible on a document. Below that, reduce pixels instead: a smaller sharp image beats a large blurry one at the same byte count.

Can I upload three JPGs instead of one PDF? Only if the field accepts multiple files, and most do not. Combine them into one PDF in the page order the portal asks for, and keep it under the per-file cap.

Does DPI matter? Not to the validator. DPI is metadata and says nothing about the image data, so the same 200x230 photo tagged 72 or 300 DPI passes or fails identically. It only matters for converting a size given in centimetres into pixels.