5 GB free storage. No credit card needed. Start free
File sharing

Password-protected file sharing, and when it helps

Create a password-protected dosya.dev link, choose recipient access and expiry, test the result, and replace or revoke a link when sharing ends.

, Senior Software Engineer, dosya.dev team updated 11 min read

To share a file with a password in dosya.dev, open Share, choose By link or By email, and enter a password under Advanced options before creating the link. Combine it with an expiry, check the recipient experience in a private window, and send the password separately from the URL when practical.

This works for a family document, a draft presentation or a client deliverable. The recipient can open the link in a browser without joining your workspace. The useful distinction is between protecting the route to a file and controlling every future copy. A share password does the first; it cannot do the second.

This guide follows the web app. Where changing an existing link works differently on another surface, that difference is called out.

Choose the access your recipient needs

A link can escape its original conversation through a forwarded message, a shared inbox or a copied chat thread. A password adds another requirement: someone who finds only the URL cannot immediately open the protected share.

Choose the access method before choosing a password:

Your situationSuitable starting pointWhat to check
A public portfolio or published handoutAn ordinary share linkEverything in the shared target should be suitable for onward distribution.
A small known audience that should receive a separate secretA password-protected linkEveryone with both the URL and password can pass that gate.
A document intended for particular email addressesBy email with Only these people can open itEach person must control an invited inbox; add a password if you need both gates.
A family member or colleague who needs ongoing workspace accessA workspace invitation and suitable roleMembership is broader than access to one delivered file.

Named-recipient sharing is still usable without a dosya.dev account. The recipient verifies their invited email address with a one-time code. Sending a link by email alone is different: you must enable Only these people can open it to restrict access to those addresses. The named-recipient setup guide shows that control and the recipient’s verification step.

For a group that works together repeatedly, use workspace roles and folder access to define ongoing permissions. For a one-off delivery, a carefully scoped share is usually easier to understand.

Prepare the file or folder first

Open the item yourself before sharing it. Check that it is the intended revision, that its filename makes sense to someone outside your own filing system, and that it contains only what you intend to deliver. A password cannot correct a mistaken attachment or remove information inside a document.

For a folder, inspect its contents and subfolders. A dedicated delivery folder is easier to review than a working directory full of drafts, notes and originals. Keep internal notes outside the target you plan to share. If the recipient only needs one PDF, sharing that file avoids uncertainty about the rest of the project.

Confirm the selected workspace too. Your role must allow creating share links, and workspace policies can require a password, cap the lifetime or disable share creation. A missing control can reflect your permissions rather than a problem with the file.

Decide three things in advance: who should open it, whether they need a download, and when access should end. That turns the sharing dialog into a short review of choices you already made.

  1. Open Files in the intended workspace. Find the exact file or folder and open its Share action.
  2. Choose the delivery path. Use By link to copy the URL yourself. Use By email to enter recipients and send it through dosya.dev.
  3. Set recipient restrictions if needed. On By email, add the intended addresses and enable Only these people can open it when access must be tied to those inboxes. Check the spelling before sending.
  4. Choose the expiry. Pick a period that covers the recipient’s actual task. Review the final stored deadline afterward because account and workspace rules can shorten the requested lifetime.
  5. Open Advanced options. Enter a new secret in Password (optional). The minimum is eight characters. Do not reuse your dosya.dev account password.
  6. Review download access. Leave normal downloading available when the recipient needs an original local copy. Choose View only only when the available preview is sufficient.
  7. Create the share. Choose Generate link or Send, depending on the path you selected. Keep the resulting URL private until you have tested it.
  8. Check the saved link. Open Shared → By me and inspect the correct record. Confirm its target, password indicator, access mode and expiry.

The password setup walkthrough provides the detailed help flow. If you accidentally create an unprotected link, do not rely on simply avoiding further distribution: revoke that URL and create the correctly protected replacement.

Selecting several files can create a bundle. Review each selected item rather than assuming it inherits the checks you made for the first file. Bundle behavior can differ from single-file delivery; in particular, do not assume a metadata-removal option will sanitize every bundled original. For photos whose location or camera information should stay private, prepare suitable copies before sharing and read the EXIF sharing guide.

Choose and deliver the password sensibly

Use a unique password generated for this delivery. A password manager can generate and retain it. A random passphrase can be easier for a recipient to enter on a phone than a long sequence of unfamiliar symbols. The eight-character minimum is an acceptance rule, not a recommendation to use a short predictable value.

Avoid deriving the password from details already visible in the conversation: the family surname, project title, invoice number or current year. Someone who received the forwarded message may already know those details.

When practical, send the URL and password through different established channels. For example, email the link and send the password through the messaging thread you already use with the recipient. Say “I will send the password separately” in the delivery note so the recipient knows what to expect.

Separate delivery reduces exposure when only one message is forwarded. It does not prevent the recipient from forwarding both pieces or protect against someone who can access both channels. When that distinction matters, require the invited email verification gate as well.

Keep a private record of which delivery the password belongs to. Do not put live passwords or unpublished share URLs in screenshots, public support discussions or project documents that unrelated people can read.

Test the recipient experience before relying on it

Use a private browser window that has not already unlocked the link. Your normal browser may have an access grant from an earlier visit, so reopening the URL there is a poor test of whether a new recipient sees the password gate.

