Secure Way to Send Files to Clients: 5 Options
The safest everyday way to send sensitive files to clients is a link-based tool that limits who can open the file, adds an expiry date and shows who opened it, not an email attachment.
This post is for small business owners, agencies and freelancers who swap IDs, contracts, invoices and tax forms with clients. You will get a decision table that compares five options, a short checklist of settings to turn on, and a few steps you can finish in about 15 minutes. You do not need to be technical.
Why email attachments are the weak spot
Email is fine for a casual note. It is a poor home for a passport scan.
An attachment makes copies. One sits in your sent folder, one in your client's inbox, and more on every phone and laptop that syncs those mailboxes. Those copies stay there for years, and you cannot take them back. If someone guesses or steals one mailbox password, they can search for the word 'passport' and find everything.
There is also a trust problem. Criminals can fake the sender address on an email, which is called spoofing. You can see how exposed your own domain is with the email spoofing checker. Clients who get a surprise 'please upload your documents here' message should also be careful, because that is a classic phishing pattern (CISA guidance on phishing).
The fix is not complicated. Send a link to a file kept in one controlled place, and control who can open it and for how long.
The 5 options compared
Here is a quick decision table. 'Control' means your ability to limit who can open a file and see who did.
| Option | Best for | Control | Effort | Main risk |
|---|---|---|---|---|
| 1. Plain email attachment | Non-sensitive files | Very low | None | Copies live in many inboxes forever |
| 2. Cloud-drive share link (Google Drive, OneDrive, Dropbox) | Occasional documents to known people | Medium, if set up correctly | Low | 'Anyone with the link' left on by mistake |
| 3. Hosted upload portal (a file request link or client portal) | Collecting IDs and forms from clients | Medium to high | Low to medium | Weak default settings, no expiry |
| 4. Secure file transfer tool (SFTP or a managed transfer service) | Regular exchange, large files, regulated clients | High | Medium | Setup mistakes, shared accounts |
| 5. Encrypted file plus password sent separately | Any channel, as an extra layer | High for that file | Medium | Password sent in the same email |
Most small businesses do well with option 2 or 3. Option 5 is a seatbelt you can add to any of the others.
What each option really means
1. Email attachment
Use it only for files you would be fine seeing in the wrong hands, such as a public brochure. Many mail servers encrypt messages while they travel, but the message is generally readable once it lands in a mailbox. For IDs and contracts, pick something else.
2. Cloud-drive share link
You probably already have this. Google Drive, OneDrive and Dropbox can all share a file by link.
The danger is the setting called 'Anyone with the link'. Anyone who gets the link can open the file, and links get forwarded and pasted into chats. Choose 'Restricted' or 'Specific people' instead, so the client has to sign in with a named email address.
In Google Drive, this is under Share, then General access, then Restricted. You can also set an expiration date on access you give to a named person. Check the Google Drive sharing help for the current steps. Link passwords and expiry dates on public links are often limited to paid plans in other tools, so check your plan.
3. Hosted upload portal (a secure file upload portal)
This is the right choice when a client needs to send you something. You create a request link, the client uploads, and the files land in a private folder. The client never sees your other files.
Good tools offer 'file request' features. Examples are Dropbox file requests, a Google Form with a file upload question (uploaders must sign in to a Google account), or the client portal built into your accounting or CRM software. Pick a hosted tool from a company that does security as a full-time job. This is usually safer than building your own.
4. Secure file transfer tool
Secure file transfer tools include SFTP servers and managed services built for businesses. SFTP means SSH File Transfer Protocol. It moves files over an encrypted connection and needs a login.
This route fits when you swap files with the same clients every week, send very large files, or answer to a client's security questionnaire. It takes more setup, so ask your IT person or hosting provider to help. Give each client their own account, not a shared one.
5. Encrypted file with a separate password
You can lock the file itself so the channel matters less. On a Mac or Linux machine with GnuPG installed, this command locks a file with a password:
gpg --symmetric --cipher-algo AES256 contract.pdf
It creates contract.pdf.gpg. Your client opens it with:
gpg --decrypt contract.pdf.gpg > contract.pdf
Your client needs GnuPG installed to open the file (Gpg4win on Windows), so check this works for them before you rely on it. Use a long, unique passphrase. A weak one makes the encryption easy to guess.
On Windows, 7-Zip can create an encrypted archive instead, and your client needs 7-Zip to open it. Use the 7z format, choose AES-256 as the encryption method and tick 'Encrypt file names'. Use a long, unique passphrase here too.
Never send the password in the same email as the file. Use a phone call, a text message or a chat app instead. Be honest about the tradeoff: many clients find this awkward, so keep it for your most sensitive files.
A risky upload form on your own website
Many small sites have a 'Send us your documents' form built with a plugin. If it is set up carelessly, it can do harm in two ways. It can store your clients' IDs where anyone with the file address can download them, or it can accept a malicious file and let an attacker run code on your server.
The OWASP File Upload Cheat Sheet lists the main defenses. In plain English:
- Only allow the file types you need, such as PDF, JPG and PNG.
- Set a maximum file size.
- Rename uploaded files so attackers cannot choose the name.
- Store files outside the public part of the site, or in private cloud storage.
- Require a login before anyone can view or download an upload.
- Run the site over HTTPS only. See OWASP's Transport Layer Security guidance.
If you cannot tick all of these, use a hosted portal (option 3) and remove the form. For a bigger picture, read is my website hackable.
The settings checklist
Whichever tool you choose, turn on these four things. Not every tool offers all of them, and that is a good way to compare tools.
- Link expiry. Set files to stop working after a set time, such as 7 days. Old links are a common source of leaks because people forget they exist.
- A password or a named sign-in. Prefer 'sign in with this email address' over a link anyone can open. If you use a link password, send it by a different channel.
- Access logs. Make sure you can see who opened or downloaded a file, and when. If a client says 'I never got it', or you suspect a leak, the log gives you answers.
- Encryption. Look for encryption in transit (HTTPS, or SFTP for transfer tools) and encryption at rest (the stored file is scrambled on the provider's disks). Reputable providers describe this on their security pages. If a provider does not say, ask.
Two extras worth the 30 seconds:
- Turn on two-step login (multi-factor authentication, or MFA) for your own account. A strong file tool is useless if someone guesses your password.
- Delete files after the job is done. A file you no longer hold cannot leak from you.
A 15-minute setup plan
- List the documents you handle that are sensitive (IDs, contracts, bank details, health or tax forms).
- Pick one tool from the table and use it for all of them. One habit beats three half-used tools.
- Open its sharing settings and turn off 'anyone with the link' as the default.
- Set a default expiry, such as 7 days, if the tool allows it.
- Check where the access log lives and look at it once.
- Write a two-line message to send to clients: 'I will send you a secure link. I will never ask you to email your ID.' That also helps clients spot fake requests.
When a tool is not enough
A good tool protects the file in transit and at rest. It cannot fix a weak password, a client who forwards the link, or a flaw in your own website. If your upload form or client login lives on your site, it is worth testing. A free website security check is a start. It looks at your site from the outside only, so it does not replace a person testing the form by hand.
Key takeaways
- Email attachments leave permanent copies in many inboxes. Keep them for non-sensitive files.
- For most small businesses, a cloud-drive link set to 'specific people' or a hosted upload portal is the practical choice.
- Use SFTP or a managed transfer service for regular, large or regulated exchanges.
- Turn on link expiry, a password or named sign-in, access logs and encryption, and add MFA to your own account.
- If you built your own upload form, follow the OWASP file upload rules or replace it with a hosted tool.
What to do next
If your website collects documents through a form or client login, a person should test it. A Bug Circuit audit is a manual security test of one website by a real engineer, ending in a written report with every issue, its severity, evidence and fix steps. The Essential plan is $49 one-time for 1 website. It is a small-site audit, not a compliance certificate or a multi-week enterprise test. We report problems and explain the fix. Fixing is a separate service that we quote first.
A real human security engineer audits your whole site by hand and sends a full report: every issue, its severity, and the exact fix. From $49, with a 14-day money-back guarantee.
See pricing