Compress any JPG, PNG, or WebP to exactly 30KB in seconds. The ideal size for EPFO/PF portal, PMAY housing scheme, municipal & ULB portals, Skill India, DigiLocker, and university admissions. EXIF metadata stripped automatically. No signup. 100% browser-based.
JPG · PNG · WebP — any file size accepted
In the architecture of India's digital governance ecosystem, image file sizes do not form a smooth continuum — they cluster around specific thresholds dictated by database field definitions, API payload limits, and the generation of software used to build each portal. If you map all the photo size requirements across Indian government digital services, you will notice a clear gap between 25KB and 50KB where 30KB sits as a precise bridge point.
Below 30KB (the 5–25KB range) live the systems built for biometric identity infrastructure — Aadhaar, voter ID, financial KYC — where millions of records must be stored and transmitted over constrained connections. Above 30KB (the 50–100KB range) live the systems built for examination and high-fidelity document workflows — UPSC, SSC, IBPS — where photo quality must survive printing on admit cards and document verification.
The 30KB zone — roughly 25KB to 35KB — serves a distinct third category: welfare scheme portals, civic service platforms, and educational admissions systems. These systems were predominantly built between 2015 and 2020 under the Digital India initiative, using moderate-cost cloud hosting with database columns sized for the practical middle ground. EPFO's member portal, PMAY's beneficiary management system, state municipal corporation portals, and central skill development databases all fall in this category. They need photos clear enough to identify a beneficiary during physical verification, but small enough to handle millions of applications without storage problems.
30KB delivers near-print-quality for a standard 200×230px photo. At this size, JPEG compression typically runs at 75–88% quality — well above the threshold where blocking artefacts become visible to the naked eye. A 30KB photo printed on a welfare scheme card, housing allotment document, or skill certificate looks professionally photographed, not digitally degraded.
| File Size | JPEG Quality (200×230px) | Visible Artefacts | Print Quality | Typical Portal Category |
|---|---|---|---|---|
| 10 KB | ~30–40% | Moderate blocking, skin banding | Poor — pixelated on print | Biometric identity (Aadhaar, voter) |
| 15 KB | ~45–58% | Mild blocking in backgrounds | Acceptable — faces readable | Financial KYC (CKYC, VKYC) |
| 20 KB | ~55–68% | Minimal — only in hair edges | Good — clear on screen | Passport, GeM, IRCTC |
| 25 KB | ~65–78% | Almost none | Very good — exam admit cards | NEET, JEE, state police |
| 30 KB ★ | ~75–88% | None visible | Near print quality | EPFO, PMAY, municipal, skills |
| 50 KB | ~88–94% | None | Excellent | Banking exams (IBPS, SBI) |
| 100 KB | ~95–99% | None | Original quality | UPSC, SSC, modern portals |
The following section covers the most significant Indian government welfare, civic, and educational digital platforms that commonly accept or require photos in the 25–35KB range. Unlike exam portals (which specify exact sizes) or KYC systems (which enforce tight limits), these portals often give a range — and 30KB is the practical optimum within that range.
The EPFO Unified Member Portal (unifiedportal-mem.epfindia.gov.in) is one of India's most-used employee welfare portals, serving over 7 crore active EPF members across 6 lakh+ establishments. The portal handles UAN (Universal Account Number) activation, KYC linking (Aadhaar, PAN, bank account), EPF withdrawal claims (Form 19, 31, 10C), pension scheme transfers, and passbook access.
Members activating their UAN for the first time, or employers registering new employees on the EPFO Employer Portal (unifiedportal-emp.epfindia.gov.in), must upload a profile photograph. EPFO's photo upload module has historically specified photos in the 20–50KB range, JPEG format. A 30KB JPEG photo passes EPFO's file validator cleanly and provides sufficient face clarity for identity verification during claim processing — particularly important for high-value claims where EPFO field officers may need to match photos with applicant identities.
Beyond the main portal, EPFO's UMANG app integration (EPFO is one of the highest-used services on the Government of India's UMANG super-app) and Common Service Centre (CSC) portal for assisted KYC updates also accept photos in this size range. Workers in unorganised sectors accessing EPFO for the first time through CSC operators benefit from pre-compressed 30KB photos that upload reliably even on the CSC's shared broadband connections.
The Pradhan Mantri Awas Yojana (PMAY) — split into PMAY-Urban (for cities, managed by Ministry of Housing and Urban Affairs) and PMAY-Gramin (for villages, managed by Ministry of Rural Development) — is India's flagship housing scheme targeting housing for all by 2024. With over 4 crore houses sanctioned, it is one of the world's largest housing programmes by scope.
Beneficiary registration under PMAY-Urban uses the PMAY-U portal (pmaymis.gov.in), where applicants and urban local body (ULB) operators upload photographs for the beneficiary master database. PMAY-Gramin uses the AwaasSoft system (rhreporting.nic.in) maintained by NIC, where Gram Panchayat-level operators upload household photographs and beneficiary portraits.
Both systems accept photographs in the 20–50KB range. Since PMAY photos are often uploaded by ULB officers or Common Service Centre operators on behalf of beneficiaries, and since rural areas may have bandwidth constraints at data entry points, 30KB strikes the ideal balance — small enough for fast uploads on low-bandwidth connections, large enough for the housing authority to use the photo for site visits, document verification, and beneficiary identification during construction progress monitoring.
India's 4,000+ Urban Local Bodies — comprising Municipal Corporations (Nagar Nigam), Municipal Councils (Nagar Parishad), and Town Panchayats (Nagar Panchayat) — provide civic services through online portals that increasingly require citizen photographs for identity verification. Key ULB services requiring photos include:
New property registrations, ownership transfers, name changes, and mutation entries in municipal property tax records frequently require the property owner's photo on state-level urban property portals. Photo limits of 20–50KB apply across Maharashtra (Aapli Yojana), Karnataka (UPOR portal), Tamil Nadu (TNEB-linked municipal systems), and others.
Municipal trade licence applications for shops, restaurants, street vendors, and small businesses require the applicant's photograph. The PM SVANidhi (Street Vendor microfinance scheme) portal — which operates through urban local bodies — also requires vendor photographs in the 20–50KB range.
Civil Registration System (CRS) portals used by municipal birth/death registrars in several states now allow online correction and certified copy applications with photo identity uploads. State CRS portals specify photos in the 20–40KB range.
The diversity of ULB portal software across India's 4,000 urban bodies means file size specifications vary. However, the practical overlap — the size that works on virtually all ULB portals — is the 25–40KB range. A 30KB JPEG is the single most universally compatible size for any municipal portal photo upload in India.
India's skill development ecosystem encompasses several major digital platforms, all of which require learner and trainer photographs:
DigiLocker (digilocker.gov.in), India's national digital document wallet with over 25 crore registered users, serves as the official repository for digitally issued government documents — Aadhaar, driving licences, PAN cards, educational certificates, vehicle registration certificates, and more. When citizens set up their DigiLocker profile, they can upload a profile photograph. Additionally, certain DigiLocker-integrated services require uploading photographs as supporting documents alongside official certificates.
DigiLocker's profile photo upload module and its document upload interface for citizen-uploaded documents (as opposed to government-issued documents pulled from source databases) specify file sizes in the 20–50KB range. A 30KB JPEG is the optimal choice — it loads quickly in the DigiLocker mobile app (used heavily on 4G connections), renders clearly in the profile view, and easily satisfies the system's file validation.
Multiple central government self-employment and entrepreneurship support schemes operate online portals that require applicant photographs:
India's open and distance learning system, serving over 40 lakh students, uses online admission portals that specify photo sizes in a range where 30KB is consistently accepted:
The National Food Security Act (NFSA) beneficiary management system and state-level ration card portals have been digitising rapidly under the One Nation One Ration Card (ONORC) scheme. Several state food departments now allow online ration card applications, member additions, and corrections through citizen portals (like UP's fcs.up.gov.in, Maharashtra's mahafood.gov.in, and Bihar's sfc.bihar.gov.in). These portals require applicant photographs in the 20–50KB range for beneficiary identity management.
When a JPEG image is compressed too aggressively, it develops characteristic visual defects called compression artifacts. Most people recognise them as general "blurriness" or "ugliness" but cannot name what they are seeing. Understanding the three distinct types of JPEG artifacts — and knowing at what compression level each appears — helps you choose the right file size target for your specific use case and explains precisely why 30KB is such a robust target.
Visible as a grid of 8×8 pixel square patches across the image. Caused by JPEG's block-based DCT compression becoming too coarse — each block is quantized so heavily that neighbouring blocks show visibly different colour tones. Most noticeable in smooth gradient areas like blue skies, skin in shadows, and solid-colour backgrounds. Appears at JPEG quality below 35–45% (roughly below 12–18KB for a 200×230px photo).
Appear as bright or dark halos around sharp edges — particularly visible around hairlines, the boundary between face and background, and the edges of text overlays at the bottom of photos. Caused by the Gibbs phenomenon in DCT reconstruction — high-frequency edge information is truncated, creating oscillating side-lobes. Visible at JPEG quality below 50–60% (roughly below 18–25KB for a 200×230px photo).
A buzzing, dancing texture around fine detail — particularly around text, thin lines, hair strands, and eyelashes. Named for its resemblance to a swarm of tiny insects when viewed at full resolution. Caused by insufficient bit allocation for high-spatial-frequency coefficients during quantization. Appears at JPEG quality below 55–65% (roughly below 20–26KB for a 200×230px photo).
At 30KB for a standard 200×230px passport photo, the JPEG quality setting typically lands between 75% and 88% — well above the threshold where any of the three artifact types become visible:
This is the fundamental reason 30KB is described as "near print quality" for standard passport photo dimensions. It is not marketing language — it reflects the precise mathematical threshold above which all three human-perceivable JPEG artifact types become invisible at normal viewing distances. Below 30KB (at 25KB), artifacts are technically absent in most photos but may appear in high-complexity source images. At 30KB, you are in the clear regardless of source image complexity.
Every photo taken by a modern smartphone or digital camera contains hidden metadata embedded within the JPEG file called EXIF (Exchangeable Image File Format) data. This metadata is invisible when you view the photo — it does not affect the image itself — but it is readable by any software that parses JPEG headers, including government portal servers, HR systems, and anyone who downloads your photo.
When you submit a photo to an EPFO portal, a PMAY beneficiary system, a municipal corporation portal, or a university admission system, the server receiving your file may log, store, or process this hidden metadata alongside your photo. For government welfare scheme photos in particular — where beneficiaries may include individuals in vulnerable situations — the GPS location data embedded in smartphone photos represents a genuine privacy concern.
| EXIF Data Category | Specific Fields | Privacy Risk | Our Tool |
|---|---|---|---|
| GPS Location | GPSLatitude, GPSLongitude, GPSAltitude, GPSTimeStamp, GPSAreaInformation | 🔴 High — reveals exact home address | ✓ Stripped |
| Device Identity | Make (phone brand), Model (exact model), Software (OS version) | 🟡 Medium — device fingerprinting | ✓ Stripped |
| Capture Time | DateTime, DateTimeOriginal, DateTimeDigitized, SubSecTime | 🟡 Medium — reveals daily routine | ✓ Stripped |
| Camera Settings | ExposureTime, FNumber, ISO, FocalLength, Flash, MeteringMode | 🟢 Low — technical info only | ✓ Stripped |
| Image Technical | PixelXDimension, PixelYDimension, Orientation, ResolutionUnit | 🟢 Low — non-personal | ✓ Stripped |
| Thumbnail | Embedded JPEG thumbnail (miniature of original) | 🟡 Medium — contains original uncompressed mini-image | ✓ Stripped |
| Creator Info | Artist, Copyright, ImageDescription, UserComment | 🟡 Medium — can contain personal notes | ✓ Stripped |
| Image Content (pixels) | The actual visible photograph data | 🟢 Required for photo | Preserved |
Our tool uses the browser's HTMLCanvasElement.toBlob('image/jpeg', quality) method to produce the compressed output. This method creates a new JPEG file from the pixel data rendered on the canvas — it does not carry forward any EXIF metadata from the source file. The process works as follows:
ctx.drawImage(). The canvas only captures pixel colour values — EXIF metadata is not part of the pixel data and is therefore not transferred to the canvas.canvas.toBlob('image/jpeg', quality) creates a brand-new JPEG file from the canvas pixel data. This new file contains only the image pixels, standard JPEG headers, and colour space information — no EXIF tags are included by the browser's Canvas API.After downloading your compressed 30KB photo, you can independently verify that all EXIF data has been removed:
While most users of this tool are individuals compressing one photo for a portal submission, a significant number of users are HR managers, administrative officers, CSC operators, and municipal staff who need to compress dozens or hundreds of employee/beneficiary photos to 30KB as part of a bulk upload workflow. This section provides professional guidance for handling high-volume photo compression efficiently.
A frequently overlooked cause of photo upload failure is incorrect file naming. Government portals have strict file naming rules that are documented in their technical specifications but rarely communicated clearly to applicants. Here are the naming conventions that apply across most Indian government portals:
| Naming Rule | ✅ Correct Example | ❌ Incorrect Example | Why It Matters |
|---|---|---|---|
| No spaces in filename | ram_kumar_photo.jpg | ram kumar photo.jpg | Spaces break URL encoding on portal servers |
| Lowercase only | epfo_photo.jpg | EPFO_Photo.JPG | Case-sensitive Linux servers reject uppercase extensions |
| Extension must be .jpg (not .jpeg) | applicant.jpg | applicant.jpeg | Many portals only accept the 3-character extension |
| No special characters | singh_photo_2026.jpg | singh's-photo(2026).jpg | Brackets, apostrophes and hyphens cause parser errors |
| No leading numbers (some portals) | photo_9876543210.jpg | 9876543210.jpg | Some CMS systems reject files starting with digits |
| Meaningful name for identification | uan_12345678901_photo.jpg | compressed_30kb.jpg | Helps during bulk upload verification and audit |
Before uploading a batch of compressed photos to any government portal, verify each file against this checklist. Catching errors before upload saves the time-consuming process of rejection and re-submission:
.jpgOur browser-based tool processes one file at a time. For small batches (up to 20 files), the most efficient workflow is:
IMG_20260315_142035.jpg. If it says "WhatsApp Image" in the name, find the original.compressed_30kb.jpg. Rename it per your portal's naming convention before uploading.applicantname_documenttype.jpg — for example ram_kumar_photo.jpg or uan_12345678901_photo.jpg. Avoid spaces, capital letters, special characters like brackets or apostrophes, and do not start the filename with a number. Our tool downloads as compressed_30kb.jpg — rename this before uploading to your specific portal.