Share pages
A shared file or folder opens as a browser page with enough context for the recipient to understand the content before downloading. That is a better default than a raw object URL.
Sharing
Share links that stay useful without becoming permanent liabilities.
Cotton sharing is designed as a product flow: recipients get a clean preview page, operators get token cleanup, and users can choose links that expire or delete after use.
Expiring tokens
Links can expire so old shares do not live forever by accident. Background retention jobs can clean expired tokens instead of leaving manual cleanup as an operator chore.
Single-use downloads
Download tokens can be marked for deletion after use. That gives sensitive one-off transfers a tighter lifecycle without requiring recipients to create accounts.
Proof in the share lifecycle
Sharing is backed by expiring tokens, single-use download options, preview-aware share pages, native browser share hooks where available, token cleanup jobs, and metadata references instead of duplicated physical blobs.
Why this is sharper
Sharing stays intentional. Cotton gives the recipient a useful page, gives the sender expiry and single-use options, and gives the operator cleanup paths instead of a pile of permanent public URLs.
Native share integration
Where supported by the browser or operating system, Cotton can use native share hooks. The fallback remains a normal copyable URL.
Preview-aware sharing
Images, PDF, audio, video, text, and model previews make shared content legible. Recipients do not have to download blindly just to verify they got the right file.
Storage model underneath
A share points back to Cotton metadata and content references. It does not require duplicating physical stored data just because a link exists.
Bearer links still need discipline
A public share link is still a bearer secret. Anyone with a valid link can use it until the link expires, is consumed, or is revoked, so sensitive workflows should choose expiration, single-use transfer, or account-based access deliberately.
FAQ
Direct answers
Can people download shared files without an account?
Yes. Share pages are intended for recipients who only have the link. Account access is not required for normal public share downloads.
Are share links the same as user permissions?
No. A public share link is intentionally accountless access for people who have the URL. Use account permissions when the recipient should authenticate as a known user.
Can shared links be cleaned up automatically?
Yes. Expiring tokens and token retention jobs keep share cleanup as part of the product lifecycle.