Table of contents
A 40 MB PDF is not normal — here is what causes itFind out which one is your problemHow small is realisticThe fix, without wrecking readabilityIt might not be a size problem at allOn a Mac? Skip Preview's blunt instrumentA 40 MB PDF is not normal — here is what causes it
A one-page contract should be a few hundred kilobytes. A ten-page scanned application should not be 60 MB. When a PDF is dramatically larger than its page count suggests, the cause is almost always one of a small handful of things: high-resolution scans, embedded photos at full camera resolution, print-quality export settings, or — less obviously — dozens of duplicate or blank pages nobody removed.
Compression works by removing genuinely unnecessary data and, for most files, reducing the resolution or quality of embedded images. That tradeoff is normal and expected. The real question is never "how small can this get" — it is whether the result is still readable for whoever needs it next.
Find out how much you can actually save
Run a duplicate of the file through the Compress PDF tool and compare the result before touching anything else.
Find out which one is your problem
Check whether the PDF is scanned. If you cannot select any text and every page looks like a photograph, the file size is coming from page images, not text or fonts.
Look for large embedded photos, charts, or full-bleed backgrounds — reports and portfolios get heavy fast when images are left at full resolution instead of being sized for the page.
Check the page count against what you actually need. Blank pages, duplicate scans, and instruction sheets a scanner picked up by accident all add size without adding value.
Compress a copy and compare. If it barely shrinks, the file may already be reasonably optimized, or it may contain content compression genuinely cannot reduce much further — some vector graphics and fonts fall into this category.
How small is realistic
A single-page PDF from a word processor is usually under 1 MB by default — text and fonts do not take up much space. A multi-page color scan is a different story entirely: a single page scanned at 300 DPI in full color typically runs 3-6 MB before any compression, and a ten-page scan of the same quality can reach 40-60 MB.
If a portal or form demands a strict target like "under 1 MB" for a scanned, multi-page document, treat it as a genuine tradeoff between size and visual quality, not a target you can always hit without compromise. Getting there usually needs more than compression alone — grayscale instead of color when color is not required, and cropping out large blank margins before rebuilding the file, both help meaningfully.
The fix, without wrecking readability
Duplicate the file before touching anything — compression can soften image quality, and you want an untouched copy available if the result is unusable.
Remove pages that do not belong: blank scanner pages, duplicate receipts, cover sheets picked up by accident.
Compress with a balanced setting first. Reserve the strongest setting for cases where you have a hard size ceiling to hit, since it is the setting most likely to introduce visible artifacts in scans and photos.
Review the result at both normal zoom and a closer zoom — small print, stamps, and signatures are where over-compression shows up first.
It might not be a size problem at all
A large share of "file too large" upload errors are not actually about size. Browser upload limits, portal session timeouts, unusual characters in a file name, and network interruptions all produce a generic error message that looks identical to a genuine size rejection.
Before compressing further, try uploading a small, unrelated test file to the same form. If that also fails, the problem is the portal or your connection, not your PDF. If only your file fails, size or format is the more likely explanation — and a simple file rename, using only plain letters, numbers, and hyphens, occasionally fixes what looks like a size error.
On a Mac? Skip Preview's blunt instrument
macOS Preview has a Reduce File Size option under File > Export as PDF, but it applies the same aggressive downsampling to every image in the document regardless of what that image actually is. For a document that mixes dense text with embedded photos, this often makes text noticeably softer than a purpose-built compressor would. Duplicate the file in Finder, run it through a browser-based compressor instead, and check the result in Preview afterward rather than using Preview to do the compressing itself.
Get your PDF down to a usable size
Compress it, check it, and know exactly why it was big in the first place.
FAQ
Are scanned PDFs always large?
Not always, but they are typically larger than text-based PDFs because each page is stored as an image rather than text and fonts.
Can compression fix every oversized PDF?
No — some files need page removal, image resizing, or a different export workflow instead of, or in addition to, compression.
Can every PDF realistically get under 1 MB?
No. Long or image-heavy scans often cannot hit 1 MB without a visible quality tradeoff.
My PDF is under the stated limit but still gets rejected — why?
Check for a session timeout, unusual file name characters, or a network issue before assuming it is still a size problem.
Does Preview on Mac compress PDFs well?
It can, but it applies the same downsampling to every image regardless of content, which often softens text more than a dedicated compressor would.