How to Send a Large PDF to a Client: 6 Methods Compared

If the document is under 50MB and you would rather know how far the client got than wonder, create a free tracked link — 50 files, 50 active links, 12 months of history, no card — or open the live demo to see the per-reader readout on sample data first. The rest of this page is the comparison, including the sizes that put your file out of our reach.

All 6 compared: the ceiling, the effort, and what you learn afterwards

A transfer service is built for size and nothing else, and it is also the route that tells you the least about what happened next. The second and third columns below are where the real trade sits: what the client has to do, and what you know an hour after they opened it.

Two of these routes are free, familiar and report essentially nothing about a PDF, and one of them is free at a scale nothing else here approaches — 15 GB free with every Google account, against 500MB on our free plan. That is not a flaw in Drive; it is a storage product doing storage, and a client who already lives in Google needs no new account and no explanation from you. It is simply the wrong instrument if the question you will have on Thursday is whether the client reached the scope section.

What actually breaks, and at what size

The number people quote is 25 MB, and it is right for one mail provider. Google states the limit for a personal Gmail account plainly — “the limit is 25 MB” — and its help page also describes the workaround it applies for you: “If your total attachment size is greater than the limit, Gmail automatically removes the attachment and adds it as a Google Drive link in the email.” On a work or school account the ceiling is whatever the administrator set, which is why two colleagues on the same domain can disagree about it in good faith.

Microsoft's numbers are lower and there are two of them. Its own troubleshooting article states that Outlook 2013 and later have “a default attachment size limit of 20 megabytes (20480 KB)” for Internet email accounts, and that on an Exchange Server mailbox the error appears by default once “the sum total of the attachments is greater than 10 MB (10240 KB)”. So a 15MB proposal can leave your outbox, sail past your own client's consumer address, and bounce off their employer's Exchange server — which is the version of this problem that costs a day, because nothing failed on your side.

There is a second ceiling nobody quotes. Attachments are re-encoded into text for transport, which makes them measurably bigger on the wire than they are on your disk, so a file comfortably under a stated limit can be refused anyway. Treat a published limit as optimistic, and if you are within a few megabytes of it, send a link.

Method 1 — send a tracked share link

The document stays on a host you control and the client gets a URL. This is the only route on the page where the answer to “did they read it” still exists a week later, because the file renders in a viewer rather than landing on a disk. Three tools do this on a permanent free plan.

Method 2 — a cloud-drive link

Upload to the drive you already pay for, right-click, copy link, paste. The ceiling stops being a per-message limit and becomes your storage quota, which for most people means the problem simply disappears: 15 GB free with every Google account, and Dropbox's free tier is Dropbox Basic — 2 GB, free. For an ongoing client relationship that already runs out of a shared folder, this is usually the right answer and the rest of the page is over-engineering.

The cost is specific rather than vague. On Drive, Activity dashboard covers only work/school-owned files, and any viewer can hide their own view history — and the Activity dashboard covers Docs, Sheets and Slides rather than a PDF stored in Drive. On Dropbox, Dropbox owns DocSend, and page-level reading lives in that separate product on a separate bill rather than in the share link you just sent.

Method 3 — a file-transfer service

Upload, get a link, the recipient downloads, the link expires. This is the least friction to set up — no account needed at either end — and size is the whole problem the category exists to solve. What this page cannot give you is a figure for where that ceiling sits; the paragraph below says why. When the file genuinely is enormous — a full print pack, a set of scans, a video walkthrough bundled beside the PDF — this is the honest answer and no reporting feature makes up for a route that cannot carry the file.

What you give up is everything after the download. You will typically learn that a download occurred and, on some services, when — and nothing about whether the document was opened, let alone read. The second cost is the expiry: the link that was convenient in March is a dead end in June, which is a real problem for a document a client is meant to refer back to.

Why no transfer service has a row of its own in the table above. We hold no dated, sourced fact for WeTransfer's, Filemail's or Smallpdf's ceilings or tiers, and this project's rules do not let an article publish a competitor number that has not been read from the vendor's own page through an approved channel. A shorter table beats a row we could not source, so the category is described here and given no cells.

Method 4 — compress the PDF first

Compression keeps the attachment workflow intact: the client still gets a file in their inbox, exactly as before. It works by throwing away resolution: images are downsampled and re-encoded, and the size falls by a proportion that depends entirely on what is inside the document. A text-heavy proposal barely moves. A photograph-heavy brochure can fall by most of its size, and it will look like it.

The decision rule is simpler than the tools make it look. If the file is a little over the ceiling and nobody is going to print it, compress it and move on. If it is several times over, or if the client is going to send it to a printer, compression is a trap: you will lose quality and still be over the limit. Use a link instead.

A smaller attachment is still an attachment, and an attachment reports nothing back — which is the whole subject of sending a PDF without attaching it, if the attachment itself is what you want to get rid of.

Method 5 — attach it anyway, and read the bounce

Sometimes this is correct. If the file is genuinely under every ceiling in the chain, an attachment is the least friction that exists for the client: it is in the message and needs no click. For a signed one-page invoice, everything else on this page is ceremony.

