How to share data online safely with an expiring link (photographer workflow)

A remote worker on a video call in a small creative agency open-plan room, reviewing photo thumbnails before sending a client gallery in warm late-afternoon light.

You searched share data online because you need a simple way to deliver files without leaving them floating around forever. The safest practical pattern for client delivery is: export clean files, put them in one folder, send them via a time-limited (expiring) download link, add a password, and keep the password out of the link message. That gives your client an easy download, and gives you an automatic clean-up date.

Below is a real-world photographer workflow, from final export to “client received”, with the small details that stop the usual mess: forwarded links, surprise re-downloads, and clients trying to pull 4GB on a phone over café Wi‑Fi.

What “safe” actually means for sharing data online

For most creative client delivery, “safe” is less about spy-movie security and more about sensible controls that prevent accidental exposure:

  • Access control: only people with the link (and ideally a password) can download.
  • Time control: the link expires, so it cannot be opened months later.
  • Storage control: the files are deleted when the transfer expires, rather than lingering.
  • Integrity: your files arrive unchanged (no auto-resize, no recompression, no “helpful” conversions).

There are more advanced needs (audits, DLP, custom contracts), but for photographers delivering galleries, selects, or a final package, those four cover 95% of the real risk.

The photographer workflow: from Lightroom export to a safe expiring link

This walkthrough assumes you are delivering a finished gallery to a client (wedding, brand shoot, architecture interiors), and you want a clean handoff that will not come back as a support ticket at 10pm.

Step 1: Export with the “client download” in mind

Decide what the client is meant to do with these files. Your export settings should match that job:

  • Social and web use: sRGB, moderate long edge (for example 3000 to 4500px), JPEG quality that looks great without being huge.
  • Print-ready: full resolution, sRGB or Adobe RGB depending on your lab workflow, minimal compression, and consistent naming.
  • Mixed delivery: deliver two folders (WEB and PRINT) so the client does not accidentally send 40MB files to their web designer.

Useful lived detail: if you export a 40GB folder of full-res JPEGs and your client starts downloading on a phone, iOS will happily try, fail halfway, and they will blame your link. You can prevent this by including a WEB set, and by telling them “download on a laptop/desktop for the full set”.

Step 2: Put everything into one clearly named folder

Make one top-level folder so the download is tidy. A good naming pattern is:

  • ClientName_Project_YYYY-MM-DD

Inside it, keep it boring and obvious: WEB, PRINT, and optionally a README.txt (download instructions, usage notes, print lab recommendations). If you include a README, keep it short and friendly.

Step 3: Decide whether to zip, and only zip for structure

Zipping is useful when you need to preserve folder structure and make “one download”. It does not meaningfully shrink most photo and video exports, because JPEG, PNG, MP4, and most RAW formats are already compressed. Re-compressing them mostly wastes time.

  • Zip if: you are sending multiple folders, or you want one clean archive to download.
  • Do not zip if: the client is likely to struggle unzipping on their device, or you want them to browse individual files easily after download.

If you do zip, test it: unzip it once on your machine and spot-check a few files. It is a 30-second step that prevents a painful resend.

Step 4: Use an expiring transfer link (not a shared cloud folder)

A shared Drive/Dropbox folder is great for ongoing collaboration. It is less great for one-off delivery because it tends to linger, permissions get messy, and clients can keep re-downloading forever (sometimes to “just check something” six months later).

An expiring transfer link is a better match when the job is: deliver, confirm receipt, and auto-clean up.

Step 5: Add a password, and send it separately

Password protection is the simplest upgrade you can make. It protects you from the most common failure mode: someone forwards the email or message with the link.

  • Best practice: send the link in email, and the password via a different channel (for example SMS or a chat message).
  • Do not: put the password in the same message as the link.
  • Keep it human: a short passphrase is better than a cryptic string the client will mistype.

Step 6: Set the expiry date based on the real project timeline

Expiry should be long enough for normal life, short enough to reduce risk.

  • Typical client gallery delivery: 7 to 14 days.
  • Busy teams (marketing departments): 14 to 30 days.
  • Highly sensitive work: consider a shorter window and a download limit.

Also tell the client the deadline in plain language: “Link expires on Friday (so please download by Thursday evening).” This reduces frantic “it stopped working” messages.

Step 7: Write a delivery message that prevents support requests

Most delivery problems are not technical. They are expectation problems. A solid delivery message includes:

  • What is in the download (WEB and PRINT, or whatever you are delivering)
  • Where to download (the link)
  • How to download (recommend desktop)
  • When it expires (specific date)
  • Where the password is coming from (separate message)

Example you can copy:

  • Subject: Your gallery download (expires 12 Oct)
  • Body: Hi Sam, here is your gallery download link (WEB + PRINT folders). For best results, download on a laptop/desktop. This link expires on 12 Oct. I will text you the password separately.

Quick comparison: expiring transfer link vs cloud folder vs messaging apps

Practical ways to share data online for client delivery
MethodBest forExpiry by defaultPassword protectionMain downside
Expiring transfer linkOne-off delivery of finished workYes (set a date)Often yesNot designed for long-term collaboration
Cloud storage folder (Drive/Dropbox/OneDrive)Ongoing collaboration and revisionsNo (you must manage it)Sometimes (depends on setup)Links and permissions tend to linger
Messaging apps (WhatsApp/Slack)Quick small files, previewsVariesNo (not link-level)File limits, recompression, messy search later
Client gallery platformProofing, favourites, print salesVaries by platformVariesMay not be ideal for delivering original files

If you use LetsSend: a safe, simple way to send with expiry and a password

