A few years ago a client sent me project files across three separate email threads — logos in one, copy in another, brand guidelines in a reply to an unrelated conversation from two weeks earlier. I spent an hour piecing it all together, still missed one attachment, and ended up using an outdated version of the logo. The client noticed. That was the last time I accepted deliverables over email.
Email was designed for messages, not file transfers. File size limits on attachments (typically 25 MB), no version tracking, no confirmation of receipt, and zero organization. Yet many teams still rely on it because they haven’t set up anything else. Collecting files from your clients without email is not just convenient — it prevents exactly this kind of silent failure.
There are three alternatives, each adding a layer of structure over the last: shared online storage, web forms with file submission fields, and dedicated client spaces. The right way to collect files depends on how often you handle file collection, from how many clients, and whether you need context around those transfers.
AI Key Takeaways — brief reading, less than 30 seconds (Claude)
- Email attachments fail at scale: 25 MB limits, no version tracking, no delivery confirmation, and no organization.
- Online storage (Google Drive, Dropbox, OneDrive) is the fastest fix — share a directory or request link, and clients submit directly without needing special software.
- Web forms (Jotform, Typeform, Google Forms) add structure by collecting metadata alongside files — project name, asset type, deadlines.
- Dedicated client workspaces (YetOnePro, Canto, Bynder) provide a professional, persistent space for recurring client relationships with access controls and audit trails.
- Start with the simplest solution that works. Shared directories for one-off drops, forms for structured intake, dedicated spaces for ongoing collaboration.
- File size limits vary dramatically: forms cap at 10–100 MB, online storage handles gigabytes, and DAM platforms typically support 2+ GB per file.
Glossary6 terms
- File Request: A link you send to a client so they can submit files to a specific location without seeing your other content. Dropbox, OneDrive, and most DAM platforms offer this feature.
- Client Portal: A dedicated, password-protected space where a client can send you files, view shared assets, and manage their submissions. Often customized with your logo and colors.
- DAM: Digital Asset Management. A platform designed to store, organize, and distribute media files — photos, videos, design assets. Automates metadata extraction and makes every file searchable.
- File Size Limit: The maximum size of a single file that a service accepts. Email caps at 25 MB for most providers. Online forms allow 10–100 MB. Cloud storage and DAM platforms handle files from 2 GB to 250 GB.
- Metadata: Information attached to a file — author, creation date, project code, tags. Forms collect metadata through fields; DAM platforms extract it automatically from the file itself.
- Onboarding Intake: The process of collecting files and information from a new client at the start of a project. Typically handled with a web form that gathers documents, assets, and context in one submission.
Three Ways to Collect Files from Clients
Before diving into specific tools, it helps to understand the three approaches. Each one adds a layer of structure and professionalism over the last:
- Cloud storage — share a directory, let clients drop files in. Quick to set up, no learning curve for either side.
- Web forms — collect files alongside structured data (project name, description, deadlines). Better when you need context with every submission.
- Client workspaces — a dedicated, professional space where clients add, preview, and manage their files. Best for agencies and teams with recurring client relationships.
Let’s look at each one in detail.
Collect Files via Cloud Storage Folders
The simplest approach: create a shared directory in your online storage and send the link to your client. They open it, drag their files in, done. This kind of file sharing requires no forms to fill out, no accounts to create (in most cases), and no software to install. Clients can send you files directly, including large files that would bounce as email attachments.
This works well when you have a small number of clients and don’t need metadata or structure beyond the directory name. The downsides appear at scale: no automatic notifications when files arrive, no way to attach project context, and clients can sometimes see each other’s files if permissions are misconfigured.
Google Drive
Most people already have a Google account, which makes Drive the obvious first choice. Create a folder, share it with your client’s email, and they can add files directly. One friction point: clients without a Google account get prompted to sign in. And there’s no built-in file request feature — you’d need a third-party add-on or a Google Form.
OneDrive
Bundled with most M365 business plans (1 TB per user). The File Request feature is genuinely useful: clients drop files into a specific location without seeing anything else in your storage, and submissions work even without a Microsoft account. Where it falls short is ecosystem lock-in — if your client isn’t in the Microsoft world, the interface feels unfamiliar.
Dropbox
Pioneered the “file request” concept and still does it well. Create a request, optionally set a deadline, and share the link. Clients submit without needing an account or seeing your other content — everything lands where you choose. The interface is clean enough that I’ve never had a client ask how it works. The free 2 GB tier fills up fast when receiving client files.
Box
Built for compliance, data protection, and granular permissions. The file request feature supports collecting metadata alongside submissions — clients fill in fields like project code or department. If you need to collect sensitive files or handle sensitive information with an audit trail, Box is built for that.
Other Solutions
Sync.comcan encrypt files end-to-end and is a strong pick for privacy-conscious teams. pCloudhas lifetime plans that eliminate recurring costs. iCloud Driveworks well for Apple-heavy teams, but its sharing and file request features lag behind Dropbox and OneDrive.
Collect Documents Through Online Forms
Sometimes a shared folder isn’t enough. You need the client to tell you what the file is — which project it belongs to, what type of asset it is, whether it’s final or a draft. Online forms let you collect documents and files together in a single submission, turning a loose transfer into structured document collection.
This approach shines for intake workflows: onboarding a new client, collecting brand assets at the start of a project, or gathering documents from clients for a campaign. Instead of asking clients to send documents into a directory and hoping they label things correctly, a form captures client documents with the context you need — project name, deadline, file type — in one step.
Jotform
Full-featured form builder with drag-and-drop editing, conditional logic, and multiple files per submission. Integrates with Google Drive, Dropbox, and most project management tools. You can configure automated reminders to nudge clients who haven’t submitted yet — including a reminder email on a schedule.
Typeform
Shows one question at a time in a conversational flow — feels less like a form and more like a guided conversation. Be aware: per-response pricing gets expensive at volume, and files are capped at 10 MB each. That rules it out for anything heavier than documents and compressed images.
Google Forms
Free, familiar, and good enough for many use cases. Submitted files go straight to your Google Drive with file type restrictions and size limits per question. One thing to know: respondents must sign in with a Google account to attach files — a hard requirement that can be a dealbreaker for external clients.
Microsoft Forms
Integrates tightly with OneDrive and SharePoint. Simple, clean interface. Important: file attachments only work within your organization. External clients cannot attach files unless they belong to the same M365 tenant. For external collection, pair it with a OneDrive request link instead.
Other Solutions
Cognito Formshas a generous free tier with file uploads and payment integration. Formstacktargets enterprise teams with compliance and approval workflows — it’s closer to document collection software than a simple form builder. Airtablecombines form submissions with a database backend — useful when you need to track submissions over time, but it’s more of a project management tool than a form builder.
Collect Client Files via Branded Portals
When you work with the same clients repeatedly — an agency managing multiple accounts, a studio receiving assets from a dozen clients a month — a shared folder or a web form starts to feel improvised. Clients notice. A dedicated client workspace gives you a professional space where clients request files, submit what you need, and see only what’s relevant to them.
These platforms are the most structured option. They bring automation to file collection: custom styling, access controls per client, submission notifications, metadata tagging, and audit trails. You pay for that with more setup time and higher cost — but for teams that receive files regularly, the investment pays back in fewer lost files and a more professional client experience.
Disclosure: YetOnePro is our product. We’ve included it alongside competitors and describe all platforms honestly. We encourage you to verify with free trials.
Acquia DAM (Widen)
Enterprise-grade digital asset management with client-facing hub capabilities. Handles large media libraries, guidelines enforcement, and controlled distribution. External contributors send files directly into your asset library with predefined metadata. Powerful, but not practical for small teams.
Bynder
Asset management platform with DAM at its core. Sharing hubs let you create dedicated spaces for clients and partners. The Creative Workflow module handles review-and-approval cycles, and integrations with Figma and Adobe make it popular with design teams. Sales-led pricing makes it impractical for smaller teams.
Canto
DAM focused on visual assets — photos, videos, and design files. Sharing features let you create collections and distribute via personalized links. Submission requests allow clients to send files with metadata, and AI-powered tagging organizes incoming assets automatically. More accessible than Acquia or Bynder, though still designed for teams.
YetOnePro
All features unlocked from day one — including client portals, share links, visual annotations, and automatic metadata extraction. You can automate the entire way to gather files from customers and partners in one place. Share links create a custom page where clients drag and drop; the client area gives them a persistent space to add files, browse, and download. The free plan gives you 2 GB and one invited member, so you can test everything before committing.
Other Solutions
Filecampoffers unlimited users on every plan with storage-based pricing — starting at $29/month. Brandfolder(by Smartsheet) focuses on asset distribution with guest submission capabilities. Frontifycombines design guidelines with asset management and has a growing sharing feature set.
How to Choose Your File Collection Method
Each method works best in a different context. Here is a side-by-side comparison to help you decide which fits your situation:
| Criteria | Cloud Storage | Online Forms | Client Portals |
|---|---|---|---|
| Setup time | Minutes | 30 min – 1 hour | 1 – 4 hours |
| Cost | Free – $12/mo | Free – $50/mo | £5/mo – $500+/mo |
| Client experience | Folder with drag-and-drop | Guided form with fields | Dedicated space with navigation |
| Metadata collection | None (file name only) | Custom fields per submission | Automatic + custom metadata |
| Customization | Provider’s interface | Customizable (limited) | Fully custom |
| File size limits | 5 – 250 GB per file | 10 – 100 MB per file | Usually 2+ GB per file |
| Best for | Quick, one-off file drops | Structured intake with context | Recurring client relationships |
These approaches layer well together. Many teams use a Google Form for initial onboarding intake and then move the client to a dedicated workspace for ongoing file exchange. Pick the simplest option that works today, and add structure when the volume demands it.
Stop Losing Files from Clients in Email
Email was never built to collect files. It lacks size handling, version tracking, organization, and any kind of structure. The moment you move to even a basic shared folder, you eliminate the most common headaches: bounced attachments, lost versions, and the endless “did you get my file?” follow-ups.
For quick, informal file drops, cloud storage (Google Drive, Dropbox, OneDrive) is the fastest path. When you need to collect documents alongside context — project names, deadlines, asset types — online forms (Jotform, Typeform, Google Forms) add structure without complexity. And when you work with the same clients repeatedly and want a professional, dedicated experience, a client workspace (YetOnePro, Canto, Bynder) pays for itself quickly.
You do not need the most powerful tool on day one. A shared Google Drive directory is infinitely better than email attachments. You can always move to forms or a dedicated workspace later — and you probably will, because once you find a reliable way to gather files without email threads, the old approach feels broken.
If you manage visual assets — photos, videos, design files — and want to see how share links and client portals work in practice, you can try YetOnePro for free. No credit card, no commitment. Add a few files and see what a proper collection workflow feels like.
Frequently Asked Questions #
What is the best way to collect large files from clients?
Can I collect files from clients who don't have accounts on my platform?
How do I organize files once clients send them?
Is it secure to let clients send files through a shared link?
Should I use a form or a dedicated workspace to collect client files?
