How to send a whole project folder in one link (without breaking anything)

You want to send a whole project folder in one link so the client gets everything (files, subfolders, names, versions) exactly as you intended, without “where did that file go?” messages. The reliable way to do it is: package the folder into a single archive (ZIP or equivalent), sanity-check it, then upload it to a transfer-link service and share the link.

Below is a practical workflow you can follow in 10 to 15 minutes, even if your folder is messy, huge, or full of odd file types (RAWs, fonts, CAD refs, plug-in assets). It includes the parts most guides skip: what to exclude, what to rename, how to avoid broken links, and what to do when uploads fail halfway through on bad Wi‑Fi.

Quick decision: do you actually want “one link” or “one shared workspace”?

Before you package anything, choose the right delivery shape:

• One link (final delivery): best for sending a finished deliverable or a snapshot for review. The recipient downloads once, offline, no login, no permissions drama.
• Shared folder (ongoing collaboration): best if you will keep adding files, iterating, or co-editing. This is where Dropbox/Google Drive/OneDrive shine, but access requests and sync conflicts are common.

If your goal is “here is the project folder as it exists right now”, you want the one-link snapshot workflow below.

Step-by-step: send a whole project folder in one link

1. Make a clean “Delivery” copy of your folder

   Do not zip your working directory directly. Copy it and create a delivery version so you can safely remove junk without risking your real project.

   • Name it clearly: ClientName_ProjectName_Delivery_2026-08-24.
   • Remove obvious clutter: cache folders, preview renders you do not want to ship, temp exports, autosaves, and OS files (for example .DS_Store on macOS).
   • Include a tiny README (a text file is fine): what’s inside, what to open first, and any missing dependencies you deliberately excluded.

   Lived detail that saves time: if you are exporting from Premiere/Resolve/After Effects, those project folders often contain gigabytes of cache. Clients do not need it, and it turns a 6GB delivery into a 40GB problem.

2. Fix the “this will break on their computer” issues

   A folder can download perfectly and still fail to open. Do this quick pass:

   • Flatten weird characters: avoid trailing spaces, slashes, or very long filenames. Keep it boring: letters, numbers, underscores.
   • Check linked assets: design and video projects frequently reference external files by path. If you have assets outside the folder, collect them into it (for example “Collect for Output” style features in many creative apps).
   • Fonts and licenses: if you cannot legally share fonts, note it in the README and outline the substitute.

   This is the step most people skip, then they spend an hour on a call trying to reconstruct why a missing texture or font is “suddenly different”.

3. Choose the right packaging format: ZIP almost always wins

   Your goal is a single file that preserves the folder structure. The common choices:

   • ZIP: best default. Works everywhere. Recipients can open it on Windows and macOS without installing anything.
   • TAR: common in developer workflows, less friendly for clients.
   • 7z/RAR: excellent compression options, but some recipients cannot open them without extra software.

   Important: compressing does not magically shrink already-compressed media. Zipping a ProRes or H.264 export usually saves almost nothing and can waste time. You are zipping primarily to bundle and preserve structure, not to chase a smaller size.

4. Create the archive (Windows and macOS)

   On macOS: right-click the delivery folder, choose Compress. This creates a .zip in the same location.

   On Windows: right-click the delivery folder, choose Send to → Compressed (zipped) folder.

   After it finishes, you should have one file: ClientName_ProjectName_Delivery_2026-08-24.zip.

5. Sanity-check the ZIP before you upload

   This takes 60 seconds and prevents embarrassing “it’s empty” messages.

   • Open the ZIP and confirm the top-level folder is inside (not a loose pile of files).
   • Spot-check a few files: open an image, a PDF, a render, a project file.
   • Confirm size: does it roughly match what you expect? If it is suddenly 3x bigger, you probably included cache or proxies.
6. Pick your delivery method: transfer link vs cloud storage

   If you want a single download link with automatic expiry, a transfer-link tool is usually simpler. If you want ongoing collaboration, cloud storage is better. Here is a quick, practical comparison:

   One-link folder delivery: transfer link vs cloud storage (what changes in real life)

   Option	Best for	Common failure point	What the recipient experiences
   Transfer link (for example LetsSend, WeTransfer-style)	Final delivery, reviews, handoff to client	Link expires before they download, or they forward it internally without context	Click link, download ZIP, done (usually no account needed)
   Cloud storage share (Dropbox/Google Drive/OneDrive)	Ongoing collaboration, shared source files	“Request access”, wrong account, sync conflicts	Often needs sign-in, can browse folders, may stream previews

   If you are delivering to a client who just wants the package, a transfer link is the least friction.

