The Freelancer's Guide to Sending Client Deliverables on Mac

The work is done. Now comes the part nobody teaches you: getting the files to the client in a way that’s professional, trackable, and doesn’t create a week of follow-up emails asking “did you get the files?” and “can you resend in a different format?”

If you’re a freelancer on a Mac — designer, developer, writer, photographer, video editor — this guide covers the full delivery workflow: organizing files, choosing the right sharing method, tracking delivery, and archiving when the project wraps.

Clients judge the deliverables by how they’re packaged, not just what’s inside. A single ZIP file named “final_v3_REAL_final.zip” does not inspire confidence.

Name the folder clearly:

ProjectName_Deliverables_2026-04-19

Structure it predictably:

Brand_Refresh_Deliverables_2026-04-19/
├── Final/
│   ├── Logo_Primary.svg
│   ├── Logo_Primary.png (300dpi)
│   ├── Logo_Reversed.svg
│   └── Brand_Guidelines.pdf
├── Source_Files/      (if included in scope)
│   ├── Logo.ai
│   └── Guidelines.indd
└── README.txt         (what's included, fonts needed, etc.)

Include a README. Even a simple text file that says “This folder contains the final approved logo in SVG and PNG formats. Fonts used: Inter and Playfair Display.” Your client may open this folder six months from now and need to know what they’re looking at.

Step 2: Choose the right delivery method

Upload the folder to a file-sharing tool and send the client a download link. This is better than email attachments because:

Up to 5 GB per share (free)
The client can download when they’re ready
You can track when they download
You can set the link to expire after the project ends

Tools that work well for this: Swooshare (drag from Finder, shake, link is ready), Dropbox (shared link from a synced folder), Google Drive (share link with download option).

For work-in-progress review: a collaborative link

When you need feedback, not just delivery:

Figma/design tools: Share the Figma file directly. Don’t export and share static files for review — it just creates version confusion.
Documents: Google Docs with comment access is still the best for async feedback.
Video: Frame.io or a simple share link with chat (Swooshare includes in-page chat on every share).

For very large files: a dedicated transfer tool

If you’re delivering raw video, uncompressed audio, or massive design archives (10+ GB):

SwissTransfer: Up to 50 GB free, no account
Smash: No file size limit on the free tier
MASV: Fastest upload/download speeds, pay-per-GB

For sensitive or confidential work

If your contract has an NDA or you’re handling financial/legal/medical content:

Use a password-protected share link
Send the password via a different channel (text the password, email the link)
Set an expiry date
Consider Proton Drive or Tresorit for end-to-end encryption

For a deeper look at each layer of protection, see our practical guide to secure file sharing on Mac.

Step 3: Write the delivery message

The message you send with the deliverables matters as much as the files. Keep it professional and clear:

Hi [Name],

The final deliverables for [Project Name] are ready. You can download everything here:

[link]

The folder includes [brief list of what’s inside]. Everything matches the approved version from [date]. The link will be active for 30 days.

Let me know if you need any changes.

Three things this message does: confirms what’s included, references the approved version (important if scope creep is a risk), and sets expectations about the link’s lifespan.

Step 4: Confirm delivery

Don’t assume the client received and opened the files. A share link sitting unclicked in someone’s inbox is not delivery.

If your sharing tool has analytics (Swooshare, Dropbox Professional): Check if the link was viewed and files were downloaded. You’ll see exactly when it happened.

If it doesn’t: Follow up after 2-3 days if you haven’t heard back. A simple “Just checking — were you able to download the files?” is enough.

Why this matters: “I sent the files” is not the same as “the client has the files.” If you don’t confirm delivery, you risk delayed payments, scope disputes, and the awkward “I never got them” email two weeks later.

Step 5: Archive and clean up

Once the client confirms receipt:

Let the share link expire or revoke it manually. There’s no reason for deliverable files to be accessible months after the project ends.
Archive the project folder locally. Move it to an archive drive or a dedicated archive folder. Don’t delete it — clients come back months later asking for “that file you sent.”
Archive the share link info. If you used a file-sharing tool with analytics, save or screenshot the delivery confirmation (date, download time) in your project records. This is useful if there’s ever a dispute about when files were delivered.

Common mistakes

Sending source files by default. Unless your contract explicitly includes source files (PSDs, AIs, INDDs), don’t include them. Deliverables are the finished product — exported, flattened, ready to use. If the client wants source files, that’s a separate line item.

Using personal cloud storage. Sharing from your personal Dropbox or Google Drive means the client has a link to a folder in your personal storage. If you reorganize your files later, the link breaks. Use a dedicated sharing tool that creates independent download links.

Not setting an expiry. A link you shared in January is still live in December. That’s months of your files sitting on someone else’s server, accessible to anyone who has or finds the URL.

Over-delivering without documentation. Sending 47 files in a flat folder with no README is technically complete but practically useless. The client will email you asking which file is the final version, which file is for web vs. print, and what font they need to install.

The five-minute delivery workflow

For most freelance deliverables on a Mac:

Organize the folder (2 minutes)
Add a README (1 minute)
Share via link with expiry (30 seconds)
Send delivery message to client (1 minute)
Check download confirmation in 2-3 days
Archive when project wraps

Total time: about 5 minutes of intentional work that saves hours of back-and-forth and makes you look significantly more professional than “see attached.”

The designer’s file delivery playbook — a more design-specific version of this workflow, covering review rounds and source files
What is a file request? — how to collect files from clients without the email back-and-forth

Step 1: Organize before you share