Quick answer
A finished project can still miss its deadline if the recipient cannot open the delivery link. Repeatedly uploading the same files to different services creates extra copies without explaining the failure. First establish whether the problem is the link, the file or the company’s access policy.
Is the company blocking the link, or has the transfer failed?
Ask the client what appears when they open the link and whether they can see the file list. The wording matters more than a general report that it does not work.
- A company or security message appears. Ask the recipient to send the message to their IT team, including the time and any reference number. Do not assume a category restriction means your files contain malware.
- The transfer page says it has expired. Check the collection deadline. Arrange a fresh delivery from your retained source files if needed.
- The page opens but a file will not download. Record which file fails and the exact error. This is different from the entire website being blocked.
- The browser shows a certificate or security warning. Stop and ask IT or the service’s support team to investigate before proceeding.
Check your own completed transfer link and confirm that you copied it in full. Ask whether the recipient received that same link. A successful check on your device does not establish that their company permits the service. For a rejected email attachment rather than a website block, use our large email file guide.
Why would a company block a legitimate file sharing site?
Organisations can restrict categories of websites as well as particular addresses. Microsoft’s web content filtering documentation explains that even non malicious websites may be restricted for compliance, bandwidth or other reasons. Policies can apply to managed devices away from the office as well.
That means moving the same work laptop to another connection may not change the restriction. It also means that access decisions belong to the organisation. Ask the client’s IT team to identify the policy and decide whether access is appropriate.
What information should you give the client’s IT team?
Make the request specific enough to investigate. Your client can forward this checklist through their normal support channel:
- The delivery service and the exact link, shared privately with the authorised support team.
- The project purpose, expected filenames, formats and total size.
- The error text, time of the attempt and any incident or reference number.
- Whether the page opens, previews work or the failure happens only during download.
- The collection deadline and the person who needs the files.
Redact unrelated personal information from screenshots. Do not post a private transfer link or a screenshot containing it on a public forum. If IT requests technical details you cannot verify, ask the transfer service’s support team rather than guessing.
What can you say without making the client feel at fault?
Keep the conversation focused on delivery. Adapt this example to the actual project:
Thanks for letting me know. The final files are ready, but it looks as though your company’s access rules may be preventing collection. Could you send the exact message to your IT team and confirm the approved way for me to deliver them?
I can provide the file list, total size and collection deadline. If your team prefers its own upload portal, please send the authorised destination and any access instructions. I will confirm once the delivery is complete.
For example, if a designer needs to deliver a 12 GB campaign folder tomorrow, the useful decision is whether IT can approve the existing link in time or provide an approved upload destination. Sending five replacement links is unlikely to settle that decision.
Where does HeftySend fit once access is approved?
HeftySend gives you a practical delivery page with supported media previews and downloads without a recipient account. If your client approves it, prepare the final files, finish the upload and share the completed link with a clear collection deadline. Our free transfer walkthrough covers the sending steps.
The free plan allows up to 20 GB per transfer with three days of availability. HeftySend does not charge for bandwidth usage. Paid plans add custom download pages and longer availability; Premium currently includes up to 1 TB per transfer and 365 days at $9 USD per month. Check the current plans when choosing a collection period. If you use your own storage, your provider’s charges remain separate.
See the download page guide for recipient options. Branding, password protection and a paid subscription do not guarantee that a corporate network will permit access. Confirm the actual delivery route with the client.
How do web filters make these decisions?
Cloudflare’s video explains how a secure web gateway filters and inspects internet traffic. It provides background for the conversation with IT, rather than instructions for changing your client’s settings or a test of HeftySend.
Frequently asked questions
Should I use a shortened link?
Use the original transfer link so the client and IT can identify the destination. A shortened address does not establish approval and can make investigation harder.
Will buying a paid plan remove the company block?
Do not upgrade for that reason alone. A plan can change delivery limits and features, while the recipient’s organisation controls its own access rules.
Can the client use personal email or a personal device?
Ask the client to confirm what their organisation permits for those files. Do not suggest moving company material to personal accounts as a workaround.
What if the client needs the files urgently?
Ask for an approved upload portal or another authorised delivery method, then agree a realistic deadline. Keep the source files ready so you can act when the destination is confirmed.
Does a working preview mean the client has received the files?
No. Ask them to confirm that the required originals have downloaded and open correctly. A preview alone is not a completed handover.
Should I rename a blocked file extension?
No. Tell IT the actual file type and purpose. Renaming a file to conceal its type makes the handover less clear and does not resolve the underlying approval requirement.
Once the delivery method is agreed, keep the handover simple: one clear link, the right files and a confirmed collection deadline.
Checked on 2 October 2026 using current product information and the linked technical documentation. The campaign example is illustrative, not a report of a customer test.