How to Collect Files From Clients Without the Email Mess

Before the tools, one thing worth naming: "collect files from clients" is really two jobs wearing one search. Sometimes you need a legal document or a signed PDF from one person, once. Sometimes you need 400 raw photos off a client every single week. Those want different setups, and a tool that's perfect for one is a bad fit for the other. Keep your actual case in mind as you read, because the honest answer depends on it.

Pick by the shape of your problem, not by whichever brand you've heard of. One-off document from one person: a Dropbox or OneDrive file request is free and takes two minutes. Text plus files together: a form. Recurring paperwork with deadlines: dedicated collection software. Lots of files, ongoing, on a page that's yours and doesn't expire: your own upload page. The rest of this walks the tradeoffs so you're not switching tools in three months.

The best file collection setup is the one your least technical client can use on their phone without calling you.

• No account required on their end. The single biggest drop-off point is a login wall. Every account a client has to create is a fraction of them who give up and email you instead. If the upload link asks the client to sign up, you've reintroduced the friction you were trying to remove.
• One folder, named per client or project. Files that land in a shared pile with names like IMG_4021.jpg are a problem you've deferred, not solved. Route each client's uploads into their own folder so you're never guessing which invoice belongs to whom.
• Say exactly what you want. "Upload your documents" gets you a blurry photo of a photo. "PDF or JPG, both sides of the ID, under 10MB each" gets you usable files. Set file-type and size limits in the tool where you can, and put the naming convention in the instructions.
• Automate the chasing. The reminder email is the real work of file collection, and doing it by hand is where the hours go. Tools that send follow-ups on a schedule until every item's in will save you more time than any other single feature.
• Confirm receipt without attaching the file back. Clients want to know the upload worked. Send a confirmation, but never bounce the file back through email; that's how sensitive documents leak. Keep the file in the system and just say "got it."
• Match the security to the contents. Collecting event photos and collecting tax records are not the same risk. For anything sensitive, look for encryption in transit (HTTPS) and at rest, and for regulated work, the relevant compliance (HIPAA, SOC 2, PCI) stated plainly. Don't pay for a fortress to collect vacation snapshots, and don't collect PHI through a tool that can't name its compliance.

In July 2025, WeTransfer updated its terms of service with language granting itself a broad license to user content, including wording about machine learning. People read it as "they can train AI on my files," and creative professionals in particular revolted, with some lawyers advising clients to stop using it. WeTransfer walked the wording back within about two weeks and clarified it doesn't use customer files to train AI models or sell them to third parties; the machine-learning line, it said, was meant to cover automated content moderation, not generative AI.

Whether you find that reassuring or not, the lesson generalizes. When you hand a client's files to a free service, you're both bound by that service's terms, and those terms can change under you. If you're collecting other people's intellectual property, contracts, or private documents, the terms of service and privacy policy are not fine print, they're the product. A page you host on your own domain sidesteps the question entirely, because the terms are the ones you set.

Here's the honest positioning. Tonta is upload infrastructure, built for people who build things, so it isn't a two-click consumer app like a Dropbox file request. What it gives you that those don't is a real upload page on your own site: you drop a single script tag onto a page, point it at Tonta's hosted endpoint, and you've got a working uploader with storage and a CDN behind it, no server of your own to run and no cloud bucket to configure. Files from your clients land in one folder in your dashboard, and the person uploading never makes an account.

The reasons to reach for that over a free file-request link are specific. You want the link to live permanently instead of expiring. You want it on your own domain, with your look, not somebody else's logo. You want the files to be governed by your terms, which matters more the more sensitive they are. If you're collecting images specifically, Tonta resizes and converts them to WebP as they arrive, so 400 phone photos don't sit in your storage as 400 giant HEIC files. The upload endpoint is locked to the domains you allow, so the link can't be lifted and reused from some other site. The free tier is 5GB with one uploader and no credit card, which is enough for a single collection page; heavier or multi-client use steps up through the paid plans.

Where it's the wrong tool: if you need built-in per-document checklists and automated reminder sequences chasing clients through a paperwork list, dedicated collection software is purpose-built for that and Tonta isn't trying to be. And if you want something you can set up in the next sixty seconds with zero technical comfort, a Dropbox or OneDrive file request is genuinely the faster path. Tonta's the answer when "on my own domain, that I own, that doesn't expire" is the part that matters to you.