Email with file sharing has been a hack for twenty years. You attach a file, your mail server bounces it because the recipient's mail server caps attachments at 25MB, you upload to WeTransfer or Dropbox, paste a link, and try again. The hack persists because mail servers inherited attachment limits from a 1990s era when those limits made sense; today they just create friction.
TrekMail bundles the workaround into the mail composition flow itself. Attach a 200MB design file, hit send. The platform uploads the file to your Drive automatically, replaces the attachment with a share link, and sends a clean mail. The recipient sees a polished message with a link instead of a giant attachment. No login, no separate WeTransfer trip, no Dropbox tab.
This guide walks why attachment caps exist, where WeTransfer and Dropbox slot in historically, and how TrekMail's auto-convert pattern replaces them. For the broader business-email frame see custom domain email.
Why Mailbox Servers Cap Attachments at 25MB
Mail server attachment caps trace back to the cell-tower era when downloading 25MB over EDGE cost real money. The caps stuck around because spam filters use attachment size as one input. Most major receivers cap at 25MB and aggressively filter anything close to the limit.
The historical caps don't reflect 2026 reality. Most files people want to send (design assets, video drafts, presentation decks) easily exceed 25MB. The caps make email with file sharing painful exactly when sharing files is the point. The workarounds (WeTransfer, Dropbox links, Google Drive sharing) exist because the underlying mail protocol can't carry the files directly. The cap problem is structural to email, not specific to any one vendor.
Where WeTransfer and Dropbox Slot In Historically
WeTransfer slotted into email with file sharing as the one-off large file tool. Upload, get a link, paste into mail, recipient downloads within 7 days. Pro tiers cover up to 200GB at $144/year. Most operators use it for client design deliveries and large one-off transfers.
Dropbox slotted in as the persistent shared workspace. Upload files once, share with team, files stay accessible indefinitely. Business plans run $1,200-1,800/year for 5-person teams. The product solves a different problem than WeTransfer — ongoing team collaboration rather than one-off transfers. Most B2B teams running email with file sharing workflows use both tools, paying for both, and switching between them based on whether the file is one-off or persistent.
How TrekMail's 18MB Auto-Convert Works
The auto-convert pattern watches outbound mail for attachments above 18MB. When detected, the platform uploads to Drive, generates a share link with default expiry, replaces the attachment with the link, and proceeds with normal send. The conversion takes a few seconds during compose-to-send.
The 18MB threshold sits comfortably below the 20-25MB cap most receivers enforce. Files between 18MB and 25MB technically work as attachments but trigger anti-spam scrutiny that lowers inbox placement. The auto-convert at 18MB sidesteps the scrutiny by converting before it can happen. The sender experiences a normal "attach, send" flow; the recipient gets a clean mail with a download link.
Revocation and Expiry Policy
Share links from TrekMail email with file sharing carry expiry dates and revocation options. Default expiry is 7 days; the sender can extend to 30, 90, or no expiry. Revocation lets the sender disable the link at any point if a file is sent to the wrong recipient.
The policy controls live in the Drive interface after the mail is sent. The sender can list active share links, see who has accessed each, and revoke individually. The revocation takes effect immediately; subsequent click attempts return a "link no longer active" page. The combination of expiry plus revocation gives the sender substantially more control over file distribution than the email-attachment model ever did.
Team Folder Use Case
The team folder use case in email with file sharing covers persistent collaboration that Dropbox traditionally filled. A team creates a "Q3 Campaign" folder, adds files, gives team members access. Files stay accessible without per-file share links. New additions show up for everyone in the folder.
Access to team folders aligns with the mail account, so the same identity that sends mail authenticates Drive. The marketing team's mailbox aliases (marketing@yourcompany.com routing to team members) align with the marketing folder's ACL. The alignment reduces the cross-system identity management that stitched-together email+Dropbox setups create across two separate access control systems.
Four Share Patterns the Bundle Covers
Four common share patterns appear in email with file sharing workflows, and the TrekMail bundle covers all four in one identity system. The numbered list below names each pattern with the use case it serves at typical small-to-medium team scale across B2B operations today.
- One-off large file transfer. Auto-convert attaches files over 18MB to Drive automatically; recipient gets a share link with expiry.
- Persistent client folder. Shared folder with project files; client accesses via folder link with optional password protection.
- Internal team workspace. Shared folder with broad team access; updates from one person visible to all team members.
- Sensitive document delivery. Share link with short expiry (7-30 days) and revocation option for after-delivery cleanup.
Each pattern was a separate tool in the stitched-together approach (WeTransfer for one-offs, Dropbox/Box for client and team folders, password-protected uploads for sensitive delivery). TrekMail's bundle covers all four in one identity system and one storage pool. The simplification is real, not marketing — the team logs in once and uses the same tool across all four patterns.
Cost vs Stitched WeTransfer+Dropbox
The cost comparison makes the savings concrete. A 10-person team running Workspace + WeTransfer + Dropbox typically pays $720 + $144 + $1,800 = $2,664/year. On TrekMail Pro the same workload is $96/year. The savings buys back the productivity-suite gap several times over for teams using Notion or Figma.
The stitched approach also carries an operational overhead that the dollar comparison undercounts. Three logins, three admin consoles, three policy frameworks. Team-onboarding involves provisioning accounts at each. Team-offboarding involves revoking access at each. The bundled approach collapses all three into one workflow, which saves time at every onboarding and offboarding event. See business email pricing for the broader pricing frame.
Next Steps
The honest answer for B2B teams currently running stitched email + WeTransfer + Dropbox setups is to consolidate email with file sharing into TrekMail Pro at $96/year. The auto-convert pattern handles the one-off large files. Shared folders handle the persistent team collaboration. The bundled email with file sharing architecture eliminates the three-vendor overhead while keeping all four share patterns available.
Test TrekMail Nano free at trekmail.net/pricing — no card required. The Nano tier covers solo operators with 5GB pooled mail+Drive storage; Starter at $4/month expands to 15GB and adds managed outbound SMTP. The email with file sharing pattern works across all tiers; the storage cap is what scales with the tier choice.
One concrete example: an architecture firm in Boston that previously shuttled 60-80MB design renderings through WeTransfer for every client review. After switching to TrekMail Pro, the same workflow runs through the auto-convert pattern: attach the rendering to the client email, hit send, TrekMail handles the upload-and-link conversion in the background. The firm dropped WeTransfer entirely and recovered the $144/year subscription plus the friction of context-switching between tools.
For teams currently doing the email with file sharing dance manually (upload to Dropbox, paste link, send), the auto-convert pattern eliminates the context switch. The 10-15 seconds saved per large-file send compounds across the 5-20 large files a typical small team sends per week. The cumulative time savings across a year is real and recurring at the team workflow level. See business email for small business for the small-team sizing frame and email hosting for small business for the broader email-host comparison.
One more example: a 4-person legal practice that previously sent contracts via Dropbox shared links with manual expiry tracking. Switching meant contracts flow through the standard mail compose with automatic share links that expire after 30 days. The practice dropped Dropbox Standard ($720/year) and the manual expiry tracking that consumed an hour or two per week of paralegal time.
For teams in regulated industries, the revocation feature matters operationally. When a client engagement ends, the firm can revoke every share link from that client in one workflow rather than manually expiring each link individually. The discipline scales with the practice without requiring proportional admin time across a growing client portfolio.
One setup recommendation for teams adopting email with file sharing bundles: set the default link expiry to 30 days at the account level rather than accepting the 7-day default. Most business teams batch-process inbound mail weekly or receive large files during travel periods. A 7-day expiry generates "link expired" complaints regularly; 30 days covers the realistic download window for most recipients without creating indefinite open access. Adjust down to 7 days only for genuinely time-sensitive deliveries where the shorter window is intentional.
