When is compression the right move vs sending the original?

Compress when: file size is the only issue, the recipient does not need lossless quality, and visible quality at typical viewing zoom remains acceptable. Most PDFs containing screen-resolution images compress 40–70% with no visible loss; PDFs with 600 DPI print images can compress 80%+ for screen-only use. Do not compress when: the PDF is destined for high-quality print production (need 300+ DPI source images), it contains forensic evidence where bit-exact fidelity matters, or it is going to be archived as the canonical version of the document. For everyday large-PDF sharing where the file is huge mostly because of embedded high-resolution images, compression usually solves the problem; for files that are huge for legitimate reasons, link-based sharing without compression is the right path.

What is the actual upper limit for email attachments?

Varies by provider. Gmail allows 25 MB attachments; over that, Drive auto-replaces with a link. Outlook.com allows 20 MB. Microsoft 365 (corporate) often allows 35 MB. Apple iCloud Mail uses Mail Drop for >20 MB attachments, uploading to iCloud and delivering a download link valid for 30 days. Yahoo Mail allows 25 MB. ProtonMail allows 25 MB on free, 1 GB attached via secure link on paid plans. For any file over 25 MB, plan to use a link rather than direct attachment regardless of provider — even when the sender's limit allows it, recipient's download experience suffers on huge attachments. The link-based path is the better experience above 25 MB consistently.

How does WeTransfer compare to Dropbox and Drive for ad-hoc large transfers?

WeTransfer's strengths: no account needed (sender and recipient both), generous free tier (2 GB), automatic expiry (7 days) that suits one-off sharing. Weaknesses: no rights management, no preview, files vanish after expiry which is annoying if the recipient is slow. Dropbox and Drive's strengths: persistent storage, version history, preview-in-browser, rights management on Business tiers. Weaknesses: account required for both parties, free tiers have small total storage that fills up. For one-off transfer to someone you may never share with again, WeTransfer is the right tool; for ongoing collaboration where the file matters longer-term, Dropbox or Drive is better.

When should I split a large PDF rather than send it whole?

Three cases. First, for clearer organisation — a 500-page book splits into chapter PDFs that the recipient can navigate naturally. Second, for selective recipient access — different stakeholders get different sections of a comprehensive report rather than all of it. Third, when the recipient's download environment is bandwidth-constrained — mobile-only recipients in low-connectivity areas read smaller files more reliably. Trade-off: a single PDF is one artifact; multiple PDFs are a folder of related artifacts that the recipient has to manage. For most cases, the single-PDF + cover-index pattern works better than splitting; split only when there is a clear reason.

Is BitTorrent really a viable PDF distribution mechanism?

For very large public datasets: yes. Academic data archives, government open-data PDFs at scale, large-format archive distributions all use BitTorrent legitimately. The benefits are bandwidth distribution (recipients share with each other, reducing load on the source) and resilience (no single hosting account can take down the distribution). The constraints are recipient sophistication (BitTorrent is unfamiliar to most non-technical users) and reputational baggage (BitTorrent is associated with piracy in popular perception even though the protocol itself is content-neutral). For private one-to-one sharing, BitTorrent is overkill; for one-to-many distribution of large datasets where the recipients are technically capable, it remains a working solution.

6 min read

How to share huge PDFs (over 100 MB) without losing quality

By ScoutMyTool Editorial Team · Last updated: 2026-05-21

The first time I had to send a 220 MB scanned-archive PDF to a client, I did the obvious thing and attached it to an email — and watched it bounce off Gmail's 25 MB ceiling. I then made the second mistake of compressing it hard, only to have the client come back saying the print plates were unusable. Since then I've settled on a small set of channels that get oversized PDFs delivered intact, and a single decision up front that tells me whether I even need one. Below I map the seven channels I actually reach for, when each is the right tool, and how I decide between compressing and sending the original.

Large-file delivery channels compared

Channel	Size limit	Expiry	Best for
WeTransfer (free)	2 GB	7 days	One-off large files; no account needed
WeTransfer Pro	200 GB	Custom (up to never)	Recurring large files; password-protect option
Google Drive (Workspace)	5 TB per file (Workspace)	None by default; custom	Collaborative workflow; rights management
Dropbox	50 GB Plus; 100 GB Family	Custom on Business	Professional file sharing; expiry-link control
Microsoft OneDrive	250 GB per file (Business)	Custom on Business	Microsoft 365 ecosystem; integration with Office
AWS S3 + presigned URL	5 TB per object	Configurable (1 sec to 7 days for V4-signed URLs)	Developer workflows; programmatic distribution
BitTorrent / WebTorrent	No practical limit	As long as a seeder exists	Distribution of very large public datasets

Step by step — share a 200 MB PDF

