03 / GUIDES
Get a PDF under an email or portal size limit
A measured approach to oversized PDFs: confirm the real limit and the real file size, choose between structure cleanup and strong raster compression, and tie expectations to what is inside the document.
Measure before you compress
Two numbers decide everything: the limit you must fit and the size you actually have. Guessing either one leads to compressing blindly—and to re-compressing when the first attempt misses.
Keep the two numbers in the same units before comparing them; portals variously state megabytes as MB or MiB, and a file manager that reports one while the portal means the other can hide a five-percent gap.
- Know the limitFind the real limit: email attachments are often capped near 20–25 MB across providers, and portals state their ceiling in the fine print near the upload button.
- Know the sizeCheck the file’s actual size before choosing a strategy; a 26 MB document needs a small win, while a 90 MB scan needs a different plan entirely.
- Leave headroomLeave headroom: aim comfortably under the limit rather than exactly at it, since some systems count encoding overhead or companion files against you.
Try structure cleanup first
The first attempt should cost nothing in quality. Optimize-structure mode removes document metadata and rewrites the file structure—text stays selectable and searchable, and pages render exactly as before.
PDF Compressor accepts one file up to 30 MB and 500 pages, and reports the size before and after exactly as measured. Structure optimization usually wins a modest percentage—enough when the original export carried redundant objects, or when the file only just misses the limit.
If the result comes back no smaller than the original, the workspace says so plainly instead of pretending a win: the file was already well optimized, and only the stronger mode or fewer pages will help.
Open PDF CompressorUnderstand strong raster compression
Strong compression trades text for size: every page is re-rendered as a bitmap image at 150 DPI with an adjustable JPEG quality level. The workspace discloses that trade before you run it, because the consequences are permanent for the exported copy.
Run it on a representative document first. A contract that is mostly crisp text pays heavily in legibility for every saved megabyte, while a phone-scanned stack of receipts sheds most of its bytes before any blur becomes visible.
- Searchability endsText in the result can no longer be selected, copied, or searched; each page becomes a picture of itself.
- Quality is the leverThe quality slider is the size lever: lower quality means a smaller file, with artifacts most visible on sharp text edges and line art.
- Keep the originalKeep the original: the rasterized copy is a submission artifact, not an archive master, and there is no way back to searchable text from it.
Set expectations by content type
What compression can deliver depends on what the file is made of, so judge the two modes against the document’s contents before choosing one.
When even strong compression cannot reach the limit, the remaining lever is the page count: portals rarely need the appendix, the cover letter, and the full archive in one file, and removing pages costs no quality at all.
- Born-digitalBorn-digital documents—exports from word processors and design tools—are mostly text and vector graphics; structure cleanup gains are small, and rasterizing harms crisp text for little reason unless the limit is far away.
- ScansScanned paper is already images, so strong compression re-encodes those pages efficiently and usually delivers the largest reductions.
- Mixed contentMixed reports with embedded photographs sit in between: the images dominate the weight, so raster mode helps, but text sharpness is the cost.
Verify the result before you send it
A compression is not done when the download finishes—it is done when the file opens correctly and reads well at the size the recipient will see.
If the portal offers a preview after upload, use it; what the recipient sees is the only rendering that counts.
- Open itOpen the result and page through it: confirm the page count matches and nothing rendered blank or sideways.
- Read at zoomZoom to normal reading size on a scan; text re-rendered at 150 DPI should stay legible on screen, which is where portals display it.
- Weigh againWeigh the final file once more before uploading, and keep both versions until the submission is confirmed accepted.
Fit compression into the submission flow
When the size limit is one step in a longer preparation—merge the appendices, order the pages, then fit the limit—the PDF submission workspace runs that sequence in one place: arrange pages, fit the limit, verify and export.
It coordinates the same local engines used by the individual tools, so the document moves from raw pieces to a page-correct, limit-fitting submission without a server round trip. As with every local workspace, download the result before closing the tab; there is no cloud copy to fall back on.
Keep the workspace limits in mind as you plan: a source document over 30 MB or 500 pages must be reduced before the compressor will accept it at all, which is one more reason trimming pages comes early in the sequence.
Open the PDF submission workspaceMore PDF jobs, same boundary.
Merge, split, rotate, watermark, and clean PDF files alongside compression—every task runs inside your browser.