Files.com gives the business a governed, audited way to send and collect files with outside parties. So people stop emailing attachments and reaching for personal Dropbox or WeTransfer, and stop bending SharePoint and Google Drive into external sharing they were never built for.
Branded share links send files out. Branded inboxes collect them in. Every link can carry expiry, a password, a locked recipient, watermarking, and a clickwrap NDA. Every transfer in either direction lands in an immutable, exportable audit trail. Your people get the two-click convenience they went looking for. You get back the visibility and control shadow IT took away.
A branded share link instead of a personal Dropbox. Just as easy to use as the consumer tool, with all the controls the consumer tool never had.
Send one share link for a file, several files, or a whole folder. The recipient opens a page on your own domain and takes what they need. No Files.com account to make.
Put a password on a link. Tie each invitation to one email address and one browser, so a forwarded link no longer lets just anyone in. Limit who can open it to approved domains, or make it single-use so it stops working after one download.
Every link can have an expiration date. A link that used to sit in someone’s personal Dropbox forever now turns off on a date you set, and an admin can shut it off sooner. Old shares stop being a standing way in.
Turn on preview-only mode so the file can be read but not downloaded. Stamp the recipient’s name across every preview, so a leaked screenshot points back to them. Require a click-to-accept NDA, recorded with the time and IP address, before anyone gets in.
“The one-time file upload links, one-time file download links, and the management UI make my work easier and more efficient — they make it easier to gather and share sensitive documents in a secure way.”
“I set up all our users and set up inboxes where our customers can send us files, and everything just works. Email notifications are also a big thing for us — we need to know when we have a new file sent to us, and those just work as well.”
Real companies. Real file flows. Real results.
A branded inbox instead of "just email it to me," so files from outside the company stop arriving as email attachments.
A branded Inbox is a fixed web address anyone can upload to. No account needed, and they never see what anyone else sent. It is the direct replacement for the contractor emailing a timesheet and the vendor emailing an invoice.
The file lands in a folder IT controls, with the permissions and the retention you set. It does not land in one person’s email inbox where no one else can find it and nothing gets recorded.
Give the inbox its own email address, allow only approved sending domains to deliver to it, send automatic receipts back, and keep a log of every email that came in.
Administrators set the rules that make the approved way the only way. Set the policy once and it holds for every link and every inbox.
Require a password on every share link, lock every link to its invited recipient, cap how long any link can live, and block free or throwaway email domains from receiving files. External sharing then happens inside the lines you draw, not however each employee decides to do it.
Nine permission levels and SSO logins decide which staff are even allowed to share files outside the company. Sharing externally becomes something you grant to the people who need it, not something everyone just does.
Turn off a departing user’s account and their share links die with it. Per-folder rules limit what file types an inbox will take. The leftover access that usually outlives an employee just goes away.
What you’re really up against is a habit. People reach for email attachments, personal Dropbox, and WeTransfer not because anyone picked them as the company’s file tool, but because they were right there. A file dropped on a personal account moves with no expiration, no lock on who can open it, no limit on the recipient, and no record. Files.com isn’t a fancier version of those tools. It’s the approved way that’s just as easy to use, where every transfer carries the controls and the record you’re on the hook for.
SharePoint and Google Drive are the quieter version of the same habit, and the fix is just as simple: they’re great for working together inside the company, and they were never built for controlled sharing with outside parties. Keep collaborating there. Do the outside exchange here, where the link and the inbox are controlled and every access is recorded.
The questions a vendor security questionnaire asks about how your people share data with outside parties, answered before they’re asked.
Files.com has run as a managed service for 15+ years with zero breaches. AES-256 at rest, TLS in transit, and an A+ rating on Qualys SSL Labs.
SOC 2 Type II, PCI DSS, and CSA STAR, with a HIPAA BAA and GDPR DPA available. Used in production by banks, healthcare, and other regulated industries.
SSO and SAML against Okta, Microsoft Entra ID, Active Directory, LDAP, OneLogin, and Auth0, with role-based access, IP allowlisting, and password policies.
When you need a site-wide sharing policy changed or an inbox stood up, the difference between a managed service and a self-hosted box is who picks up.
The people who answer the phone are engineers who know the platform, not a tier-one queue reading a script. When a share or an inbox needs a policy change, you reach someone who can make it.
Get share-link policy, branded inboxes, retention rules, and the audit export stood up fast. Strategic enterprise deployments get our onboarding people embedded as forward deployed engineers.
The docs go deep, and the REST API and seven official SDKs are enough to wire sharing and intake into whatever you already run.
The same four moves show up at every company that replaced attachments and consumer tools with governed sharing.
Contracts, data exports, video, and installers go out as branded links with a password and an expiry, from a page under your domain. The recipient needs no account and nothing to install.
When staff have an approved way to send a file that is faster than the workaround, the personal cloud drives and free transfer sites stop being where company files live. Governance wins by being the easier path.
A vendor, a client, or a member of the public drops files into a branded inbox instead of emailing them. Each submission lands in a controlled folder, private to the sender, with a record of who sent what.
Links expire on a schedule, external accounts disable after inactivity, and delivered files age out under a retention rule, so a sharing platform never becomes an archive nobody meant to keep.
To clear Porsche AG's hosting rules, the channel combined federated identity, Porsche branding, and Canadian data residency for workflows across the business.
Read The Story
A thin, governed transfer layer now carries about a terabyte a month to changing external partners while existing storage stays in place.
Read The Story
Browser-based links let recipients Zillow could not train securely view or download each sensitive document according to its own retention requirements.
Read The Story
Custom domains, automatic identity provisioning, and centrally enforced policies let Alight remove its MFT team from every client exchange without weakening control.
Read The Story
What IT and security teams ask most when bringing external file sharing under control.
Files.com gives a business one approved way to share files: as easy as the consumer tools, with every transfer under IT control. It does this with branded share links carrying passwords, expiry, recipient binding, and watermarking, plus branded inboxes for collecting files. Every share, access, and upload is recorded in an immutable audit log.
Files.com gets a team off email attachments and personal Dropbox by making the approved way the easiest way, not by sending out a policy. Sending a file becomes one branded link, and collecting one becomes a fixed inbox address. Both are as fast as the consumer tool, so people stop going around IT. Company-wide rules then set the floor: Files.com can require passwords, lock each link to its recipient, cap how long a link lives, and decide which staff can share externally at all.
A Files.com share link sends files securely to anyone outside your company: you create the link and send the URL. The recipient opens a page under your own domain and downloads without an account. Before you send, you can require a password, lock the link to one invited email and one browser, set an expiration date, restrict it to approved recipient domains, make it single-use, or turn on preview-only mode with watermarking for sensitive content.
A Files.com Inbox is a permanent URL, and optionally its own email address, that outside parties upload to without an account and without seeing other submissions. Files land in a governed folder under your control with the permissions and retention you set, you can allowlist the sending domains, and an inbound email log records every arrival. It replaces the contractor or vendor emailing you an attachment.
Files.com captures every share creation, every recipient access, every download, and every inbox upload as a discrete event in an immutable audit log. Events are retained for 7+ years and export on demand or stream to your SIEM. When a breach notification or a regulator asks who saw a file, the record exists.
Files.com does the job SharePoint and Google Drive were never built for: governed sharing with outside parties. They are excellent at internal collaboration, so keep collaborating there. Stretched into outside sharing, links sprawl, external recipients are neither bound nor recorded, and admins burn effort fighting the external-sharing settings. Run external exchange on Files.com, where every outbound link and inbound upload carries the controls and the audit IT is accountable for.
Files.com scans shared files for malware on the Enterprise plan: turn it on and every inbound file is checked before anyone can open or download it and before automations run. Files.com does not read file contents for sensitive data. Content inspection stays with the DLP and endpoint tools you already run, and the API gives them a governed surface to work against. Either way, the sharing surface stays governed: who can share, who can receive, what file types an inbox accepts, and a record of every transfer.
Files.com preview-only mode means there is no downloaded file to re-share, and watermarking stamps the recipient’s identifier on every preview. Both are deterrence and forensic identification rather than DRM, so a determined screenshot still gets through. For binding control, pair them with recipient locking, single-use links, and expiry.
Share links, Inboxes, custom intake forms, and the audit log are part of the Files.com platform, not separate add-ons. The security layers on top come with the Power plan: link passwords, watermarking, clickwrap NDAs, and the custom domain that puts sharing under your own brand. Past the included counts, overages are cheap rather than a forced tier jump. Full tier and overage detail is on the pricing page.
Yes. A Files.com share link opens in the recipient’s browser with no account and no software, under your own domain, with a password and an expiry if you set them. Files up to 5 TB transfer the same way, and the audit log records who opened the link and when.
Yes. Preview-only mode shows the file in the browser and blocks download, and a watermark can carry the viewer’s identity across the page. It is a viewing control for sensitive documents, not a rights-management system: what the reader sees on screen is still theirs to read.
Branded share links, branded inboxes, the policy controls, and an immutable audit trail, in one platform your whole company will actually use. Stand up your sanctioned external-exchange path on a real workload during the 7-day free trial.
No credit card required • Free for 7 days • Live in minutes
