Direct and share links
The raw media delivery path checks the link expiry, and the share-page route checks it before showing the file. A visitor should not receive the active file through either output after the deadline.
Temporary sharing is useful when a screenshot, draft, document or diagnostic file should stop serving after the task is over. Media2URL applies an expiry setting to the file link, then the direct response and share page stop serving that link when the time condition is reached.
The useful detail is what changes after the upload or selection. Follow the steps to see where the file, link and recipient fit together.
Upload a supported image, GIF, PDF, audio, video or other approved file. The uploader applies the current file-type, size and plan checks before creating a link.
The normal uploader exposes one day, one week, one month, one year and lifetime choices. Temporary-focused flows can expose shorter choices, so use the selector shown on the page.
After the upload, copy the direct URL when a system needs the file response, or copy the share-page URL when a person should open a browser page. Both use the configured link expiry.
After expiry, the direct media request returns an unavailable response and the share page shows its unavailable state. Account cleanup and deletion are separate from the moment the link stops serving.
A time limit answers when a link should stop working. It does not answer who may open the file, whether downloads are allowed or whether the asset should be removed from the workspace.
The raw media delivery path checks the link expiry, and the share-page route checks it before showing the file. A visitor should not receive the active file through either output after the deadline.
Public, unlisted, private and password-protected modes control access differently from expiry. Private and password settings can require a paid plan, while unlisted access still depends on possession of the link.
For an owned asset, the dashboard can expose a date, download settings, preview-only or force-download delivery, one-time view and maximum-download controls according to the current account.
Expiry changes the link state first. The backend has expired-link cleanup behavior, but the page does not promise immediate deletion of every original file at the exact expiry time.
Send a screenshot or log while a support case is active, then let the link become unavailable after the period in which the evidence is useful.
Share a draft PDF, image or video for a defined review window instead of leaving an early version open through a permanent-looking link.
Give a contractor or collaborator a file for the task that needs it, then use the dashboard to change access or remove the asset when the handoff ends.
Use a time-limited URL for a form, quotation or diagnostic document when the recipient needs a link now but the file has no long-term publishing role.
It means a supported file is shared through a link with an expiry condition instead of being left active indefinitely. The time setting controls when that link stops serving the file.
Yes. The raw media route and the share-page route both check the configured link expiry. After the deadline, the direct response is unavailable and the share page shows its unavailable state.
The link stops serving first. Expired-link cleanup can remove expired records and storage objects through the backend, but the page does not promise that deletion is immediate at the exact expiry time.
Where the account exposes those controls, yes. Privacy and password settings control who can open the link, while expiry controls how long the link remains valid.
Use a related page when the next step needs a different file type, workspace control or sharing mode.
Product controls and plan availability can change. The active dashboard remains the source of truth for your account.