Government and job portals reject oversized PDFs every day. Limits vary—100 KB on strict forms, 200–500 KB on many education uploads, a few MB on tax/immigration systems—but the fix is the same: understand whether your file is text-heavy or a scan, then compress in the browser with PDFUtilKit before you submit. This pillar guide covers typical ceilings, a merge-then-compress workflow for certificate packs, and why client-side processing matters for ID-adjacent documents. Always read the portal’s own size text; numbers below are common patterns, not universal law.
Common portal limits (typical — verify on the form)
Use this as a planning table. Exact caps change by agency, state, and recruitment cycle.
| Scenario | Typical limit | Notes |
|---|---|---|
| Strict India exam / some state forms | 100–200 KB | Often JPEG photos separate; PDFs tightly capped |
| Many job / education portals | 200–500 KB | Scanned certificates are the usual problem |
| Broader agency uploads | 1–2 MB | Still crush multi-page phone scans |
| US tax / some federal flows | Often multi-MB | Readable text > tiny file vanity |
| Email to an agency desk | ~10–25 MB mailbox rules | See compress-for-email guide |
| WhatsApp document share | App/chat practical limits | See WhatsApp PDF guide |
Workflow: merge certificates, then compress
Applicants often upload a single PDF of multiple certificates. Build the packet deliberately:
- Collect: Gather clear scans or digital PDFs of each certificate.
- Pre-compress: Shrink noisy phone scans individually if one page dominates size.
- Merge: Combine into one packet with Merge PDF when the portal wants a single file.
- Final compress: Run Compress PDF and verify KB in your file properties.
- Fallback: Split non-essential pages or re-scan at lower DPI if still oversized.
- Merge PDF — build the packet
- Combine certificates guide
- Compress PDF — final size pass
- 100 KB deep-dive
Scanned vs digital PDFs
Born-digital PDFs (exported from Word) usually compress well because text is vector. Phone scans are images wrapped in PDF—those need image downsampling. If compression barely moves the needle, you are fighting a huge image. Re-scan at 150–200 DPI, crop margins, or compress the image first then wrap with Image to PDF.
Step-by-step with PDFUtilKit
Client-side compression keeps ID and marksheet PDFs on your device while you hit a size target.
- Open: Go to the Compress PDF tool in Chrome, Edge, Firefox, or Safari.
- Add file: Drag-and-drop your PDF — processing stays in the browser.
- Choose setting: Use a stronger preset if you must hit 100–200 KB; check stamps/signatures.
- Verify: Download and confirm OS-reported file size before portal upload.
- Tighten: If rejected, follow the 100 KB or 200 KB guides for stricter tactics.
When compression fails
Already-optimized exports, encrypted PDFs, or single-page scans at extreme resolution can resist further shrinkage.
- Unlock encrypted PDFs first if your reader allows, then recompress.
- Remove blank pages before compressing.
- Split a huge packet and upload only what the form requests.
- Re-photograph documents square-on with even light instead of crushing a dark photo.
Privacy for ID-adjacent documents
Marksheets, ID scans, and offer letters are sensitive. Upload-based compressors require trusting a remote server with the original. PDFUtilKit’s compressor is designed to process locally so the first time a government portal sees the file is when you submit it. This is not legal advice—just a practical reason to prefer on-device tools for personal documents. See the privacy & benchmarks guide for architecture notes.
Related size targets
Jump to the matching long-tail guide when the portal states an exact ceiling:
Compress your government PDF now
Open Compress PDF and shrink the file in your browser before you upload to the portal.