Decide if compression is acceptable. If the file is large because of high-resolution images destined for screen viewing only, ScoutMyTool Compress PDF will bring it under 25 MB with no visible quality loss, and you can email it. If the file is large because of legitimate print-resolution content or other fidelity-critical reasons, skip to the link-based path.
For one-off transfer to an external recipient: upload to WeTransfer (free up to 2 GB). Enter recipient email; WeTransfer sends them a download link valid for 7 days. No account setup required for either party.
For ongoing collaboration with the same recipient over time: use Dropbox, Google Drive, or OneDrive shared folder. Drop the PDF in the folder; share the folder link with the recipient. Files persist; revisions stay accessible.
For sensitive content: add password protection to the PDF (ScoutMyTool Protect PDF, client-side) before uploading. Send the password by a separate channel (SMS, Signal). On Business-tier cloud services, also set link expiry (7 days typical) to limit the access window.
Verify the recipient can access the file. Brief follow-up message asking them to confirm download. Catches issues (link broken, password wrong, file corrupted during upload) before the recipient assumes the document is en route and you assume it has arrived.

When the file size is the wrong problem to solve

Sometimes the right move is to question why the PDF is so large. Three diagnostic questions. First, are images embedded at print resolution (300 DPI) when the deliverable is screen-only? Downsample to 150 DPI; file size drops 60–80% with negligible visible difference. Second, are scanned pages still in their high-DPI raw form? OCR them and re-export at lower DPI; smaller file, searchable text. Third, does the file contain unused embedded fonts, hidden layers, or revision history? Sanitise via Acrobat Pro Tools → Redact → Sanitize Document; often shrinks by 20–40%.

For files where the size is justified — high-resolution archival scans, large-format print masters, image-rich design comps — the large-file channels in the comparison table are the right path. For files where the size is incidental rather than intentional, fixing the upstream cause is better than compensating downstream with bigger transfer channels.

FAQ

When is compression the right move vs sending the original?: Compress when: file size is the only issue, the recipient does not need lossless quality, and visible quality at typical viewing zoom remains acceptable. Most PDFs containing screen-resolution images compress 40–70% with no visible loss; PDFs with 600 DPI print images can compress 80%+ for screen-only use. Do not compress when: the PDF is destined for high-quality print production (need 300+ DPI source images), it contains forensic evidence where bit-exact fidelity matters, or it is going to be archived as the canonical version of the document. For everyday large-PDF sharing where the file is huge mostly because of embedded high-resolution images, compression usually solves the problem; for files that are huge for legitimate reasons, link-based sharing without compression is the right path.
What is the actual upper limit for email attachments?: Varies by provider. Gmail allows 25 MB attachments; over that, Drive auto-replaces with a link. Outlook.com allows 20 MB. Microsoft 365 (corporate) often allows 35 MB. Apple iCloud Mail uses Mail Drop for >20 MB attachments, uploading to iCloud and delivering a download link valid for 30 days. Yahoo Mail allows 25 MB. ProtonMail allows 25 MB on free, 1 GB attached via secure link on paid plans. For any file over 25 MB, plan to use a link rather than direct attachment regardless of provider — even when the sender's limit allows it, recipient's download experience suffers on huge attachments. The link-based path is the better experience above 25 MB consistently.
How does WeTransfer compare to Dropbox and Drive for ad-hoc large transfers?: WeTransfer's strengths: no account needed (sender and recipient both), generous free tier (2 GB), automatic expiry (7 days) that suits one-off sharing. Weaknesses: no rights management, no preview, files vanish after expiry which is annoying if the recipient is slow. Dropbox and Drive's strengths: persistent storage, version history, preview-in-browser, rights management on Business tiers. Weaknesses: account required for both parties, free tiers have small total storage that fills up. For one-off transfer to someone you may never share with again, WeTransfer is the right tool; for ongoing collaboration where the file matters longer-term, Dropbox or Drive is better.
When should I split a large PDF rather than send it whole?: Three cases. First, for clearer organisation — a 500-page book splits into chapter PDFs that the recipient can navigate naturally. Second, for selective recipient access — different stakeholders get different sections of a comprehensive report rather than all of it. Third, when the recipient's download environment is bandwidth-constrained — mobile-only recipients in low-connectivity areas read smaller files more reliably. Trade-off: a single PDF is one artifact; multiple PDFs are a folder of related artifacts that the recipient has to manage. For most cases, the single-PDF + cover-index pattern works better than splitting; split only when there is a clear reason.
Is BitTorrent really a viable PDF distribution mechanism?: For very large public datasets: yes. Academic data archives, government open-data PDFs at scale, large-format archive distributions all use BitTorrent legitimately. The benefits are bandwidth distribution (recipients share with each other, reducing load on the source) and resilience (no single hosting account can take down the distribution). The constraints are recipient sophistication (BitTorrent is unfamiliar to most non-technical users) and reputational baggage (BitTorrent is associated with piracy in popular perception even though the protocol itself is content-neutral). For private one-to-one sharing, BitTorrent is overkill; for one-to-many distribution of large datasets where the recipients are technically capable, it remains a working solution.

Citations

Compress before you choose the channel

ScoutMyTool Compress PDF runs client-side. Bring 200 MB files under 25 MB without visible quality loss; many of your large-PDF problems disappear before you reach for a special channel.

Open Compress PDF →