PDF still too large to upload? A practical size-limit checklist
GlobePDF ·
A smaller PDF is only useful if it meets the upload limit and still contains a readable, complete document. Work through size, quality, and portal checks in that order.
1. Check the actual limit before changing the file
Read the instructions beside the upload field. Write down the maximum file size, accepted format, page limit, and any filename or paper-size requirement. Check whether the limit applies to each document or to one combined PDF. A file that fits a size limit can still fail a different requirement.
Use bytes when the recipient provides an exact number. GlobePDF’s Compress PDF workspace uses decimal presets: 200 KB means 200,000 bytes, and 1 MB means 1,000,000 bytes. In Advanced settings, check “Exact limit in bytes,” particularly after loading saved settings.
A rounded file-size label is not enough near the cutoff. For example, a PDF containing 200,400 bytes exceeds a 200,000-byte limit, even if your file manager displays approximately 200 KB. This example illustrates rounding; it is not a compression benchmark. If the portal only says “200 KB,” start with the 200 KB preset and verify the recipient’s requirements if it still fails.
2. Keep the original and try the least destructive option
Keep an untouched original. In Compress PDF, choose your PDF, set File size limit, and leave Priority on “Keep text and links” for the first attempt. Select Compress PDF, then read the result and any checks that need attention.
This mode rewrites the PDF structure without the image-conversion fallback used by smaller-file modes. It can help some documents, but an already efficient PDF may barely shrink or may be returned unchanged. The setting is a starting point, not a promise that every document feature will survive or that a particular size is achievable.
Digitally signed PDFs need special care: rewriting a signed file can invalidate its signature. If the tool detects a signature field, it asks before creating a copy. A detected field is not proof that a signature is valid, and this workflow does not validate signatures. If the recipient requires the signed original, ask them how to handle the size restriction before altering it.
3. Decide whether a smaller file is worth the quality tradeoff
If the first attempt misses the target, consider what the recipient needs from the PDF. A scanned page is often mostly an image. A document exported from a word processor may contain selectable text, clickable links, or form fields. Those features matter when somebody needs to search, copy, navigate, or complete the document.
The “Smaller file,” “Much smaller file,” and “Smallest file” priorities may turn pages into images. This can reduce size, but text selection, links, and forms can be lost. Try a less aggressive option first and compare the result with the original. Stronger settings are not automatically better for your submission. With a size target set, the tool can try more aggressive passes to reach it, so inspect the output even when you choose “Smaller file.”
If selectable text is required, enable “Require selectable text on every page” in Advanced settings and inspect the result. This check is not an accessibility audit or a guarantee that an application system can read the document correctly. A scanned document may not contain selectable text to begin with; compression alone does not add OCR.
4. Review the downloaded copy, not just the success message
Open “Preview before and after” and check the small text, page edges, stamps, and other details that matter to the recipient. Review every page, especially mixed documents where one page is a sharp export and another is a faint scan. Then download the output and open that exact file in your PDF viewer.
Check that all required pages are present, in the right order, and readable at a normal viewing size. Try selecting text, opening links, or using form fields if those features are needed. Confirm the filename and exact size of the file you will upload. Keep the original and compressed copy clearly named so you do not accidentally submit the wrong one.
“Size limit met” describes the configured size check. It does not mean the receiving portal has approved the file. “Download PDF anyway” lets you save a result with failed checks; it does not override the portal’s requirements. Read the checks that need attention before deciding whether that output is usable.
5. If it still fails, fix the specific problem
Still above the limit: if you have the source document, try exporting a new PDF with smaller source images rather than repeatedly compressing an already degraded copy. If you are scanning again, improve lighting and framing so the content is clear before reducing image quality. Never remove required pages just to meet a size target.
Too many pages or separate upload slots: split the document only if the recipient accepts separate PDFs. If one combined file is required, splitting does not satisfy that requirement. Ask the recipient about an alternative upload method when the complete, readable document cannot fit.
Below the limit but rejected: re-read the portal’s exact error. Check its accepted format, filename rules, password restrictions, page count, and any required document standard. Simply renaming another file to end in .pdf does not convert it into a PDF. Use PDF Doctor for local checks, but do not treat those checks as portal certification or PDF-standard validation.
Unreadable at the required size: stop lowering quality. A tiny file that hides important information is a failed outcome. Keep your readable original and ask the recipient whether they allow a larger file, separate documents, or a different submission channel.