There is no single PDF size limit - each destination publishes its own. The documented limits for email, messaging, website uploads and application portals, and how to get under the one you are facing.
"How big can my PDF be?" has no answer on its own. File size is a property of the file; the limit belongs to whatever receives it, and every receiver draws its own line. The same document can be four times too big for an application form, comfortably under a chat app's ceiling, and rejected by an email server that never states its limit out loud.
So the useful question is narrower: where is this file going? Below are the limits the destinations themselves publish, the ones that are usually stated but rarely noticed, and the order to try fixes in when you are already over.
The limits that are actually published
Every number in this table comes from the provider's own documentation rather than a forum answer, and each source is linked underneath. These are the published limits - a workplace mail server or a university portal can still be configured lower. Work and school Google accounts, for instance, follow an administrator's configured sending limit rather than the personal 25 MB figure.
| Destination | Documented limit | What it means for you |
|---|---|---|
| Gmail (personal) | 25 MB per message | Past the limit, Gmail replaces the attachment with a Drive link. |
| Outlook.com | 25 MB, message included | Body text and attachments share one budget. |
| Outlook desktop, internet mail | 20 MB by default | Exchange mailboxes default to 10 MB, set by the mail admin. |
| WhatsApp (documents) | 2 GB | Messaging is rarely the constraint. |
| Cloudflare (Free and Pro) | 100 MB per request body | Applies to uploads on sites served through Cloudflare. |
| nginx (default config) | 1 MB per request body | A 413 error until an administrator raises client_max_body_size. |
Documented limits, quoted from each provider's own documentation
Website uploads: the limit you never see
Upload forms usually print their cap beside the field - 2 MB, 5 MB and 10 MB are the common round numbers - and then enforce it twice: once in the browser, once on the server. The server-side check is the one that decides the outcome, and it is frequently a default rather than a decision made about your file.
A default nginx installation refuses any request body over 1 MB with a 413 error. Cloudflare, in front of a large share of the web, rejects request bodies over 100 MB on its Free and Pro plans. Neither has anything to do with your document, and both will refuse it regardless of how well written it is.
If the form states no limit anywhere, treat 5 MB as a working assumption until you find the real one. Then read the rejection carefully: "file too large" from the page is a stated cap you can aim at, while a 413 or a timeout that never returns a message is a server default you can only get under.
Application and government portals
Portals that accept applications publish their own numbers, and those numbers are exact rather than approximate: a submission is accepted or it is not. Photographs and signatures are usually capped in kilobytes - the recruitment notifications tracked in GainUtility's own requirement database range from 4 KB to 300 KB - while the document itself, a certificate, a declaration, the PDF you are attaching, is typically capped at a few megabytes.
Those caps are not general advice. They are quoted in the official notification, enforced by the portal, and changed between cycles without warning. The notification, the portal's own message, or the form's helper text is the only authority here - not a blog post, and not this one.
Why a PDF gets big in the first place
A PDF built from text is small. Pages are stored as characters and vector shapes, so a long document can still land well under a megabyte. A PDF that came out of a scanner stores every page as an image, and from there size tracks page count, resolution and colour depth. Almost every size limit is hit by the second kind of file.
The conversions that catch people out
Two counting systems are in use for the same unit, and they disagree by just under 5%. That gap is invisible right up until the moment a file sits exactly on the limit.
| What the message says | What the number actually is |
|---|---|
| 1 MB on an upload form | 1,000,000 bytes - decimal units, the usual convention for limits. |
| 1.00 MB in your file manager | 1,048,576 bytes - binary units, what Windows and macOS display. |
| The gap between them | Just under 5%. A file showing exactly 1.00 MB is already over a 1,000,000-byte cap. |
| A 200 KB cap | 200,000 bytes if the form counts in decimal; a file at 200 KiB is 204,800 bytes, over by 4,800. |
| An email attachment | Base64-encoded for transmission, which adds about a third to the bytes actually sent. |
Bytes behind the labels, and the overhead an email adds
The practical version: aim for 90% of whatever cap you are given. The headroom absorbs encoding overhead, the difference between the two counting systems, and the page you forgot to delete.
Getting under the limit, cheapest fix first
Work backwards from the destination rather than forwards from the file. The order below is the one that keeps the document readable for longest.
- Write down the number the destination states. If none is stated, assume 5 MB until you find one.
- Check the file's actual size in bytes before changing anything.
- Compress the embedded images one level, then re-measure. For a scan, this is usually the whole fix.
- If it is still over, drop the pages that are not being submitted and compress again - a shorter document needs far less compression to fit.
- If the cap is a hard target rather than a ceiling, keep re-measuring until the output lands under it with room to spare.
Split when the cap is small
A 5 MB cap on a 40-page scan is a compression problem only up to a point. Extracting the pages that are actually being submitted shrinks the file before any quality is touched: two pages need far less compression to fit than forty, so the text you keep stays sharp instead of crushed.
When the limit is a target, not a ceiling
Some forms do not reject large files; they reject the wrong ones - a scan below the readable resolution, a document that overshoots a stated maximum by a few kilobytes. An exact target needs a tool aimed at the number rather than simply downwards.
Every tool used above, plus merging, rotating, protecting and converting, sits in one directory. The compress and split pages there carry their own longer guides if you want the detail.