Disclosure: LetsSend is our product. We build and run a private file transfer service, so the guidance above reflects what we see go wrong in real transfers.

If you want a straightforward expiring-link delivery, LetsSend is designed for exactly this workflow:

  • Free: up to 5GB per transfer (5GB daily allowance, up to 10 files per day), links expire after 7 days.
  • Pro (as of September 2026): up to 200GB per transfer, expiry up to 30 days, $12/month. Pro links can also have a download limit.
  • Account security: passwordless sign-in using a short code emailed to you (no password to leak).
  • How transfers work: files upload straight from your browser to encrypted object storage (not relayed through a middle server).
  • Privacy: we do not sell files or contact details, and expired transfers are deleted rather than quietly archived.

When you are ready to send, you can send a file free. If you want the knobs and dials first, you can see all features (expiry, passwords, download limits).

Edge cases that trip up “safe sharing” (and what to do instead)

“My upload keeps failing on bad Wi‑Fi”

This is the most common real-world problem, especially from hotels, venues, trains, and shared studios. Before you assume the service is broken:

  • Use a wired connection if you can (even a cheap USB-C ethernet dongle is magic).
  • Keep your laptop awake until the upload finishes (sleep kills uploads).
  • Upload from Chrome or Safari if your browser is being weird, and close heavy tabs.
  • Send in two transfers if your gallery is massive and you cannot risk a single long upload session.

If you want a deeper checklist, the Help Center is the fastest place to troubleshoot specific setups.

“I need to send to multiple people, but I do not want it forwarded”

If you truly need to prevent forwarding, you need identity-based access (logins) or per-recipient links with tracking, which starts to look like a client portal or a data room.

For most creative delivery, a practical middle ground is:

  • Use a password.
  • Keep expiry short.
  • If available, use a download limit (helpful when you only expect one download).

Be honest with yourself: if you send a single link and password to five people, you are relying on team behaviour. That might be fine, but it is not the same as strict access control.

“I am sending sensitive documents, not photos”

The workflow is the same: expiring link, password, separate channels for link and password. If the documents are highly sensitive (legal, medical, HR), consider whether you need a specialised encrypted document portal with audit logs and compliance features. A simple transfer link is convenient, but it is not a full governance system.

“The client says the link expired, but I swear it shouldn’t have”

Two common causes:

  • Time zone confusion: your “Friday” is their “Thursday night”. Put the date in the message, and if it matters, include the time and time zone.
  • They bookmarked an old link: if you resent a corrected transfer, clients often click the first email thread. Tell them “use the newest link below”.

A simple safety checklist before you hit send

  • Right files: spot-check 3 images from different parts of the shoot.
  • Right structure: one folder, clear names, WEB/PRINT if relevant.
  • Right expectations: tell them to download on desktop for big sets.
  • Controls: expiry set, password set, password sent separately.
  • Clean-up: confirm the service deletes expired transfers (not all do).

Where to check how LetsSend handles privacy and retention

If you are trusting a transfer service with client work, it is reasonable to ask who is behind it and what happens to your files. You can read about the team behind LetsSend and review how we handle your data. If you have a specific question about a client delivery, you can also contact us.

Related guide if your delivery is bigger than you expected

If you landed here because the folder is over your usual limits, you may also want: Send 7gb file free: a step-by-step way to deliver it when email is too small.

Verdict: the safest “normal person” way to share data online

If you want client delivery that is simple and safe, use an expiring transfer link, add a password, and send the password separately. It is fast for your client, it reduces accidental exposure, and it gives you automatic clean-up instead of a folder that lives forever.

When you are ready, you can send a file free, or compare Free and Pro if you regularly deliver larger projects.

Frequently asked questions

What is the safest way to share data online with a client?

Use a download link that expires, add a password, and send the password separately from the link. This reduces accidental forwarding, limits how long the files stay accessible, and keeps the client experience simple. Also confirm the service deletes expired transfers, not just disables the link.

Are expiring links safer than Google Drive or Dropbox shared folders?

For one-off delivery, yes in practice. An expiring link is designed to stop working on a set date, which reduces long-term exposure. Shared folders are better for ongoing collaboration, but they tend to linger, permissions get messy, and clients can keep re-downloading indefinitely unless you manage access actively.

Should I zip a photo gallery before I share it online?

Zip mainly for structure, not for size. Zipping helps you deliver one neat download and preserves folders, but it rarely shrinks JPEGs, RAW files, or videos much because they are already compressed. If your client is not technical, consider sending an unzipped folder to avoid unzip problems.

How long should I set an expiring link for client delivery?

Set it based on real timelines. For typical gallery delivery, 7 to 14 days is usually enough. For busy teams, 14 to 30 days can be more realistic. Always state the expiry date in your message so the client knows when to download, and you avoid last-minute panic.

What if my client forwards the link to someone else?

If the link has no password, anyone with it can typically download. The practical fix is password protection and sending the password separately. If you need strict prevention of forwarding, you usually need identity-based access (logins) or per-recipient links, which is more like a client portal than a simple transfer link.

How do LetsSend expiry and size limits work on Free vs Pro?

As of September 2026, LetsSend Free allows up to 5GB per transfer with a 5GB daily allowance, up to 10 files per day, and links expire after 7 days. LetsSend Pro allows up to 200GB per transfer, expiry up to 30 days, costs $12/month, and Pro links can include a download limit.

share data online expiring link password protected file sharing photographer workflow client delivery secure file sharing

Your files are waiting.

Drop something in and watch it fly. It takes about ten seconds.

Send something