PDF too large for a portal
A portal error is a diagnosis problem before it is a compression problem. Confirm that file size is the failing rule, then make the smallest change that produces an accepted, readable document.
Identify the failed rule
Copy the portal’s exact error before changing the document. “Too large,” “invalid file,” “upload failed,” and “unsupported document” can point to different problems even when they appear at the same upload step.
Compare the PDF’s byte size with the current field limit and check file type, page count, password protection, filename characters, and whether the portal accepts one combined file or several attachments.
- ■Exact error message saved
- ■File size compared in bytes
- ■PDF opens without a password
- ■Filename uses simple characters
Change one variable
If the file is genuinely over the stated limit, keep the source and create a separately named compressed copy. Changing one factor at a time makes it easier to understand whether size or another rule caused the rejection.
If the document is already under the limit, try the portal’s supported browser, a shorter filename, or a fresh login before degrading quality. Do not repeatedly compress a file when size is not the failing condition.
Finish on the receiving site
After compression, inspect every page and retry the upload. A successful local download does not prove the receiving system accepted or correctly processed the document.
If the portal continues to fail, save the stated rule, time, browser, and error. Contact the receiving organization for its approved alternative rather than emailing sensitive documents to an unverified address.
- ■Compressed copy has a new name
- ■Critical details remain readable
- ■Portal reports upload success
- ■Submission receipt is retained
Put the limit first
Run one local compression pass, then inspect every page before submitting.
Open the compressor →