You finally finished scanning your certificates. The portal says “Upload PDF (max 200 KB)”—or 500 KB, 1 MB, 2 MB—and your file is 4.8 MB. Or it accepts the size but rejects the upload because pages are in the wrong order, the file is password-protected, or each photo is a separate attachment when they wanted one merged PDF.
This guide is for that moment. It focuses on phone-first workflows: using what you already have (Camera, Files, Photos) plus a browser converter when you need merge, reorder, page size, and compression without installing a heavy desktop app.
These are the failure modes that show up again and again on admission, scholarship, KYC, and job portals.
What portals usually care about
Most upload rules boil down to a handful of checks:
- File type — almost always PDF (sometimes JPG only for a photo field).
- Maximum size — commonly somewhere between about 100 KB and 2 MB for document packs; photo fields may be smaller.
- Page size / dimensions — A4 is common for multi-page sets; ID slots may want a specific aspect.
- Page count and order — e.g. application form first, then ID, then certificates.
- No password / no encryption — locked PDFs often fail silently.
- Readable text or clear scan — blurry phone photos get human rejection even when size is fine.
If you only shrink the file but ignore order or clarity, you can still get rejected.
Step 1: Capture better before you compress
Compression cannot invent detail that was never in the photo.
- Light: Face a window or use even indoor light; avoid harsh flash glare on glossy certificates.
- Angle: Shoot straight-on; skewed pages waste pixels on background and look unprofessional.
- Fill the frame: Crop clutter in your gallery app before converting.
- One page per shot unless the portal explicitly wants a single photo of a spread.
- Prefer the document scanner mode in Google Drive, Microsoft Lens, Adobe Scan, or your phone’s built-in scanner if you have it—these flatten perspective better than a casual Camera roll shot.
Save or export as clear JPG/PNG first. You will turn them into PDF next.
Step 2: Decide page size on purpose
Portals that generate printable packets often expect A4 (common outside the US) or Letter. Fitting a tall phone photo onto A4 with huge white margins is fine for readability; stretching a wide panorama into a square page is not.
Rules of thumb:
- Multi-page academic / government packs: A4 or Letter, portrait, consistent margins.
- Single ID image fields: sometimes the portal wants JPG, not PDF—read the label.
- “Fit to image” helps when you only need one photo per page and do not care about standard paper size—but some portals are picky about dimensions, so prefer A4/Letter when unsure.
Tools that let you pick page size before export save a re-upload cycle. In JPG to PDF Mobile you can choose A4, Letter, Legal, or fit-to-image and use ID-oriented presets when you are preparing Aadhaar/PAN/passport-style pages.
Step 3: Merge and order pages before you shrink
Portals that say “upload a single PDF” will reject a ZIP of images or five separate files.
- Collect every page as an image.
- Sort them in the exact order the instructions list (form → ID → proofs is a common pattern).
- Merge into one PDF.
- Only then compress.
Reordering after heavy compression is possible but annoying; order first while thumbnails are easy to read. Drag-to-reorder in a mobile browser is usually faster than renaming IMG_0042.jpg by hand.
Step 4: Compress without making it unreadable
Size limits force a trade-off between clarity and kilobytes.
Practical approach:
- Downscale megapixel photos. A 12 MP phone image is overkill for a portal that displays a stamp-sized preview. Resizing the long edge to roughly 1500–2000 px often cuts size dramatically before PDF encoding.
- Use JPEG quality carefully. Start around a medium quality setting; if the PDF is still over the limit, lower quality slightly or downscale more. If text becomes muddy, undo and try fewer pages per file if the portal allows multiple uploads.
- Avoid double-encoding traps. Exporting a PDF, screenshotting it, and re-PDFing again softens text. Convert once from the best originals you have.
- Skip fancy filters. Heavy contrast on already-scanned pages can add noise and size.
If the limit is extremely tight (~100–200 KB for several pages), use fewer pages, grayscale, or a second compress pass. Always zoom into small text (dates, seal numbers) before submitting.
Step 5: Common rejection reasons (and fixes)
| What you see / what support says | Likely cause | What to try |
|---|---|---|
| “File too large” | Over max KB/MB | Downscale → lower JPEG quality → re-export PDF |
| “Invalid format” | DOC/HEIC/PNG when PDF required | Export real PDF, not a renamed extension |
| Blank or corrupt on their side | Password-protected or unusual encryption | Re-save without password |
| “Upload failed” with no message | Network timeout on big file | Compress more; retry on stable Wi‑Fi |
| Human reject: “not clear” | Blur, glare, cropped edges | Reshoot, then compress less aggressively |
| “Wrong document” | Page order / missing page | Re-merge in listed order |
| Accepts PDF but wants photo | Field expects JPG | Upload image to that field only |
Also watch filename rules (some portals dislike spaces or non-English characters) and session timeouts on slow mobile networks—generate the PDF offline, then upload on Wi‑Fi.
Phone workflow checklist (print-friendly)
Use this as a pre-flight list:
- [ ] Read the portal’s max size, type, and page-order instructions twice.
- [ ] Reshoot any page that is blurry or glare-heavy.
- [ ] Crop backgrounds in Photos/Gallery.
- [ ] Order images exactly as required.
- [ ] Merge to one PDF with intentional page size (A4/Letter unless told otherwise).
- [ ] Check total size against the limit.
- [ ] If over limit: resize images → reduce quality → export again (once).
- [ ] Open the PDF and verify every page is upright and readable.
- [ ] Confirm the file is not password-protected.
- [ ] Upload on stable Wi‑Fi; keep the PDF until you see a success receipt.
When a browser tool helps
Built-in phone “Print → Save as PDF” is enough for a single image. It gets awkward when you need many pages, reordering, consistent A4, and size control in one place—especially on a phone where desktop apps are not installed.
A browser-based converter that runs on-device is useful here: you stay on the phone, keep sensitive IDs off random servers, and can iterate on compression without emailing files to yourself. If you want to convert JPG to PDF on your phone with merge, reorder, page size, and compression controls, that flow matches the checklist above.
For official rules, always trust the portal’s own help text over any blog—including this one. Portal limits change by season (admissions) and by form.
Quick FAQ
Compress or merge first? Merge and order first, then compress (or resize sources and merge once).
Smaller always better? No—under the limit with readable text beats a tiny blurry file.
Portal wants separate files? Skip merging; use the same capture and compression habits per file.
Closing
Portal uploads fail for boring reasons: too many megabytes, wrong container, scrambled page order, or unreadable scans. Fix capture quality first, set page size deliberately, merge in the documented order, then compress just enough to clear the limit. Keep the final PDF until the status page confirms success. When instructions and file size disagree, the instructions win.
Top comments (0)