Why Your Recipient Can't Open a File
Diagnose account, invitation, access, expiry, and preview problems without weakening confidentiality settings.
On this page (7 sections)▼
“I can't open the file” can mean a blocked identity, an expired URL, an incomplete gate or a preview that cannot render. Each needs a different fix.
Begin with the visible symptom and the specific sharing URL. Keep confidentiality settings in place while diagnosing the cause; switching to a public link can hide the problem while introducing a larger one.
1. Find the stage where access fails
Ask the recipient for the error wording, the time of the attempt and the browser or device used. Have them describe the screen without sending passwords, verification codes or confidential document contents.
Determine whether they reached the page at all, reached a gate, or opened the viewer but saw no usable preview. Confirm they are using the current URL from the sender, not an old bookmark.
| Symptom | Recipient check | Sender check |
|---|---|---|
| Page does not load | Reopen the complete current URL | Confirm the link exists and is active |
| Identity blocked | Use the intended email | Compare the saved allowed addresses |
| Agreement screen remains | Complete the required step | Check agreement configuration |
| Viewer opens, preview fails | Note the affected file and device | Check processing and supported format |
| Access recently stopped | Report the time and message | Inspect expiry and other limits |
2. Compare the recipient identity
The address used to receive an invitation may differ from the account active in the browser. Ask the recipient which identity they entered or selected. Compare it with the approved address, including spelling and the intended corporate account.
SendNow documents several independent causes of blocked links, including expired access, view limits and an address missing from the allowlist. Use its current troubleshooting guide to match the symptom. SendNow: Recipient access troubleshooting
If a verification message does not arrive, check the mailbox's junk folder and organizational mail handling. Do not solve the issue by asking the recipient to send their code back to you. Escalate persistent delivery problems with non-secret diagnostic details.
3. Check permissions and gates in order
Review the settings on the exact URL. Check password, agreement, recipient restrictions, expiry and view limits individually. A recipient may clear one gate and still be blocked by the next.
If the file is inside a room, verify its folder permissions and any independent direct-file URL. The sender's owner access is not evidence that an external identity has the same permissions.
Correct a genuine configuration mistake with the project owner's approval. Keep deliberate restrictions intact. If the deadline has passed, a renewal decision is different from fixing a broken viewer.
4. Separate preview problems from access problems
When the gate succeeds but the content does not render, inspect the file itself. Check that the upload completed, the file is not empty, and its format and size are supported by the chosen service. Compare the local source with the uploaded release. SendNow: Supported formats and limits
Try a harmless file of the same format to isolate the workflow. Test another supported browser or device when appropriate, documenting the difference. For media, identify playback failure separately from permission failure.
Do not convert a signed PDF, flatten a workbook or re-export a presentation merely to make the preview load without considering what that transformation would remove. Offer an approved alternative format only after checking the reader's actual need.
5. Retest and close the support loop
After the change, use a recipient session to repeat the failing step. Ask the recipient to confirm they can reach the intended content. A saved setting alone is not a complete outcome.
Record the original symptom, change made, test result and final URL. If support is needed, provide the file type, relevant link reference, error and time through an approved support channel. Share sensitive identifiers only where necessary.
A useful reply says what changed and what the recipient should do next. Avoid sending several conflicting URLs without explaining which one is current.
Frequently asked questions
Why does the link work for me but not the recipient?
Your owner session may bypass recipient restrictions. Test the approved external identity and the actual URL rather than using the administrative preview alone.
Should I turn off every security setting?
No. Identify the failing gate and correct the specific issue while keeping the intended access policy.
Can a file open locally but fail online?
Yes. A local application and a hosted preview may support different formats or features. Check the provider’s supported-file documentation and the uploaded release.
Before you share
Close the case when the intended recipient can use the current link and the fix preserves the original sharing policy. Keep unresolved preview and identity issues distinct.
Related articles
Sources and editorial disclosure
Primary documentation reviewed October 11, 2026. Product settings and entitlements can change; use the linked help for current details.
VDR Directory is published by the SendNow team. SendNow is included where relevant to the task. This guide is based on public documentation and editorial recommendations, not a claim that a signed-in product demonstration was performed. Stock photos illustrate the topic; they do not show the described product interface or prove feature behavior. Examples and verification checklists are illustrative unless explicitly stated otherwise.
Related Guides & Research
Recommended next reading for deal teams and transaction leaders.
How to Revoke Shared File Access
Disable intended online access and understand the limits for ordinary downloaded or copied files.
Share Files Without a Recipient Account
Choose an account-free viewing workflow while retaining the access checks appropriate for the material.
How to Update a Shared File Collection
Replace one item in a shared collection while checking linked copies, navigation, access, and version notices.