How to Create an Expiring Download Link (Auto-Expires in 10 Steps)

Expiring download links are one of the simplest ways to deliver client work without leaving it accessible forever. They reduce accidental sharing, cut down on “old link still works” confusion, and give you a clean end date for drafts, review cuts, and final exports.

Below is a practical, numbered setup you can follow in any tool that supports link expiry (file-transfer services, some cloud storage providers, and client portals). The exact labels vary, but the choices are the same.

Before you start: pick the right expiry for the job

Choose an expiry that matches how the recipient will actually download. If you set it too short, you create extra support messages. If you set it too long, it defeats the point.

• 24 to 72 hours: time-sensitive handoffs (press files, last-minute exports).
• 7 days: typical client review and download window.
• 14 to 30 days: stakeholders in different time zones, larger teams, or slower approval cycles.

How to make a download link that expires automatically (10 steps)

1. Create a “delivery” folder for this send.

   Make a new folder named clearly (for example: ClientName_Project_Delivery_2026-07-08). Put only what the recipient needs in it so there is no confusion about versions.

2. Export the right file types for the recipient.

   Choose formats your client can open without guesswork. Examples: PDF for proofs, JPG/PNG for previews, WAV/MP3 for listening, or your final H.264/H.265 export for viewing. Keep working files separate unless explicitly requested.

3. Zip the folder if you want “one download.”

   If you want the recipient to click once and get everything intact (especially lots of small files), compress the folder into a single ZIP. If your transfer tool preserves folder structure well, you can skip this step.

4. Upload the files to a service that supports expiring links.

   Use a transfer-link tool designed for delivery, or a cloud storage tool that supports setting an expiry date on shared links. With LetsSend, you can send a file free as a transfer link, rather than giving access to an ongoing folder.

5. Create a share link (set it to “download,” not “edit”).

   In the sharing settings, choose the most restrictive option that still works: Anyone with the link can download (or view) rather than can edit. Avoid “editor” permissions unless you truly need collaboration.

6. Turn on automatic expiry and choose an exact date and time.

   Set an expiry that matches your earlier decision (for example: 7 days from now at 6:00pm). If you work with clients internationally, pick a time that is safe for both time zones (end of your workday is often easiest).

   If the tool offers both options, prefer “expires on date/time” over “expires after X downloads” for predictable client timelines.

7. Optional: add a password (and send it separately).

   Passwords are useful for sensitive work (contracts, unreleased media, client data). Turn on password protection if available. Then send the password in a separate message channel (for example: link by email, password by chat).

   If you need more options and best uses, see: Top 7 Ways to Password Protect a File You Send Online.

8. Optional: limit downloads, or disable forwarding (if available).

   Some tools let you limit the number of downloads, restrict link access, or require verification. Use these sparingly because they can add friction, but they are helpful for pre-release work or one-person deliveries.

9. Write the recipient message with the expiry clearly stated.

   Copy the link and paste it into a short message that includes:

   • What the files are (and which one to use).
   • The expiry date/time (and time zone).
   • Any password instructions.
   • What to do if the link expires (ask you to reissue, or request an extended window).

   Template: “Here’s your download link for the final files: [link]. It expires on [date] at [time] [time zone]. (Password: sent separately.) If you need a longer window, reply and I’ll extend/reissue.”

10. Test it like a client, then send.

    Open the link in a private/incognito window. Confirm the download starts, the folder or ZIP is correct, and the link shows an expiry. Then send it. If you want more delivery workflow improvements, see all features or visit the Help Center.

Quick comparison: expiring transfer link vs cloud folder share

If your goal is a link that stops working automatically, transfer links are usually simpler than sharing an ongoing folder, especially for client delivery.

Troubleshooting: why expiring links still cause “can you resend?”

• Expiry was too short: If the client downloads on Monday but forwards to a teammate on Thursday, set 7 to 14 days next time.
• Time zones weren’t clear: Include a time zone in the message (for example: “5pm BST”).
• Too many versions: Put only the final intended files in the delivery folder, label clearly (FINAL, V2, etc.). For more on clean folder sends, read How to Send a Whole Project Folder in One Link (2025): Transfer Links vs Drive Links Compared.
• Password sent in the same message: If the message is forwarded, the password is forwarded too. Send it separately.

A simple “expiry policy” you can reuse

If you send work regularly, decide a default policy and stick to it:

• Drafts / review cuts: expire in 7 days.
• Final deliverables: expire in 14 to 30 days.
• Sensitive files: always use a password and a shorter expiry.

If you want a consistent setup across projects, you can create a free account and standardise your delivery settings, or compare Free and Pro if you need more control for client work.