The Designer's File Delivery Playbook: From Review to Final Handoff
You design the work. Delivering it shouldn't be harder than creating it. A practical guide to sharing design files with clients — from draft review to final handoff.
Designers are good at making things. We’re less good at the last mile — actually getting the files to the client in a way that doesn’t create three email threads, a Slack conversation, and a text message that says “sorry, can you resend that?”
This guide covers the full delivery cycle for designers on Mac: sharing work-in-progress for review, managing feedback rounds, delivering final files, and handling the “do I owe you the source files?” conversation.
Phase 1: Sharing work-in-progress
During the design process, you need to share drafts for feedback. The goal is fast iteration with minimal friction.
For UI/UX design: Share the design tool link
If you’re working in Figma, share the Figma link. Don’t export PDFs or PNGs for review — that creates version confusion and strips away all the context (component names, spacing, states).
Set permissions carefully:
- “Can view” for most clients. They can comment but can’t accidentally move things.
- “Can edit” only for collaborators who need to make changes.
If the client isn’t comfortable with Figma, use Figma’s built-in presentation mode and share that link. It looks like a slideshow, not a design tool.
For print/branding: Export and share a PDF
Print clients typically expect a PDF. Export from InDesign, Illustrator, or whatever you use, and share via link — not email attachment.
Why a link, not an attachment:
- PDFs for print can be large (50+ MB with embedded fonts and bleeds)
- A link lets you update the file without resending
- You can track when the client opens it
Share through Swooshare, Dropbox, or Google Drive. Add a note: “This is a review PDF. Final files will be delivered separately after approval.”
For motion/video: Share a streaming link
Don’t send a 2 GB video file for review. The client won’t download it, and if they do, they’ll watch it on their phone where they can’t see the detail.
Upload to Frame.io (industry standard for video review), or use a share link with video preview. Swooshare shows video previews on the share page, so the client can watch before deciding to download. Vimeo with password protection also works.
Phase 2: Managing feedback
Keep feedback in one place
The worst outcome is feedback arriving via email, Slack, text, Figma comments, and a phone call — all for the same project. Before you send the first review link, tell the client where to leave feedback:
“You can leave comments directly in Figma [link]. If you prefer, reply to this email with your notes. Please keep all feedback in one place so nothing gets lost.”
Version naming
Never use “final,” “final_v2,” or “FINAL_REAL.” Use dates:
Brand_Review_2026-04-15.pdfBrand_Review_2026-04-22.pdf
Or numbered versions with dates:
Brand_v1_2026-04-15.pdfBrand_v2_2026-04-22.pdf
The client should always be able to tell which file is newest by looking at the name.
Phase 3: Final delivery
Once the client approves, it’s time to deliver the final files.
Structure the delivery folder
ClientName_Final_Deliverables/
├── Logo/
│ ├── Logo_Primary.svg
│ ├── Logo_Primary.png (transparent, 300dpi)
│ ├── Logo_Primary_White.svg
│ ├── Logo_Primary_White.png
│ ├── Logo_Icon.svg
│ └── Logo_Icon.png
├── Brand_Guidelines.pdf
├── Color_Palette.pdf
└── README.txtThe README should say:
- What’s included
- Recommended usage (web vs. print formats)
- Fonts used (with licensing note)
- Contact info for future requests
Choose the delivery method
| Deliverable size | Best method |
|---|---|
| Any size | Swooshare (no file size limit) |
| Occasional large files | SwissTransfer, Mail Drop |
| Very large / rush delivery | MASV, external SSD |
Set an expiry
Deliverable links should expire after 30-60 days. The client should download the files and store them on their end. If they need them again later, they can ask you — but a file sitting on a server indefinitely is a security and liability risk.
Send the delivery message
Keep it professional and clear:
Hi [Name],
Here are the final deliverables for [Project Name]: [link]
The folder includes the logo in SVG and PNG formats (primary, reversed, and icon), plus the brand guidelines PDF. Fonts used are Inter and Playfair Display — I’ve included licensing notes in the README.
This link will be active for 30 days. Please download and archive the files on your end.
Let me know if you need anything else!
Phase 4: The source files question
Every designer faces this eventually: “Can I get the source files?”
The answer depends on what was agreed in your contract:
If your contract includes source files: Deliver them. Package the InDesign/Illustrator/Figma/Sketch files in a separate folder labeled “Source_Files” and include a note about what software and version is needed to open them.
If your contract doesn’t mention source files: They’re not included by default. Source files represent your working methodology, your reusable components, and your competitive advantage. You can offer them as an add-on for an additional fee.
A reasonable middle ground: Deliver editable vector files (SVG, EPS) but not the working production files (AI with all your artboard iterations, InDesign with linked assets). The client gets files they can edit with any tool, and you keep your working environment private.
Whatever you decide, have this conversation before the project starts, not during delivery. Put it in the contract.
Phase 5: Archive
After the client confirms receipt:
- Expire or revoke the share link
- Archive the project folder on your local drive or backup
- Keep a record of what was delivered and when (screenshot the download confirmation if your tool provides analytics)
This protects you. If a client says “you never sent the final files” six months later, you have a dated delivery confirmation.
Common mistakes designers make
Sending working files instead of exported files. The client doesn’t need your 47-artboard Figma file with all your explorations. They need clean, exported, ready-to-use assets.
Not including usage instructions. A logo SVG without context is just a file. Include a one-page brand guideline (even for small projects) that shows minimum size, clear space, and color codes.
Using personal cloud storage for delivery. If you share from your personal Dropbox and reorganize your files later, the client’s link breaks. Use a dedicated sharing tool that creates independent links.
Delivering without confirming approval. Get written approval (“Looks great, approved!”) before sending final files. This protects against scope creep and revision requests after delivery.
Not setting a link expiry. A deliverable link from January is still accessible in December. That’s 11 months of your files on a server, accessible to anyone with the URL.
Related reading
- The freelancer’s guide to sending client deliverables — covers the general freelancer delivery workflow beyond design
- Secure file sharing on Mac — how to add passwords, expiry dates, and encryption to your delivery workflow
- What is a file request? — how to collect assets from clients without the email chaos