Check the entire delivery, not just whether the page loads:

  • The displayed filename or folder is the one you meant to send.
  • The password challenge appears before protected content is accessible.
  • An incorrect password fails, while the intended password works.
  • A named-recipient link requires verification of a listed email address.
  • The available preview or download action matches the intended task.
  • The final expiry gives the recipient enough time to finish.

Use harmless sample content for your first test of an unfamiliar combination of controls. A download limit can be consumed by eligible previews as well as download activity, so leave room for testing and inspect the saved result.

The private-window preflight guide helps distinguish an owner session from a recipient test. If you use a named-recipient sample, perform the inbox verification with an address you control; do not request another person’s verification code.

Understand View only, expiry and activity

View only is a delivery preference, not copy prevention. It removes the offered download action, but recipients can still capture visible content. Preview behavior depends on the format, and some content must reach the browser to be displayed. Use it when reviewing is the task, rather than as a promise that an original can never be recovered.

Expiry limits future access through the link. It does not remove previously downloaded files or revoke ordinary workspace membership. A deadline also reduces the period during which a forgotten URL remains useful. The expiring-links guide explains how to choose a lifetime around the handoff rather than leaving every delivery open indefinitely.

Activity is evidence of an event, not necessarily a person’s attention. A password is shared knowledge, so it does not identify which person used it. Even with recipient verification, an open does not prove that somebody read every page, approved the contents or retained a complete download. Keep those claims separate when reporting delivery progress.

Replace a password or end sharing

The current web app creates and revokes share links; it does not expose an in-place password editor. To replace a web share password, use this sequence:

  1. Open Shared → By me, find the exact link and inspect its details.
  2. Record the access settings you need to preserve, including recipients, password requirement, expiry and download behavior.
  3. Choose Revoke or Revoke link and confirm the correct URL. Revocation is irreversible for that token.
  4. Open the old URL privately and confirm that it reports Link revoked.
  5. Return to the file or folder, create a replacement with the new password and reapply the other controls.
  6. Test the replacement and deliver its new address. Update any private message or document that still points recipients to the old URL.

Revocation ends access through the old token even for a browser that unlocked it earlier. It leaves the workspace item in place. The password-change guide also documents the API alternative: an in-place password update can preserve the URL, but an already issued unlock grant can remain valid for up to 30 minutes. Use revocation when your requirement is an immediate cutoff.

Once delivery is complete, follow the same revocation check without creating a replacement. The broader access-revocation guide covers reviewing other paths that may still provide access.

A practical family or client handoff

Suppose you need to send a household document to one relative, or a finished project PDF to a client. Create a dedicated delivery copy, inspect it, and share that file rather than its whole working folder.

Choose By email, list the intended address and enable named-recipient access if a forwarded URL should not be enough. Set a deadline around the review period, add a unique password, and allow downloading if the person needs to keep a copy. After a private-window test, send the password separately.

Ask the person to confirm they received the correct document. An activity event can help troubleshoot access, but their confirmation answers a different question: whether this is the material they needed. Revoke the link when the handoff is finished, remembering that their already saved copy remains theirs to manage.

Troubleshoot a protected share

What you seeWhat to check next
The link opens without asking for a passwordTest in a fresh private window, then inspect the saved password indicator under Shared.
The password is rejectedCheck that it belongs to this exact URL and has no copied leading or trailing spaces. Avoid repeated guesses; retry after any displayed wait.
A named recipient cannot get inConfirm the invited address and have the recipient use its inbox for the verification code. The password does not replace that step.
The expiry is shorter than expectedInspect the stored deadline and applicable account or workspace maximum.
There is no web Change password buttonRevoke the old share and create a replacement with the new password.
The recipient sees a preview but needs the originalCheck View only and the download settings; replace the web share with the appropriate delivery controls.
A revoked URL no longer worksThat is the expected result. Create a new link if sharing must resume.

Start with one file you can safely test. Open dosya.dev, create the share, and verify that its access, lifetime and download behavior match the person and purpose of this delivery.

Frequently asked questions

How do I password protect a file sharing link in dosya.dev?

Open Share for the file or folder, choose By link or By email, and set the expiry. Open Advanced options and enter at least eight characters under Password (optional), then generate or send the link. Test it in a private browser window before delivering it.

Do recipients need a dosya.dev account to open a protected link?

No. A password-protected share opens in the recipient's browser. If you also enable Only these people can open it on the email path, each recipient must verify an invited email address with a one-time code before entering the link password.

Can I change a share password without changing the URL?

The current web app uses revocation and a replacement link for password changes. The API supports an in-place update, but an existing password unlock grant can remain valid for up to 30 minutes. Revoke and replace when access through the old URL must end immediately.

Does a password stop recipients from forwarding my files?

A password prevents someone with only the URL from opening the share. It does not stop a recipient forwarding both the URL and password, copying visible content, or redistributing a downloaded file. Use named-recipient verification when access should require an invited inbox.

Does View only make a shared file impossible to copy?

No. View only removes the offered download action, but visible content can still be captured. Preview handling also depends on the file format. Treat it as a delivery control, not as a guarantee that recipients cannot retain or reproduce what they see.

Will revoking a link remove copies people already downloaded?

No. Revocation ends further access through that share URL, including for a browser that previously unlocked it. It cannot erase local downloads, screenshots or copies already made elsewhere. The workspace file remains available to its authorized members.