NOTE 01
When email refuses your attachment
Gmail caps a message at 25 MB, Outlook typically 20 MB, and most corporate mail gateways are stricter still. A folder of design exports blows past that in one click. The usual workaround — "let me zip it" — fails too, because a zip barely compresses PNGs, video, or already-compressed PDFs.
Three things actually work, in this order of preference. First, send a preview instead of the master: a 200 KB JPG of page one settles 90% of "did you get the file" conversations. Second, send a link if the recipient needs the whole thing — a link costs nothing in the inbox and the file does not have to live forever. Third, split the archive into parts only when someone genuinely needs all of it offline, because reassembling parts is a support ticket waiting to happen.
The reason a link works better has nothing to do with size. It is that a link has a deadline. When you attach a file, you are silently promising to be the archive for it. When you send a 24-hour link, the file manages itself.
NOTE 02
The 30-second checklist before you paste a link
Almost every accidental leak we hear about follows the same shape: the right file, the wrong link, one second of inattention. Five checks make that shape much rarer.
- Open your own link first. Not the share page you just saw — the actual URL, pasted fresh. Ten seconds of friction catches the wrong file far more often than memory does.
- Read the filename as a stranger would. "final_v3_REAL.pdf" tells the recipient nothing. "acme-invoice-2026-11.pdf" tells them whether to open it at all.
- Check the corners of screenshots. Browsers, chat windows and notification banners leak client names, internal URLs and occasionally an email address. Crop or blur before uploading, not after.
- Match the expiry to the audience. An internal review link that lives a week is a link that gets forwarded twice and outlives the decision. A one-hour link is usually enough for a handoff.
- Do not reuse a link across two audiences. Same file, two links: one for the client, one for the contractor. It costs nothing and keeps the download counts honest.
NOTE 03
Choosing an expiry window that matches the task
An expiry is not a security setting — the link is already unguessable. It is a lifecycle decision: how long should this object exist in the world? Four patterns cover almost everything.
- One hour — the live handoff. You are on a call, someone needs the deck now. A short window means the link is dead before anyone forwards it to a group chat.
- Twenty-four hours — the default, and usually the right answer. Long enough for a client in another timezone to wake up and download it, short enough that nobody treats the link as permanent storage.
- Three days — over a weekend or a review cycle. When a document needs to survive a Friday-to-Monday gap without becoming a fixture.
- Seven days — reference material with a known end. A supplier price list, a conference handout, a temporary asset pack. Still a deadline, just a calmer one.
If you are unsure, pick the shorter window. Re-sharing costs one drag; an over-long link costs a conversation two months later about why a competitor’s draft is still downloadable.