The failure mode is that the chain has more links than you can see: each hop applies its own ceiling, and the lowest one wins. Outlook's error is the useful one to recognise because it names the fix in the same breath — “The file you're attaching is bigger than the server allows. Try putting the file in a shared location and sending a link instead.” When you see that, stop optimising and change route.

The quieter failure is worse: a message that leaves cleanly and is silently stripped or quarantined downstream, so you believe it was delivered and the client believes you never sent it. Nothing in your sent folder distinguishes that from success — a link produces a record of arrival, an attachment only a record of dispatch.

Method 6 — split the document into parts

Splitting a 60-page report into three messages gets each one under the ceiling and requires no new tool, no new account and no explanation. It is the right answer in exactly one situation: the recipient's systems block links, transfer services and cloud drives alike, which is common inside government, healthcare and some financial institutions.

Everywhere else it moves the work onto the client. They now hold three files that have to be opened in the right order, they will refer to “the second one” in a reply you have to decode, and a version update means reissuing all three. And, like every attachment-based route here, it reports nothing back.

Where these beat us

Four specific things, each bounded to the dimension it wins on.

A file-transfer service beats us on ceiling, outright. If the file is 900MB there is no argument to have: our ceiling is 50MB free and 250MB on Pro, we cannot carry it, no setting changes that, and a transfer service is what that job wants. We publish no figure for where that category's own ceiling sits, because we hold no dated read of one. That win is bounded to size and does not extend past the download, where those services stop reporting and a tracked link does not.

Google Drive beats us on capacity and on adoption. 15 GB free with every Google account — thirty times the 500MB on our free plan — and a client who already uses Google needs no new account, no unfamiliar domain to trust and no explanation from you. That win is bounded to reach and capacity: it does not extend to what happens after the file opens, where the Activity dashboard covers Docs, Sheets and Slides rather than a PDF stored in Drive.

Peony beats us on alert timing, free. included on every tier, Free first means a Peony sender on the free plan knows the instant a client opens the document; ours reports it in the next morning's digest and reserves the real-time alert for Pro. If you follow up by phone within the hour, Peony closes that gap for nothing.

Papermark beats us on deployment control and on file types. Its open-source code lets a firm that cannot put client reading data on someone else's server run the product itself, and its free plan takes PDF, Notion pages, images and spreadsheets where ours takes PDFs. PDFTrackr is a hosted service with no self-hosted option — a real limit for that specific firm rather than a general weakness.

When Pro becomes the right choice

Free is the product here, not a trial of it. Page-by-page reading, the per-reader verdict on your first document, the email gate, the password, the expiry, the download switch and 12 months of history all sit on the free plan. On this topic the trigger is a number rather than a feeling: Pro is what you buy the first time a document you have to send is between 50MB and 250MB, which in practice is the day a designed brochure or a scanned pack arrives and free simply will not take the file. The second trigger is running out of room rather than reading data — deleting old links to make space, or passing 50 files — which moves you to 10GB, 500 files and unlimited active links. The third is timing, and at $9 a month it is the cheapest of the three to justify: if knowing within the hour rather than the next morning changes how you follow up, that is the gap Peony closes on free and ours closes on Pro. Full limits are on the pricing page.

Which one to use

PDFTrackr is the pick when the file is under 50MB, the client is named, and the follow-up depends on how far they read — one link per client, page-by-page reading, a per-reader verdict in plain English on your first document, 12 months of history, free. Above 250MB it is not a candidate at any price and a transfer service is the honest answer. If your firm cannot put client reading data on a third-party server, use Papermark and host it yourself. If knowing within the hour matters more than knowing next quarter, use Peony. If the client already works out of a shared folder with you and nobody needs a reading record, Google Drive or Dropbox is the answer that costs everyone the least. And if the file is a little over the line, nobody will print it and the client just needs it in the message, compress it and send the attachment.

Pick by which sentence you would rather be able to say next week: “the file went through” or “the client read eleven of the fourteen pages and stopped at the fee schedule.”

How we evaluated these — and who is missing

The two mail-server ceilings above are quoted from Google's and Microsoft's own published help documentation, read on 19 Aug 2026, rather than repeated from other roundups. The competitor storage, retention, price and alert cells in the table above each render from a stored vendor fact, read from that vendor's own pricing or help page on 12–18 Aug 2026, in a browser or from raw HTML rather than a summarised fetch. The “what the client does” column is our own one-phrase summary of each route's access model, not vendor wording.

What is missing, and why. The live results for this search are led by WeTransfer's support article, Smallpdf and pdf.net, with Wondershare, FlippingBook and FlipLink behind them. None of them has a row in the table: we hold no dated vendor fact for any of them, and this run had no route to fetch one through a channel this project's rules accept for a ceiling or a tier. Adding those facts is a vendor-refresh job for a session with a browser, not something to look up inline — so the transfer-service category is described in Method 3 and given no cells. For the wider free-tool ranking see the free PDF tracking tools we compared.

Keep reading: how to share a PDF without sending it as an attachment, how to see who downloaded your PDF, and PDFTrackr's free tracking plan. Or start from the free plan and send one link today.