Create a secure file sharing link
Create and test a cloud file sharing URL with the right recipient access, password, expiry, download controls and workspace policy.
Last reviewed
In Files, choose Share on a completed file, select By link for a public URL or By email for named recipients, configure its access controls, then test the result privately before sending it.
Before you start
- Verify the active workspace, filename and completed upload. A sharing URL points to the selected workspace item; it does not upload a replacement.
- Your role needs create share links permission. A folder-confined member may share only targets inside the assigned subtree.
- A hidden target appears unavailable to a member it is hidden from. A target or ancestor with configured Full lock cannot receive a public link, even if your current member session has a personal unlock grant.
- Decide whether the URL can be forwarded. By link is public to anyone holding it, subject to password, expiry and other controls. By email can restrict access to verified addresses.
- Keep sensitive URLs and passwords out of public tickets and screenshots.
Steps
Choose who can open the share
- Open Files, locate the completed file, and select Share from its row/card menu or right-click menu.
- Verify the target name under the Share heading.
- Select the recipient path that matches this delivery:
- By link displays Anyone with the link can access this file. It creates a bearer URL and sends no invitation.
- By email accepts up to 50 distinct valid addresses. Leave Only these people can open it. selected for a private link. Each visitor must enter an invited address and a one-time code emailed to it.
- For restricted email access, know the timing: the code lasts 15 minutes, permits five incorrect attempts, and a successful recipient grant lasts up to 30 minutes. Forwarding the URL alone does not add another address.
Configure expiry and download behavior
- Review Expires in. The web choices are 1 hour, 24 hours, 7 days, 30 days, 90 days, Custom date… and Never.
- A custom timestamp must be at least one minute ahead and no more than 3,650 days away. Workspace policy can silently shorten a longer selection and can supply the initial default, so check the stored expiry after creation.
- Expand Advanced options and apply only the controls the delivery needs:
- Password (optional) requires eight or more trimmed characters. It is independent of recipient email verification.
- View only. blocks the normal attachment download and serves eligible inline previews. JPEG, PNG and HEIC are re-encoded as WebP with the longest edge capped at 1,600 px. WebP, AVIF, GIF, SVG, BMP and ICO lack that server decoder and can be shown inline as their original bytes, so View only does not promise that every image preview withholds the source bytes. Any visible material can still be captured.
- Remove photo metadata. strips location, camera and capture-time metadata from delivered photos while leaving the workspace original unchanged.
- Download limit (optional) accepts a whole number from 1 through 10,000. The first eligible preview or download byte session claims one slot, including a View-only preview. Later Range requests for that same file within its one-hour signed session reuse the claim; a new browser or later session can consume another.
- The current dialog also displays Title (optional). The current By link request saves the trimmed Title (optional) and message with the share and displays them on the recipient page. Set a clear title when the filename alone does not identify the delivery; verify the saved values in Shared after creation.
Create and verify the delivery
- On By link, generate and copy the URL; on By email, send the invitations:
- For By link, select Generate link, wait for Share link created, use the copy icon, and select Done. Automatic clipboard success is confirmed by Link copied — Share link copied to clipboard.
- For By email, select Send. The success notice reports how many addresses received the invitation and lists any failures. The modal then resets and closes; it does not show Share link created or a copy result.
- Open Shared → By me and inspect the saved row. Its detail states who can open it, the stored expiry, password state and Downloads: Allowed or View only. This is also where you retrieve the saved URL after the email modal closes.
- For a public bearer link, open the copied address in a private window. For a restricted email delivery, retrieve the address from Shared → By me and test with an invited inbox that can receive its one-time code.
- Confirm the target, password prompt, recipient challenge, expiry and download behavior that you intended. Do not open file bytes while testing a one-slot delivery: even an eligible inline preview consumes its only slot. Use a limit of at least two when the private-window byte test and one recipient session must both succeed.
- Distribute a By link address only after that check, sending its password separately when practical. By email has already sent invitations; correct and retry any addresses named as failures instead of waiting for a generated-link result.
Expected result
The new row appears under Shared → By me with the selected target, final expiry, password state, recipient scope and download mode. The private-window visitor reaches the intended file and encounters every configured challenge before any protected bytes are served.
Plan and workspace limits
- A Free-plan creator can hold five active sharing links across workspaces. The exact refusal is The free plan allows 5 active share links at a time. Revoke one, let one expire, or upgrade for unlimited links.
- Free links are clamped to seven days even if Never or a longer duration was chosen. A tighter workspace maximum wins.
- Revoked and expired URLs no longer occupy an active-link slot.
- Public share traffic owned by a Free account has a 10 GiB allowance per UTC day. When exhausted, recipients see This link’s owner has reached their free plan’s daily share-transfer allowance. Try again later - or the owner can upgrade for unmetered sharing.
- A workspace can disable share links, require every link to have a password, impose a default expiry or cap the maximum expiry.
- A multi-file link supports 1 through 100 files. A selection of 101 is refused with Maximum 100 files per share link.
These limits apply to what is ultimately saved, not merely what the form showed. Verify the final row in Shared before distribution.
Locks, hiding and later changes
Public link creation deliberately ignores a member’s temporary unlock. If the selected file or an ancestor is configured Full lock, remove or change that configured lock with the appropriate authority, or share a separate delivery copy. A hidden file is reported as not found to a role that cannot see it.
If a target receives Full lock or becomes hidden from the link creator after the URL was created, public access is blocked at open time. Removing that configured state can make an unrevised, unrevoked link reachable again. Revocation is different: it permanently ends the token.
A target-level View only setting also makes the link effectively view-only even when the link itself was created with downloads allowed. Personal unlock grants never bypass any of these public-link decisions.
Revocation and irreversible outcomes
Open Shared → By me, locate the precise row, select Revoke share link, and confirm Revoke. Subsequent requests immediately return This share link has been revoked. The URL cannot be reactivated; create another one when access should resume.
Revocation does not erase the source file, recall a downloaded copy, retract an email already delivered or change other active URLs for the same target. Review all rows when the item must no longer be shared anywhere.
Troubleshooting
Generate link says sharing is disabled or a password is required. Follow the workspace policy shown by the exact message. Only an authorized workspace administrator should change those controls.
The selected expiry is shorter in Shared. Free-plan and workspace ceilings clamp longer choices. The saved timestamp is authoritative.
The form reports a locked or missing file. Confirm the item is visible to your role and not beneath a configured Full lock. Re-entering a personal unlock password cannot authorize a persistent public token.
A private recipient cannot continue. They must use the exact invited address. One-time codes expire after 15 minutes and are replaced when a new code is sent. After five wrong attempts, request another code.
The download limit ended too early. Your private-window preview or download can consume a slot. Range requests for one file within the same one-hour signed session are counted together, but another browser, another file or a later session can claim another place.
The recipient gets a Free-plan transfer message. Wait for the UTC-day allowance to reset or have the owning account change plan. Regenerating another link under the same Free owner does not create a separate allowance.
Frequently asked questions
Does a public recipient need a Dosya account?
No. A By link visitor opens the public page subject to the URL’s controls. Restricted By email access proves control of an invited inbox instead of requiring workspace membership.
Can I edit the URL after sending it?
The authenticated API supports in-place updates to several settings, while the current web flow creates and revokes links. Use the controls actually present in your interface and retest after any change.
Is a sharing password the same as Full lock?
No. A share password protects that URL. Full lock is configured on the workspace target or folder tree and blocks creation or public access regardless of a member’s temporary unlock.
Related guides
Was this helpful?
Loading helpfulness results…
Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.
Questions and replies
Ask about the steps in this guide. Questions are reviewed before publication.
Keep account details, credentials and private files out of public questions. Use private support for those.
Loading questions…
Sign in to your Dosya account to ask a question.