A PDF proposal, project photographs or campaign materials often reach a client by email. For a small team, choosing between an attachment and a download link affects delivery, confidentiality and time spent resending files. There is no universal size limit for large files: you need to consider both parties’ email services and how the message is prepared.
1. When to attach a file and when to send a link
An attachment suits a relatively small, final document that the client should be able to keep alongside your message. A straightforward proposal or product sheet may be easier to read directly, without signing in to another service.
A link is often more practical for high-resolution photographs, collections of documents, video or files that will change. Instead of sending several large copies, you direct the client to a location where the materials can be downloaded.
- Choose an attachment when the document is small, final and expected in that format.
- Choose a link when files are large, there are many of them or you need to manage access afterwards.
- Check the client’s requirements if their organisation blocks external services or requires a particular transfer method.
Neither option is automatically safer. The content, recipient and permissions all matter. An attachment can be forwarded, while a public link can reach people it was never intended for.
2. Why the sender’s limit is not the recipient’s limit
Your email service may accept a message that the client’s server rejects. Limits vary between providers and may apply to the whole message, individual attachments or a particular sending method. Your email application may also impose its own restrictions.
At the receiving end, other rules can apply: maximum message size, available mailbox space, permitted file types and security filters. A message appearing in your sent folder does not confirm that it has reached the client’s inbox.
Encoding makes the message larger
Binary attachments are usually encoded for email transport, commonly using Base64. This adds roughly a third to the size of the data, before accounting for headers, separators and the message itself. The file size shown on your computer is therefore not the same as the size of the transmitted email.
If an attachment is already close to the stated limit, the complete message may exceed it. Several smaller attachments also add up. Check whether the service’s documentation describes a file limit or a total message limit, and leave some room rather than working right up to it.
For questions about the service you use, consult the available documentation or the frequently asked questions. If you receive a delivery failure notice, read the reason before trying again: reducing an attachment will not fix an incorrect address.
3. Prepare your files before sending
Before looking for a transfer service, establish what the client actually needs. Images optimised for viewing may be sufficient for approving a concept, while printing or further editing may require the originals. Do not reduce quality without understanding the purpose.
- Select the relevant materials. Remove duplicates, working versions and internal documents.
- Use clear filenames. Include the project and version, without unnecessary sensitive information in the filename.
- Optimise a copy. Resize images or export a more compact PDF, keeping the original separately.
- Check the output. Open exported files and review readability, page content and image quality.
- Look for hidden information. Comments, tracked changes and metadata may contain details that should not be shared.
An archive can keep several documents together, but it will not always make them significantly smaller. JPEG photographs, many PDFs and video files are already compressed. Some organisations also block certain archives, particularly encrypted ones that security filters cannot inspect.
4. How to share a link with restricted access
Choose a file-sharing service that suits the materials and your team’s rules. Uploading files to an online location does not automatically make them private. Check explicitly who can open the link and what they can do once they have access.
Permissions, expiry and access checks
- Invite named recipients using their email addresses, if supported, rather than allowing anyone with the link to open it.
- Grant only the permissions needed: viewing or downloading, without editing unless it is necessary.
- Set an expiry date, where the service supports it, and tell the client when access ends.
- Add a password if the option is available and appropriate; share it through a separate channel.
- Check access before sending using the service’s permissions preview or an authorised test identity.
A link that works while you are signed in may not work for the client. Conversely, a link that opens in a private browsing window without authentication may indicate public access, but that check alone does not establish that every setting is correct.
Expiry and revocation stop future access through that link, subject to how the service works; they do not delete copies already downloaded. Restricting downloads cannot prevent every form of copying either. For sensitive information, follow your internal rules and agreements with the client.
If you are considering a team-managed solution on cloud infrastructure, assess the sharing application, updates, authentication and access management separately. The infrastructure does not configure these measures automatically.
5. Give your team a simple routine
A short internal procedure helps prevent colleagues sending different versions or relying on personal accounts. Decide where final materials are stored, who manages access and when active sharing links should be reviewed.
In the client’s email, explain what the package contains, which version you are sending and whether signing in is required. Include the expiry date and explain what the recipient should do if they cannot open the materials. Avoid vague messages containing nothing but a link.
If delivery fails, review the notification and confirm the address. For email attachments that are too large, switch to a sharing method the client accepts rather than repeatedly sending the same message. If you need clarification about GazduireOnline.ro services, use the contact page.
6. Conclusion: keep delivery simple and check access
Keep attachments for small, settled documents, and use a link with appropriate permissions for large files. Check both email services’ limits, account for encoding overhead and test access before sending. Finish with one straightforward check: are you sending the correct version to the right person through a channel they can use?
