You spent three weeks on a brand video. The edit is tight, the grade is dialed, the motion graphics are clean. Then you send the client a Dropbox link.
They open it to a folder called Final Exports (2) containing render_v3_FINAL_USE THIS.mp4, render_v3_FINAL_FINAL.mp4, and a subfolder called old. They download the wrong file. They come back a week later asking which one to use. You re-explain everything.
That is not a client problem. That is a delivery problem. And it is completely avoidable.
What bad delivery actually looks like
Most freelancers and small studios treat file delivery as an afterthought. The creative work gets full attention. The handoff gets a Dropbox link and a "let me know if you have any questions".
Here is what the client sees on the other end:
The generic Dropbox folder. No context, no instructions, a pile of files with unclear names. The client has to guess which file is the final version. If they pick wrong, you find out in a revision request two weeks later.
The WeTransfer link with no sender name. A generic page with a download button and WeTransfer, or Google branding at the top. Looks like the file came from a random internet service, not a professional you hired.
The Google Drive link that asks them to sign in. Marketing managers at agencies and brand teams often have personal Google accounts that are not their work accounts. "Sign in to access" creates friction, confusion, and support emails to you.
The email attachment that is too large. It bounces. You have to go find a transfer service anyway, except now it looks like you did not plan ahead.
The Zip file called DELIVERABLES_FINAL.zip. They open it and find a flat list of fifty files with no folder structure. Everything that had context inside your project folder is now context-free.
Each of these sends the same message: the creative work may be good, but the business side is not.
File naming conventions that make you look like a pro
The goal of a file name is to communicate four things without any additional explanation: who the client is, what the project is, what version this is, and when it was created.
A file name that does this looks like this:
NikeCampaign_HeroVideo_v3_2026-05.mp4
A file name that does not do this looks like this:
render_v3_FINAL_USE THIS.mp4
The convention to follow:
[Client]_[Project]_[Description]_[Version]_[Date].[ext]
Nike_Q2Campaign_HeroVideo_v3_2026-05.mp4
Nike_Q2Campaign_SocialCut_15sec_v1_2026-05.mp4
Nike_Q2Campaign_SocialCut_9sec_v1_2026-05.mp4
A few rules:
- Use underscores, not spaces. Spaces in file names cause problems in browsers and some download tools.
- Use ISO date format (YYYY-MM or YYYY-MM-DD), not "May" or "05-22". ISO dates sort correctly.
- Never write "FINAL" in a file name. The version number is the source of truth. If you delivered v3 and then v4, calling v3 "FINAL" is immediately wrong.
- Use lowercase extensions (
.mp4, not.MP4). Inconsistent capitalisation looks sloppy.
Folder structure to send with every delivery
If you are delivering multiple files for one project, the folder structure is as important as the file names. A flat pile of files forces your client to make sense of something that already has structure in your mind.
A clear structure for a video delivery looks like this:
Nike_Q2Campaign_Delivery_2026-05/
├── exports/
│ ├── Nike_Q2Campaign_HeroVideo_v3_2026-05.mp4
│ ├── Nike_Q2Campaign_SocialCut_15sec_v1_2026-05.mp4
│ └── Nike_Q2Campaign_SocialCut_9sec_v1_2026-05.mp4
├── audio/
│ └── Nike_Q2Campaign_Music_Licensed.mp3
└── README.txt
The README.txt is the most overlooked part of a professional delivery. It does not need to be long. Three to five lines:
Nike Q2 Campaign Delivery
Delivered: May 2026
Contact: your@email.com
exports/: Final video files ready for upload to Meta and YouTube.
HeroVideo v3: approved final. Social cuts v1: awaiting your review.
This eliminates the "which file do I use" email. It also shows that you run a real operation, not just a freelancer who hits Export and sends a link.
For design deliveries, the structure works the same way:
Acme_BrandRefresh_Delivery_2026-05/
├── print/
│ ├── Acme_BusinessCard_Print_v2_2026-05.pdf
│ └── Acme_Letterhead_Print_v1_2026-05.pdf
├── digital/
│ ├── Acme_Logo_RGB_v2_2026-05.png
│ └── Acme_Logo_RGB_v2_2026-05.svg
├── source/
│ └── Acme_BrandRefresh_Source_v2_2026-05.ai
└── README.txt
What the client sees when they open your link
The delivery page is the last thing you control before the work reaches your client. Most freelancers give this zero thought and use whatever default the transfer service provides.
A generic WeTransfer or Dropbox page looks like you are a user of WeTransfer or Dropbox. It looks like the file is coming from an internet service, not from a professional.
What a professional delivery page shows:
Your name or studio name at the top. Not WeTransfer or Google Drive. Your name. The page should feel like an extension of your studio.
The file name, size, and expiry. The client should be able to confirm they have the right file before downloading 8GB. They should also know how long they have.
One download button. No navigation, no ads, no "also try our premium plan" banner. One action: download.
A clean URL. A generic WeTransfer URL makes the page look like a shared file, not a professional delivery.
On TrunkTransfer Starter, the download page shows your display name and studio name with no TrunkTransfer branding, and your client gets a 30-day download window. Start your 7-day trial.
The delivery checklist
Before you share any link with a client, run through this:
Files:
- Every file named with client, project, version, and date
- No spaces in file names
- No "FINAL" in file names
- File extensions are lowercase
Folder structure:
- Files organised into subfolders by type (exports, audio, source, print, digital)
- README.txt in the root folder with delivery date, what each folder contains, and your contact
- No leftover work-in-progress files or old versions included
Delivery link:
- Using a dedicated delivery link, not a cloud storage folder
- Download page shows your name, not a generic service name
- Expiry is long enough: 30 days minimum on a professional delivery
- Password protection on for anything unreleased or confidential
- Download notification turned on so you know when the client downloads
Communication:
- Link sent with a one-line note on what the client is receiving and any next steps
- You have the link saved somewhere so you can resend it without re-uploading
The upgrade that makes the most difference
Most of what is described here is free. File naming and folder structure are habits. The README takes two minutes. The only thing that costs money is the delivery page itself.
For client deliveries, TrunkTransfer Starter ($9/mo) gives you:
- your own custom domain for every delivery, like file.yourstudio.com
- your studio name on the download page
- a 30-day file availability window
- password protection
- instant email notifications when your client downloads the files
The full professional delivery workflow, start to finish
A client who receives a well-named file inside a clear folder structure, via a branded download page with a 30-day window, assumes you run a tight operation before they have even opened the file. A client who receives render_v3_FINAL_USE THIS.mp4 via a generic Dropbox or WeTransfer link assumes the opposite.
The work is the same. The perception is not.
Frequently Asked Questions
How should I name files before delivering them to a client?
Use a consistent structure that communicates client, project, version, and date without needing to open the file. A format like Client_Project_Description_v2_2026-05.mp4 is self-explanatory at a glance. Use underscores instead of spaces, ISO date format, lowercase extensions, and never write "FINAL" in a file name. Version numbers are the source of truth.
Should I include a README in every delivery?
Yes. A README.txt in the root of the delivery folder takes two minutes to write and eliminates the "which file do I use" email. It should list the delivery date, what each subfolder contains, and who to contact with questions. Clients read it. It signals that you run an organized operation.
What folder structure should I use for a brand video delivery?
Organize by use case: one folder for exports (final video files by platform), one for audio (music, stems), and one for source files if included. Each file named consistently. The structure should be obvious to a client who has never seen your system before. Avoid flat folders with dozens of unnamed files.
Does the delivery page matter if the files are well-organized?
Yes. A well-organized folder inside a WeTransfer or Google Drive page still arrives under their branding. The client sees WeTransfer's logo before they see your files. A branded delivery page with your studio name, logo, and a 30-day window signals the same care and professionalism as the file organization itself. Both things are part of the delivery.
How long should a client have to download their files?
30 days minimum on any professional delivery. Marketing teams share links internally, and someone will come back two weeks after you sent it. TrunkTransfer Starter gives you 30 days, which covers the vast majority of professional delivery situations without follow-up.
What is the easiest way to set up a branded delivery page?
TrunkTransfer Starter ($9/mo) lets you add your studio name, logo, and optionally a custom domain in a few minutes. Every delivery link you send from that point shows your branding, not TrunkTransfer's. No developer needed.
