
There are three real ways to create a file sharing link in 2026: dedicated services, cloud storage, and self-hosted. Most people use the first option wrong — they skip the security controls that separate a useful link from a leaky one. This guide covers every method and the five settings worth caring about.
Surya Prakash
Author
TL;DR: To create a file sharing link in 2026, you have three real choices: (1) a dedicated file-share service like Uploadex / WeTransfer / Smash — upload, get link, paste link wherever; this is the cleanest workflow for one-off sends. (2) Cloud storage like Google Drive / Dropbox / OneDrive — right-click the file → Share → "Anyone with the link"; good if you and the recipient are in the same ecosystem. (3) Self-hosted via rclone + Cloudflare R2, or a Nextcloud instance — full control, technical setup. For 95% of cases, option 1 is the cleanest — especially if you need password protection, link expiration, or download caps, none of which Google Drive / Dropbox give you on consumer plans.
I share files via link about a dozen times a day — design files to clients, screenshots to support tickets, datasets to collaborators, backups to my own remote storage. Each of those uses a different tool, picked for the threat model and the recipient's tech level.
Here's the honest version: "how to create a file sharing link" isn't one workflow, it's three. Picking the wrong tool for the wrong job is why people end up emailing 50 MB attachments that bounce, or asking clients to "request access" to a Google Drive link for the fifth time.
This guide walks through every method that works in May 2026, ranked by use case, with the security controls each one supports.
In order of cleanest to most niche:
Below, each method with the actual steps.
This is what I default to. The tools are purpose-built for "create a link, send it, forget about it."
/f/contract-abc-2026 instead of a random ID)
| Service | Free tier file size | Security controls free | Best for |
|---|---|---|---|
| Uploadex | 2 GB | Password ✓, expiry ✓, download cap ✓ | Everyday secure sharing |
| WeTransfer | 3 GB total/month (post-2024 changes) | Password ✗, expiry 3 days fixed | Brand recognition |
| Smash | unlimited | Password ✗ (Pro only), 14-day expiry | No-account "drop-and-go" |
| SwissTransfer | 50 GB per transfer | Password ✓, expiry up to 30 days | EU privacy |
| Tresorit Send | 5 GB | End-to-end encrypted | Zero-knowledge transfers |
For a full ranked comparison with pricing and trade-offs, see 9 Best WeTransfer Alternatives.
If the file is already in your Google Drive / Dropbox / OneDrive, you can generate a share link without uploading anywhere else.
Caveats: - No password protection on consumer / personal plans - No link expiration on consumer / personal plans (Workspace Business+ adds it) - No download cap - "Anyone with the link" means anyone — if the link leaks, anyone has the file forever - Free Google account has a 15 GB total storage cap; uploading a 5 GB file fills 33% of it
Caveats: - Password + expiry are paid features (Plus and above) - Free tier only 2 GB total storage
Caveats: - Password protection requires Microsoft 365 Personal or Family ($6.99–9.99/month) - Free tier only 5 GB storage
Caveats: - No password, no expiry, no download cap on any plan - Only useful if recipient is on an Apple device or willing to use the web viewer
For a deeper look at the cloud-storage alternatives, see 8 Best Google Drive Alternatives and the encrypted cloud storage explainer.
For developers who want full control — over expiry, access logging, custom domains, and no third-party storage — self-hosting is the answer. Three real options:
# Install
brew install rclone # macOS
sudo apt install rclone # Linux
# Configure R2 (free tier: 10 GB storage)
rclone config # interactive setup
# Upload a file
rclone copy ./bigfile.zip r2:my-bucket
# Generate a signed URL valid for 24 hours
rclone link r2:my-bucket/bigfile.zip --expire 24h
The output URL is unguessable, expires automatically, and can be revoked by deleting the file from the bucket.
Nextcloud is a full self-hosted cloud-storage suite — Drive replacement with share links, expiry, password protection, and audit logs. Run it on a $10/month VPS or a home server.
Once installed, share links work like Drive's but with stronger controls: password mandatory for external links, expiry configurable, download counters built in, end-to-end encryption available via the E2EE app.
ProjectSend is purpose-built for client-deliverable file sharing — upload files, generate per-client links, email notifications when downloaded. Open source, simple, no Nextcloud's full kitchen-sink complexity.
share.yourbrand.com)For more on self-hosted file sharing options, see self-hosted file sharing reviewed.
If you take nothing else from this guide, take this. A file sharing link is more than just a URL — the controls around it determine whether your file is safe.
1. Password protection. A password on the link itself, communicated through a different channel (text, separate email, voice call). Defeats forwarded-link attacks.
2. Link expiration. The link self-destructs after a set time — 24 hours, 7 days, 30 days. Smaller window = smaller attack surface.
3. Download cap. The link stops working after N downloads. For one-to-one sends, set cap = 1.
4. Revocation. You can kill the link from your dashboard, immediately, without deleting the file. Useful when you realize you sent to the wrong address.
5. Per-link analytics. Who downloaded, when, from what country. Helps you spot suspicious access.
Consumer Google Drive / Dropbox / iCloud give you exactly zero of these on free plans. Dedicated file-share services (Uploadex, SwissTransfer, etc.) give you most or all.
For why these matter and the threat model behind each, see how to send large files securely — same controls, applied to the file-transfer use case.
Three I see constantly:
1. Sending the password in the same email as the link. Defeats the purpose. If the email is breached or forwarded, attacker has both. Use a different channel.
2. Default-permissive sharing. "Anyone with the link" on a Google Drive file → the link gets forwarded → company info goes public. Use restricted sharing or dedicated services with password + cap.
3. Forgetting to set expiry. A file shared in 2022 with "no expiration" is still accessible in 2026. Half the data leaks I see in security forums are five-year-old share links that someone forgot to kill.
Three ways: (1) use a dedicated service like Uploadex / WeTransfer / Smash — upload, click "generate link," copy, send. (2) Use cloud storage like Google Drive / Dropbox / OneDrive — right-click the file → Share → set "Anyone with the link" → copy. (3) Self-host via rclone + S3 or Nextcloud. Option 1 is easiest and most secure.
The free tiers of Uploadex (2 GB per file), Smash (unlimited file size, no account), SwissTransfer (50 GB per transfer, no account), Google Drive (15 GB total storage), and Dropbox (2 GB total) all let you create share links for free. Best free balance of file size + security: SwissTransfer or Smash.
Same as any file — upload the video to Uploadex / Smash / WeTransfer / Google Drive → generate a share link → send. Don't bother converting the video to a direct URL — services give you a download page that handles browser compatibility, mobile playback, and tracking.
Yes — on Uploadex (free), Smash Pro, SwissTransfer (free), Dropbox Plus and above, OneDrive (Microsoft 365 Personal+), and Tresorit Send (free). Consumer Google Drive and consumer iCloud do not support password-protected links.
It depends on the service: WeTransfer free — 3 days. Smash free — 14 days. SwissTransfer free — up to 30 days. Uploadex — configurable, up to never (paid plans). Google Drive / Dropbox / OneDrive — until you delete the file or revoke sharing.
Use a service that supports password protection + download cap of 1. Examples: Uploadex (free), Tresorit Send (zero-knowledge encryption), SwissTransfer (with password). Send the password through a different channel than the link itself.
A service with end-to-end / zero-knowledge encryption (Tresorit Send, Proton Drive share links) where the provider cannot read the file, combined with a password sent through a different channel, a short expiration (under 24 hours if possible), and a download cap of 1. For everyday "secure enough" sharing without zero-knowledge, Uploadex with the same controls is the practical balance.
Yes — instead of "Anyone with the link," choose Restricted and add specific recipient emails. They'll be prompted to sign in to a matching Google account to access. For non-Google recipients, this loop is friction-heavy; a dedicated file-share service with password protection is usually a better UX.
Creating a file sharing link in 2026 isn't a single workflow — it's a choice between:
For 95% of cases, option 1 is the cleanest — especially if you need password protection, link expiry, or download caps, which consumer cloud storage doesn't offer.
Whichever route you pick, the five controls to verify are: password + expiry + download cap + revocation + analytics. If your chosen tool is missing any of those, ask whether you'd be comfortable with the file forwarded, archived forever, and downloaded by an unknown party — because that's the failure mode you're accepting.
For the full secure-transfer workflow, see how to send large files securely and the Gmail-specific guide. For service comparisons, 9 Best WeTransfer Alternatives and 8 Best Google Drive Alternatives.
Sources:
- Google Drive sharing documentation
- Dropbox sharing documentation
- Microsoft OneDrive sharing
- Cloudflare R2 documentation
Author
Surya Prakash is the founder of Uploadex. He writes about secure file sharing, large file workflows, and the engineering decisions behind running a fast, global delivery network. Previously built tools for creators across India, the US, and Southeast Asia.