7. Upload the ZIP and generate one link

   With LetsSend (disclosure: this is our product), the workflow is built for this exact job: upload the single ZIP and share one expiring link. Files upload straight from your browser to encrypted object storage rather than being relayed through a middle server.

   • Free: up to 5GB per transfer, with a 5GB daily allowance, up to 10 files per day, and links expire after 7 days.
   • Pro (as of August 2026): up to 200GB per transfer, link expiry up to 30 days, at $12/month. Pro links can also carry a download limit.

   If your ZIP is bigger than 5GB, you either need to split it (see step 9) or use a paid plan/tool that supports your size.

8. Set link controls before you send it

   For client work, two settings prevent most headaches:

   • Expiry: choose an expiry date that matches your project timeline, not your optimism. Give them enough time for approvals, weekends, and “I’ll download it when I’m back at my desk”.
   • Password protection: if the folder contains client personal data, unreleased work, or anything sensitive, enable a password and send the password in a separate message channel.

   On LetsSend, links expire automatically, can be password protected, and Pro links can include a download limit. You can review the full set of controls on see all features.

9. Write the message that prevents back-and-forth

   Send the link with a short, structured note. Copy and paste this:

   • What it is: “Final delivery of Project X” or “Round 2 review package”.
   • What to do: “Download the ZIP, then open /01_START_HERE/README.txt.”
   • What’s inside: key folders, exports, specs.
   • Expiry: “Link expires on Friday.”
   • Password: send separately if used.

   This is small, but it is the difference between “got it, thanks” and a chain of “which file is the final one?” emails.

10. If your folder is too big, split it without confusing the recipient

    If you hit a size cap (for example 5GB on a free transfer), you have three sane options:

    • Split by deliverable: Exports in one ZIP, source assets in another. This often maps to what the client actually needs.
    • Split by folders: /Renders, /RAW, /ProjectFiles, /Audio. Keep names consistent.
    • Use a plan/tool that supports the whole package: fewer moving parts, fewer links to track.

    Avoid splitting into random “part1.zip, part2.zip” unless the recipient is technical and expecting it. It is a guaranteed support ticket.

11. Failure-proofing: what to do when uploads fail halfway

    Large uploads fail for boring reasons: flaky Wi‑Fi, laptop sleep, VPNs, and browser tab crashes. Here is a practical checklist:

    • Use stable internet: if you are on hotel Wi‑Fi, expect trouble. If possible, switch to wired, or a reliable hotspot.
    • Keep the tab open until it finishes. Do not let your laptop sleep.
    • Try a different browser if you see repeat failures (Chrome and Safari can behave differently depending on extensions).
    • Upload the ZIP, not 2,000 tiny files: many small files increase overhead and can amplify failures. One archive is usually more resilient.

    If you want deeper troubleshooting, visit the Help Center.

Security and privacy: what “one link” really means

A link is convenient, but treat it like a key:

• Anyone with the link can usually download unless you add a password. If the work is sensitive, use password protection.
• Expiry is not just tidiness: expiring links reduce the risk of old client links being forwarded months later.
• Know the retention behaviour: some services keep data after the link “expires”. At LetsSend, expired transfers are deleted rather than quietly archived.

If you want to understand who is behind the service and how data is handled, you can read the team behind LetsSend and how we handle your data.

When you should not zip a folder (and what to do instead)

Zipping is best for snapshots. Skip it when:

• You need selective access: “They should see /Exports but not /Contracts.” Use a permissioned cloud folder or separate transfers.
• You need ongoing updates: if you will add files daily, a shared folder avoids repeatedly downloading huge ZIPs.
• The recipient is on mobile: phones can download big ZIPs, but extracting and working with them is painful. Consider sending just the exports, or a smaller curated package.

Do the thing: send your folder in one link

If you have your delivery ZIP ready, the fastest next step is to upload it and send one clean link. You can send a file free (up to 5GB per transfer) and add expiry and a password if needed. If your packages are routinely larger, compare Free and Pro before you build your delivery workflow around a cap.

If you are unsure about any edge case (expiry, passwords, download limits, or file count), read the FAQs or contact us and a real person will help you choose the simplest safe setup.

Related reading

• How to send files that are too big for email: 7 best options (ranked)