Send large filesstraight from Outlook.No 25 MB limit.
Microsoft 365 caps email attachments at 25 MB. OneDrive forces recipients to log in with Microsoft. ZIP splitters are embarrassing. With SecureFiles you send files of any size right from Outlook, encrypted, without login requirements for recipients, without a new interface.
The problem is well known. The three common workarounds are all worse than the disease.
25-MB limit hard capped
Microsoft 365 blocks attachments above 25 MB. No matter how big your mailbox is, the Exchange transport service caps.
OneDrive link = login required
External recipients need a Microsoft account or fail the permission check. Customers without a Microsoft environment are locked out.
ZIP splitting is amateurish
Split a file into 20 parts, send by email, have the recipient reassemble, a workflow from 1998. And the recipient-side virus scan often blocks the first part.
WeTransfer is GDPR-risky
Caches in the US, no E2E encryption. Unsuitable for client, patient, or personnel data.
Neue E-Mail · Outlook
Senden
Anfügen
Signieren
SecureFiles
Anmax@kunde.de
BetreffVertragsentwurf + Baupläne + Video
3 Dateien · 47 GB sicher verpackt
Anhänge durch verschlüsselten Link ersetzt
vertrag-2026.pdf8 MB
baupläne-A1.dwg2,4 GB
begehung-drohne.mp444 GBOHNE LIMIT
Outlook flow · Attachment becomes link
Large attachments are quietly, securely wrapped in the background
You keep working in Outlook as usual, subject line, attachments, signature. SecureFiles detects attachments that are too large or sensitive and silently replaces them with an encrypted link including expiry and optional password.
Works in classic Outlook, new Outlook, and Outlook on the Web.
Recipients need no account, no Microsoft login, no new app.
No fixed size cap. CAD, video, database dumps, it all ships.
Three steps to send from Outlook
SecureFiles fits seamlessly into your existing Outlook flow. No second tool, no context switch.
1. Outlook add-in installed
One-time rollout central via Microsoft 365 Admin Center. End users install nothing. Classic, New, and Web Outlook supported.
2. Write the email as always
Compose the email, open the add-in, add the file, send. One click replaces the attachment with an encrypted link.
3. Add-in replaces with a link
The file is uploaded encrypted to SecureFiles infrastructure in the EU, the attachment is replaced with a signed link. Recipient clicks, download. No Microsoft account, no software.
Why SecureFiles beats any workaround
No tool switch, no training, no GDPR risk, on the contrary: more security than native Outlook attachments.
No hard size cap
Enterprise tier supports single attachments of virtually any size. CAD, video editing, database dumps, all work.
Classic + New Outlook + Web
COM add-in for Classic Outlook, Office add-in for New Outlook and Outlook on the Web. One add-in, three clients.
Central admin rollout
Roll out to all employees via Microsoft 365 Admin Center. No end-user installation, no training.
Recipient without account
The recipient needs nothing but the link in your email. No Microsoft, no Dropbox, no Tresorit.
End-to-end encrypted
Optional zero-knowledge with client-side key, more secure than a normal email attachment would be anyway.
Malware scan + audit log
Every upload is scanned before release. Audit log shows download events, IP hash, timestamp. GDPR Art. 30 ready.
Outlook workarounds in comparison
Which approach actually scales, for enterprise use.
SecureFiles add-in
Typical workarounds
Max. attachment size
No fixed size cap
25 MB (Outlook native)
Login for recipient
Not required
OneDrive: Microsoft account usually required
GDPR hosting
EU jurisdiction
OneDrive: US hoster / WeTransfer: US caching
End-to-end encryption
Optional zero-knowledge
TLS only
Virus scan during transfer
Malware scan standard
Not documented
Admin rollout
Centrally via M365 Admin Center
End-user installation required
Audit log
Included, GDPR Art. 30
OneDrive: limited / WeTransfer: hardly any
As of 2026. Comparison statements about third-party vendors are based on publicly available sources at publication time. Without warranty of continued accuracy.
FAQ: Send large files by Outlook
Why does Outlook have a 25-MB limit?
Microsoft sets the limit at the Exchange transport service to protect mail queue performance. Admins can raise it to 150 MB (classic Exchange) or 100 MB (M365), but many third-party receiving servers cap at 10–25 MB. In practice, 25 MB is the de facto limit for reliable delivery.
Can I simply raise the limit?
In M365 Exchange Online up to 150 MB send, 150 MB receive, but that helps little if the receiving mail server rejects at 10 MB. Plus, backup and journal costs grow, mailbox performance suffers, mobile sync slows. The limit is structurally sensible. The answer is not a higher number but a different architecture, link instead of attachment.
How do I install the SecureFiles add-in?
As admin, you roll out the add-in centrally via Microsoft 365 Admin Center (Integrated Apps → Add apps → upload manifest.xml). No end user installs anything. Within minutes, the add-in appears in all Outlook clients (Desktop, Web, Mobile) for the assigned users.
Does it work in the new Outlook?
Yes. The add-in is a modern Office add-in that runs in classic Outlook (COM and Web modes), in new Outlook for Windows/Mac, and in Outlook on the Web. Three clients, one add-in, consistent user flow.
Does the recipient need to install software?
No. The recipient gets an email with a link. Click, browser opens, file downloads. Optionally enter a password, otherwise nothing. No Microsoft account, no SecureFiles account, no app download.
What happens technically to the file?
The add-in uploads the file in chunks (multipart upload) to SecureFiles infrastructure in the EU. TLS in-transit, AES-256 at-rest, optional client-side pre-encryption (zero-knowledge). The Outlook attachment is replaced with a signed, time-limited link. After the configured retention (7/10/30 days), the file is deleted automatically.
Can I roll out the add-in centrally and set policies?
Yes. Via M365 Admin Center you distribute the add-in per group, department, or user. Policies (minimum file size for auto-replace, allowed file types, retention, max downloads, password requirement) are configured in the SecureFiles admin dashboard per tenant.
Is there a limit on the number of recipients?
Per transfer you can address up to 100 recipients. Each recipient gets an individual signed link, independent download count, and audit log entries. For bulk sends to more than 100 recipients, talk to us, we have bulk scenarios for newsletter-style file distribution.