A freelancer choosing between an email attachment and a restricted cloud link while checking who can open the file

Editorial illustration.

An email with a large attachment can fail without a useful explanation. Sometimes the sender sees an error; sometimes the message leaves the outbox but the recipient never gets it. The quick fix is often to upload the file somewhere and paste a link. That works only if the link points to the right version and the right people can open it.

This guide is for anyone sending a video, design file, report or folder to a client or colleague. The useful question is not simply “How do I get around the size limit?” It is “Which delivery method fits this file, recipient and level of sensitivity?”

Summary

  • Compress a file when it is a small bundle of items or an image that can tolerate loss; compression will not shrink every format.
  • Use a cloud link for files that exceed a mail service’s limit, change often, or need access to be removed later.
  • Set the narrowest practical permission, test it as the recipient, and state which version is final.
  • Keep confidential material out of public links and use an approved service for work data.

Pick the method before uploading

A compressed attachment is convenient when the recipient needs a fixed copy and the file is not too large. A link is better when the file is large, likely to change, or should not be copied into several inboxes. Neither method is automatically private: an attachment can be forwarded, and a link set to “anyone with the link” can travel beyond its intended audience.

Situation Better starting point Check before sending
A few documents, modest total size Attach them directly Confirm the recipient and file names
Many related documents Create one clearly named archive Tell the recipient what is inside; avoid password-by-email if the contents are sensitive
A video or design export Share a cloud link Restrict access and confirm playback or download works
A document still under review Share a working link Give comment or view access, not edit access by default
Personal, financial or client data Use an approved secure channel Check your organisation’s policy before uploading

Mail limits differ by provider and account type, and a message can become larger when an attachment is encoded for email. Check the limit shown by your mail service rather than relying on an old number from a forum. If a message is only just below the limit, leave room for other attachments and the mail encoding overhead.

A reliable handoff in six steps

1. Confirm what the recipient actually needs

Ask whether they need to read, edit, review or download the file. A client who only needs to approve a PDF does not need editor access to the whole project folder. If they need one deliverable, send one deliverable instead of granting access to a broad folder containing drafts and internal notes.

2. Choose a copy or a live document

If the file should be frozen as a point-in-time delivery, export a final copy such as PDF and label it with a version or date. If the recipient is collaborating on a document that will continue changing, a shared document may prevent conflicting copies. Make that choice explicit: “Review copy, 18 Nov” is clearer than “final-final-new”.

For a compressed archive, remember that compression is useful for groups of text files and some uncompressed assets, but already-compressed photos, videos and PDFs may barely shrink. Do not lower image or video quality blindly just to force a smaller number; export a separate delivery copy and retain the source.

3. Upload only the intended material

Before uploading a folder, scan its contents. Remove temporary exports, hidden working files, credentials, customer records and drafts that the recipient should not see. A shared folder can carry broader permissions than the individual file settings, so inspect both levels. Google’s Drive guidance specifically notes that a parent folder’s permissions can override a file’s own sharing settings.

4. Give the least access that still lets the job happen

For a review, choose viewer or commenter access. Grant edit access only when the recipient must change the file. Prefer named people or a known work group where practical. “Anyone with the link” is convenient for a public handout, but it is a poor default for invoices, identity documents, contracts or unpublished customer work.

Some work or school accounts allow access to expire on a chosen date. If that control is available, set an end date for a temporary handoff and put a reminder in your own calendar to review access. If it is not available, decide when you will remove the recipient manually.

5. Test the link from the recipient’s point of view

Open the link in a private browser window or ask a colleague who is not already signed in to the same account. This catches two common mistakes: the link opens only for the sender, or it opens a folder broader than intended. Do not test by changing an important original file. Use a harmless copy if you need to verify edit rights.

For a large video, check that the link opens and that playback or download begins. A successful upload does not guarantee the recipient can access the file on a phone or a restricted work network.

6. Send a short, useful note

Include the file name, what action you need, the deadline if there is one, and whether the linked version will change. For example: “Please review Campaign-brief-v2.pdf by Thursday. This is a view-only copy; I’ll send a new link if the approved content changes.” That small note reduces the chance that someone replies to the wrong version.

If the recipient still cannot open it

First, ask what exact message they see and whether they are using the intended account. Then check the share list, parent-folder permissions and link type. If access should be limited to a named account, verify the email address character by character. If the recipient’s employer blocks an external service, use a channel approved by both organisations rather than switching to a personal account without checking.

If the service reports that the file exceeds its own upload limit, split an archive only if the recipient can reassemble it, or export a smaller delivery version. Do not split sensitive documents across unrelated consumer services just to get around a limit. For work data, the right next step may be asking IT or the client for an approved transfer method.

Mistakes that create extra work

  • Making a public link because it is faster. A link can be forwarded; use named access for private work.
  • Sharing the parent folder. That can reveal drafts or give broader access than the file requires.
  • Sending a link without naming the version. The recipient may review an old file from a previous email.
  • Assuming compression equals encryption. A ZIP file is not automatically protected; use an approved encrypted transfer process for sensitive data.
  • Deleting the source after upload. Keep the original until the recipient confirms the handoff and your retention rules allow deletion.

If your team shares many deliverables, a small folder convention helps. The shared project file guide explains how to keep the current draft distinct from approved output. For cloud folders, the cloud file safety checklist is a useful reminder to review ownership and access before sharing.

My Take

A file transfer is complete when the right person can open the right copy with the right permission. The few seconds spent testing a link are usually cheaper than resending a document, exposing a draft or finding out on a deadline that the recipient cannot get in.

Conclusion

Use an attachment for a small, fixed copy; use a restricted link when size, collaboration or revocable access matters. Before sending, inspect the contents, set permission, test the link from outside your own account and identify the version in your message. If the file is sensitive, follow the approved channel for that data rather than improvising around a mail limit.

Sources