A Bitwarden Send Alternative Built for Sending Files

Bitwarden Send is excellent for shipping a secret string - a password, an API key, a note you don't want sitting in chat history. It can carry files too, but file sending is gated behind a paid plan, capped in size, and lives inside a password-manager workflow that isn't really shaped around "send this document to someone once." If files are your actual job, this guide lays out where Bitwarden Send shines, where it gets awkward, and what a file-first single-use link service does differently.

What Bitwarden Send does well

Credit where it's due: Bitwarden Send is one of the cleanest secure-sharing tools around, and for its core use case it's hard to beat.

• End-to-end, zero-knowledge encryption. A Send is encrypted on your device before it ever reaches Bitwarden's servers, and the decryption key travels in the link fragment. Bitwarden genuinely cannot read the contents. For sharing secrets, that's the gold standard.
• Text and file sends. You can send a plain text snippet or attach a file, from the web vault, browser extension, desktop app, or mobile app.
• A deletion date. Every Send has an expiry after which it's gone - no forgotten link lingering for years.
• Optional password and access limit. You can require a password to open a Send and cap the number of times it can be accessed, so the link alone isn't always enough.
• Hide-email and disable controls. You can keep your address off the share and deactivate a Send instantly if you change your mind.

If you're already a Bitwarden user and you mostly need to hand someone a credential or a short secret, you probably don't need anything else. The friction starts when the payload is a real file.

Where it falls short for files

Bitwarden Send was clearly designed secret-first, file-second, and it shows in a few places that matter once documents are involved:

• File sending is premium-gated. Text Sends are free, but attaching a file requires a paid Bitwarden plan. If you just want to send one PDF, you're signing up for a subscription to a password manager to do it.
• A file-size cap. File Sends are limited to roughly 500 MB. That's generous for a contract or an ID scan, but it's a hard ceiling, and it's part of a tool whose center of gravity is text.
• No metadata stripping. Bitwarden encrypts your file exactly as-is. That's correct for a zero-knowledge tool - it can't open the file to clean it - but it means the EXIF GPS coordinates in a photo, or the author and revision history baked into a PDF, travel along untouched and land on the recipient intact.
• Vault-centric UX. Sending a file means opening your vault or extension, finding the Send section, creating a Send, attaching, configuring, and copying the link. It's a few extra steps compared with a tool whose entire front door is "drop a file, get a link."

None of these are bugs. They're the natural consequences of building a secrets tool inside a password manager. They just add up if your real task is moving files to people.

What to look for in an alternative

If you're shopping for something file-first, these are the things worth checking before you commit:

• Files without a subscription tax. Can you send a file as a first-class action - ideally pay-as-you-go - rather than unlocking it through a broader paid plan?
• Single-use enforced on the server. A link that genuinely returns "gone" after one download, not just a polite client-side counter you have to trust.
• Expiry and an optional password. The same after-the-fact controls Send gives you, so a leaked link isn't an open file forever.
• Metadata handling. Does anything actually scrub EXIF, GPS, and document metadata before delivery, or are you on your own?
• No recipient account. The person you send to should be able to download with a click, not a signup.
• An abuse process. Boring but important: a service with a verified sender, a report-abuse path, and blocked executables is one that stays online and off email blocklists.

Bitwarden Send vs Bottleneck

Here's the honest side-by-side. They're built for overlapping but different jobs, so read the table as "which fits your task," not "which is better."

Notice the size column is the one place Bottleneck deliberately gives ground: 500 MB beats ~100 MB, and we're not going to pretend otherwise. Our cap is a safety choice, not a spec sheet to win. If your file is large and you don't need metadata scrubbing, Bitwarden Send (or another large-file tool) may simply be the better fit.

The honest trade-off

This is the part that matters most, so we'll state it plainly. Bitwarden Send is zero-knowledge and end-to-end encrypted: your file is sealed on your device and Bitwarden has no way to look inside it. Bottleneck is not zero-knowledge, and we won't pretend it is. Your file reaches us over an encrypted connection and we process it on our servers.

That difference is the whole point of choosing one over the other. Because we handle the file server-side, we can do something a zero-knowledge tool structurally cannot: actually open it and sanitize it - strip the GPS coordinates out of a photo's EXIF, drop the author name and edit history out of a PDF - then deliver the cleaned file and purge our copy after delivery. A zero-knowledge service can't scrub what it can't read. So the trade is real and symmetric: Send gives you secrecy from the operator; Bottleneck gives you a sanitized, single-use, accountable delivery and a purge afterward. Pick the property your situation needs.

That server-side model is also why our transfers stay accountable. Every send is tied to a verified sender, carries a report-abuse path, and blocks executable file types - the kind of guardrails that keep a file service alive instead of getting it blocklisted.

When to use which

Reach for Bitwarden Send when you're sharing a credential, an API key, a seed phrase, or a short secret note; when zero-knowledge encryption is a hard requirement; or when you're already living in Bitwarden and the file fits comfortably under its limit.

Reach for a file-first single-use service like Bottleneck when the payload is a document - a contract, an invoice, an ID scan, a photo - and you want the hidden metadata cleaned before it lands, a link that works exactly once and then reports "gone," no subscription just to attach a file, and no account on the recipient's side. You can send a file in a few seconds, strip a photo's location data first with our EXIF remover, or wire it into your own flow with the single-use signed URL API.

If Bitwarden Send isn't a fit because you're really chasing the old "upload, link, gone" feeling rather than a vault, our roundup of secure Firefox Send replacements walks through the wider landscape.

FAQ

Can Bitwarden Send share files for free?
No. Text Sends are free on Bitwarden, but sending an actual file requires a paid plan. If your goal is to send one document without subscribing to a password manager, a pay-as-you-go file service is a closer fit.

What is Bitwarden Send's file size limit?
File Sends are capped at roughly 500 MB on paid plans. That's larger than Bottleneck's deliberate ~100 MB safety cap, so for very large files Send (or a dedicated large-file tool) can be the better choice - Bottleneck's edge is metadata stripping and enforced single use, not raw size.

Does Bitwarden Send strip metadata from files?
No. Because Send is zero-knowledge, your file is encrypted exactly as-is and Bitwarden never opens it, so EXIF GPS data in photos and author/revision metadata in PDFs travel through untouched. Bottleneck processes the file server-side specifically so it can strip that metadata before delivery, then purges its copy.

Is Bottleneck zero-knowledge like Bitwarden Send?
No, and we won't claim it is. Your file reaches us over an encrypted connection and we process it on our servers - that's exactly what lets us sanitize metadata and enforce single use. Bitwarden Send is genuinely zero-knowledge; Bottleneck trades that for sanitized, accountable, single-use delivery. Choose the property you actually need.

Do recipients need an account to download?
With either tool, no. Bitwarden Send and Bottleneck both produce a link the recipient opens directly - no signup on their end. The difference is that Bottleneck can enforce single use server-side, so the link returns "gone" after the first download.