On this page
Match expiry to the delivery purpose
Original pages
Text, vectors and images
Copy pages
Keep source objects intact
Merged PDF
New order, same page detail
One day works for coordinated confidential delivery. Three days fits active reviews. Seven days is a practical general default. Fourteen days is useful when several stakeholders need time to respond.
Expiry should not be used as the only protection for sensitive files. Add a password, a download allowance, or both when the consequences of forwarding are higher.
| Window | Good fit | Tradeoff |
|---|---|---|
| 1 day | Coordinated confidential exchange | Recipient must act quickly |
| 3 days | Active project review | Short follow-up window |
| 7 days | General external delivery | Balanced default |
| 14 days | Multi-person review | Longer exposure window |
Manage access after sharing
The server enforces expiry on public views, previews, individual downloads, and ZIP downloads. The sender can also revoke access before the scheduled date from Recent Transfers on the creating device.
Removing a recent-transfer entry from the browser does not revoke the public transfer. Use the explicit Revoke action first when access must end.
Put the workflow into practice
Arrange source documents, select the pages you need, and create one PDF locally in your browser. Review the result before choosing any optional next step.
Try Nexynto TransferFrequently asked questions
Clear answers before you merge
Can I extend a transfer after creation?
Not in the current no-database workflow. Create a new transfer with the required availability window.
What happens after expiry?
New access and downloads are blocked, and cleanup removes expired transfer objects according to the configured lifecycle.