Share large files with passwords and expiry.
Send photos, video exports or project files with a link. Choose a password, expiry and download limit. You need a dosya.dev account to send; public-link recipients can download without signing up.
What you can share on Free
Start with 5 GB of storage, up to 5 active links, expiry up to 7 days and 10 GB of share-link downloads per day. Storage and upload-method limits apply. Reaching the daily allowance pauses downloads until the window resets. See the allowances or see how no-egress-fee pricing works. Transfer allowances still apply.
5 ways to share, one simple interface
Public Share Links
Anyone with the link can access the file. No login required, no restrictions. Best for content you want to distribute widely, like press kits, open-source releases, or marketing assets.
Private Share Links
Only people you explicitly invite can access the file. Recipients must verify their email before downloading. Every access is logged with user identity and timestamp.
Password-Protected Links
Add a password to any share link. Recipients must enter the correct password before they can view or download the file. Failed password attempts are logged.
Expiring Links
Set links to expire after a specific time: 1 hour, 24 hours, 7 days, 30 days, or a custom date, and on a paid plan you can leave a link with no expiry. On Free the maximum is 7 days, and up to 5 links can be active at once. After expiry, the link shows an "expired" page and cannot be used again - the file itself stays in your workspace until you delete it.
Download Limits
Limit how many times a file can be downloaded through a share link. After the limit is reached, the link is automatically disabled. Set limits from 1 to unlimited.
How sharing works in practice
Anyone downloads via public link
PUBLICRecipient enters wrong password
BLOCKEDLink accessed after expiration date
EXPIREDDownload limit reached (5/5 used)
LIMITCorrect password, link still valid, downloads file
SUCCESSCheck a client delivery before you send it
- Put only the approved files in a delivery folder. Keep RAW originals, working edits and unrelated client files separate.
- Create a share link, choose an expiry and add a password if needed. Send the password through a separate channel.
- Open the link in a signed-out browser. Download a sample file using Download; a browser preview is not a check of the original file. Test downloads consume the link’s download count and transfer allowance, so leave enough for the recipient.
- Compare the downloaded file's size and, for an exact byte check, its SHA-256 checksum with your local export. Check image dimensions or play the video or audio file too.
- Send the checked link with the file list and expiry date. Revoke access when the delivery window closes.
Expiry and revocation stop future link access. They cannot remove copies a recipient already downloaded. Password-protected sharing is access control; it does not make ordinary shared files end-to-end encrypted. See Vault for that separate workflow.
For photography projects, use our RAW archive and storage planning guide and client gallery workflow.
For clips, follow the original-video delivery check. To collect files from a client instead, create a file request.
Real-world sharing use cases
Sending final deliverables to a client
Password-protected + 7-day expiry + 3 download limit
A designer generates a share link for the approved brand assets. She sets a password, 7-day expiry, and limits downloads to 3. The client downloads the files, and after 3 downloads or 7 days (whichever comes first), the link stops working automatically.
Sharing lecture recordings with students
Private link restricted to @university.edu emails
A professor shares a folder of lecture recordings via a private link. Only people with a @university.edu email can access it. Students verify their email once, then can download any time during the semester. All access is logged for the professor to review.
Open source release distribution
Public link, no restrictions, unlimited downloads
A team on a paid plan publishes a new SDK release as a public share link. Anyone can download it without logging in. The link never expires and has no download limit; on Free the same link would run for up to 7 days. The team tracks download counts in the audit log to measure adoption.