Sharing channels — what each preserves

Step by step — share a 200 MB PDF with quality intact

1. Decide if compression is acceptable. Most 200 MB PDFs compress to 20–40 MB with no visible quality loss; if so, compress with Compress PDF first and use any channel.
2. If the original size is required (legal evidence, print production, archival), skip compression and pick a link-based channel: Dropbox, Drive, or WeTransfer.
3. Generate the share link. Set link expiry (Dropbox Business / Drive / WeTransfer default 7–30 days) — restrict the access window.
4. Password-protect the PDF itself if it is sensitive. Use Protect PDF for client-side AES-256 password.
5. Send the link and password by separate channels. Link via email; password via SMS or Signal. Verify recipient receipt; revoke link after use.

When channels silently degrade quality

A few channels recompress PDFs without telling you. WhatsApp Web on slow connections occasionally proxies file delivery through a transcoder; the desktop and mobile apps do not, but the web client sometimes does. Older corporate email gateways (legacy Cisco IronPort, some Symantec configurations) rasterise PDF attachments for malware-scanning and forward the rasterised version rather than the original; text becomes selectable-pixels and the file size balloons. Social-media direct messages on some platforms convert PDFs to image previews. If you suspect a channel has degraded your file, ask the recipient to email back the file they received and compare its SHA-256 hash with the file you sent. Hash mismatch = quality changed during delivery; hash match = original preserved.

For deliveries where quality must be guaranteed (court evidence, signed contracts, audit-trail records, design proofs), bypass any channel you do not control. Upload to your own controlled share platform (Dropbox Business, S3-backed link, your own cloud storage), share the link, and the recipient downloads the byte-identical file directly from your storage. The added 60 seconds of upload eliminates the entire class of channel-mangling problems.

The link-based delivery also gives you analytics most attachment-based channels do not: timestamp of recipient download, IP origin, browser used. For high-stakes deliveries (legal evidence chain, financial audit responses), this audit trail can matter later. For routine sharing the link is sufficient even without the analytics; the quality-preservation is the main win.

One more pattern worth knowing: PDFs sent through certain messaging platforms can be silently downgraded to "preview-only" versions that disable text selection and search. Recipients see what looks like the file but cannot interact with it normally. The fix is to always send the file as a downloadable attachment or link, never as an inline preview embed. If a recipient reports that selection or search does not work on a PDF you sent, they likely received the preview version; ask them to download the file directly and retry. The recovery is a one-click action on their side, but only if they know to do it.

Related reading

• Share PDFs securely: deeper coverage of password, expiry, watermarks.
• Compress PDF: when smaller-but-clean is better than huge-and-original.
• Send large PDF by email: companion piece on email-attachment workflows.
• PDF email size limits: per-provider attachment caps.
• PDF security guide: password types and encryption tiers.

FAQ

Will WhatsApp / iMessage recompress my PDF?

PDFs themselves are not recompressed by WhatsApp or iMessage — they are delivered byte-identical. What does get recompressed is photos and videos sent as media. So a PDF containing high-resolution images stays intact (the PDF byte-stream is preserved), but if you sent the same images separately as photos, they would be recompressed. If quality matters, always send the PDF, not loose images.

Why does my Dropbox link sometimes show a low-quality preview but download the original?

The Dropbox web previewer rasterises pages to display quickly in a browser, which can look soft compared to the source. The downloaded file is identical to what you uploaded. If recipients complain about quality, ask them to click "Download" rather than judging from the preview. Same applies to Google Drive — preview is rasterised, download is original.

What is the safest way to share a PDF link that expires?

WeTransfer expires links after 7 days on the free tier — no setup needed. Dropbox Business and Google Drive both support custom expiry on shared links (7 days, 30 days, custom). For sensitive files, set the shortest expiry that works for the recipient's schedule, plus password-protect the PDF itself so the link alone is not enough. Send the file link and password through different channels (link via email, password via SMS or Signal).

I sent a 50 MB PDF and it bounced. What now?

Email caps are 20–25 MB in most systems. Three options. First, compress the PDF — most 50 MB PDFs drop to 5–15 MB without visible quality loss. Second, share via Dropbox, Drive, or WeTransfer link instead. Third, use iOS Mail Drop (auto-detected when attaching files over 20 MB in Mail on Mac/iOS — uploads to iCloud, delivers a link that expires after 30 days). Each path keeps PDF quality intact; only the delivery channel changes.

How do I check if a shared PDF arrived as-sent without quality loss?

Compare file hashes. On the sender side: `shasum -a 256 file.pdf` (Mac/Linux) or `Get-FileHash file.pdf -Algorithm SHA256` (Windows PowerShell). Ask the recipient to run the same on the file they received. Matching hashes prove byte-identical delivery. For most workflows this is overkill — assume hash-equal unless the recipient reports visible issues. For high-stakes deliveries (legal evidence, original signed contracts) the hash check is worth the 30 seconds.

Citations

1. ISO 32000-1:2008 — "Document management — Portable document format" — base PDF specification.
2. Dropbox Help Center — shared-link expiry and password documentation.
3. Apple Mail Drop — iCloud Mail Drop attachment delivery documentation.
4. WeTransfer — file-transfer service specification and retention policy.