Compress Image Under 100 KB for Forms
Aadhaar, PAN and most state portals reject anything over 100 KB. A practical walkthrough that works on any device, with nothing to install.
To get an image under 100 KB for a government portal, crop it, resize the longest edge to about 600 pixels, then set a 100 KB target and let the compressor pick the quality. 100 KB is a generous limit, so a correctly resized photo lands near 60 KB to 80 KB and still looks like a photograph. Most rejections happen because phone cameras now produce 4 MB and 5 MB files by default, which is 40 to 50 times over the cap.
100 KB is the most common upload limit across Indian government services, including Aadhaar update requests, Permanent Account Number (PAN) applications, state land record portals, pension and scholarship systems, and most municipal service forms. The number is consistent enough that preparing one 100 KB copy of your photograph and identity documents saves repeated work.
Where the 100 KB limit applies
100 KB is the default cap for photographs and scanned documents on most central and state portals. Signatures on the same forms are usually held to a tighter 10 KB to 20 KB.
| Portal type | Photo cap | Document scan cap | Format |
|---|---|---|---|
| Aadhaar update and enrolment | 50 KB to 100 KB | 100 KB to 500 KB | JPG or PDF |
| PAN application | Under 50 KB | Under 300 KB | JPG or PDF |
| State scholarship portals | 100 KB | 100 KB to 200 KB | JPG or PDF |
| Pension and welfare forms | 100 KB | 200 KB | JPG or PDF |
| Land and revenue records | 100 KB | 500 KB | JPG or PDF |
Caps change without notice, and the official instruction sheet is usually the only reliable source. Check the numbers printed beside the upload button before you prepare files, because a portal that accepted 200 KB last year may accept 100 KB today.
Why a phone photo fails a 100 KB limit
Phone cameras save 12 megapixel images by default, and 12 million pixels cannot fit in 100 KB. The camera is optimised for printing and cropping, while the portal only needs enough pixels to show a face in a small box on screen.
A portal typically displays a photograph at around 200 by 230 pixels, which is 46 thousand pixels. Your camera supplied 12 million. The portal is asking you to remove data it was never going to display, and a resize does exactly that without any visible cost.
How to compress an image under 100 KB
To bring any photograph or scan under 100 KB, work through these 6 steps.
- Crop the image to the shape the form needs, removing table edges, fingers and background from scanned documents.
- Resize so the longest edge sits near 600 pixels for a photograph, or near 1240 pixels for a full document page that must stay readable.
- Convert HEIC or PNG sources to JPG, because JPG is the only format every government portal accepts without exception.
- Set 100 as the KB target so the compressor searches for the highest quality that fits.
- Check the output for readability, particularly small printed text on scanned documents.
- Rename the file to something plain such as photo.jpg, since some older portals reject spaces and special characters in filenames.
Working in that order usually lands between 60 KB and 80 KB with the photograph still looking natural. Reversing the order, by compressing first and resizing afterwards, wastes quality that cannot be recovered.
Scanned documents need more pixels than photographs
A scanned document must stay readable, so keep the longest edge near 1240 pixels rather than 600. Text becomes unreadable long before a face does, and an unreadable document is rejected during verification even when the upload succeeds.
Scan at 200 to 300 DPI in greyscale where colour is not required. Greyscale removes two of the three colour channels and typically cuts file size by 40 to 60 percent with no loss of readability on a black and white document. Colour is only necessary when the document carries a coloured seal, stamp or signature that a verifier needs to see.
Why browser processing matters for identity documents
An Aadhaar card, PAN card or passport scan uploaded to an unknown compression website is an identity document handed to a stranger. Most online compressors send your file to a server, process it there, and return a download. The retention policy is a promise you cannot verify.
Our compressor runs entirely inside your browser using your own processor. The file is read by the page, resized and re-encoded locally, and written back to your disk. No request carries the image, so there is nothing on a server to retain, leak or subpoena. You can confirm this yourself by opening developer tools, switching to the Network tab, and watching that no upload request appears while a file is compressed.
JPG or PDF for a document upload
Upload JPG when the portal accepts either, because a JPG can be compressed to an exact KB target and a PDF cannot. PDF is only the better choice when a single upload must carry several pages, such as a multi page certificate or a bank statement.
A PDF produced from a phone scanning app usually embeds the photograph at full camera resolution, which is why those files arrive at 3 MB to 8 MB. Compressing the image first and building the PDF from the compressed image gives a far smaller result than compressing the finished PDF. When the portal accepts both, converting the pages to JPG and uploading them separately avoids the problem entirely.
Working on a phone with no computer
The full workflow runs in a mobile browser, because the processing happens on the phone rather than on a server. Applicants filling government forms are frequently doing so on a phone at a service centre, with a slow connection and no software they are allowed to install.
Open the tool in Chrome or Safari, tap the drop zone, and choose the photo from the gallery. An iPhone will offer a HEIC file, which converts to JPG in the same step. Because no upload occurs, a weak or intermittent connection does not interrupt the work, and a 5 MB source photograph does not have to travel over mobile data before it can be compressed.
The 5 errors that cause rejection
- File over the cap. Set an explicit KB target rather than guessing at a quality percentage.
- Wrong dimensions. Portals check pixel size separately from file size, so both numbers must match.
- HEIC from an iPhone. Government portals do not decode HEIC. Convert to JPG first.
- Renamed file. Changing a .png extension to .jpg does not convert the file, and the server reads the actual file header.
- Dark or angled scan. A photograph of a document taken at an angle is often rejected during manual verification even when the upload passes.
Preparing a full application in one batch
Most applications need 4 to 6 files, so prepare all of them before the form opens. A typical set includes a photograph, a signature, an identity proof, an address proof, an education certificate and a category certificate.
Drop all the files in together, set the target once, and every file comes back under the cap with its own quality calculation. Batches of up to 500 images are supported, and a ZIP folder can be dropped in directly, which helps when documents are already collected in one place.
Keep the compressed set in a clearly named folder on your device. The same photograph and identity proof are requested again by the next portal, the next scholarship renewal and the next verification round, and a folder of files already sized to 100 KB turns a 40 minute task into a 2 minute one. Application windows close on fixed dates, and having every file sized correctly in advance removes the most common reason a submission fails in the final hour.