Every email provider has a ceiling, and it's low: Gmail rejects attachments over 25 MB, Outlook.com around 20 MB, and many corporate mail servers sit at 10 MB. One decent PDF portfolio, a short video, a CAD file or a photo shoot blows straight past it. The providers' own workaround is to upload your file to their cloud and email a link — which works, but now your file lives on a server, under someone's terms, waiting on an upload before the recipient can start. Beamaroo takes the direct route: both of you open a browser tab, pair with a one-time code, and the file streams device to device — encrypted, any size, with a verified receipt when it lands.
Why email has a size limit at all
Email was never built for big files. Attachments are encoded into the message itself (which inflates them by about a third), copied across relay servers, and stored in both mailboxes forever. Providers cap sizes to keep all that survivable — and the caps haven't meaningfully moved in a decade: Gmail's 25 MB limit dates from an era when phones shot 2-megapixel photos.
That's also why 'just attach it' fails quietly: the message bounces after you hit send, sometimes minutes later, from the recipient's server rather than yours. The file wasn't too big for your outbox — it was too big for theirs.
The workarounds, honestly compared
Cloud links (Google Drive, OneDrive, Dropbox) are email's official answer: upload, share a link, hope the permissions are right. They work well when the recipient needs the file later or several people need it — but you wait through a full upload, the file sits on the provider's servers under their terms, and 'anyone with the link' is a real setting with real consequences.
Upload-and-link transfer services (WeTransfer and similar) are the same shape with less friction — and the same trade: your file is stored on their infrastructure, usually with size caps and expiry timers on the free tier.
A direct beam changes the shape: no upload phase, no stored copy, no link that can be forwarded. The transfer starts immediately, the file only ever exists on your device and theirs, and the pairing code means it can't reach the wrong person. The one honest requirement: both devices online at the same time — if the recipient is asleep, a cloud link waits and a beam doesn't.
For the everyday case — one file, one person, both reachable now — the beam is the shortest path: open beamaroo.com on both devices, pair, done. The receipt tells you it arrived intact, which email never did even for small attachments.
Delivery receipt built in — you'll know it landed
Every file is hash-checked on the receiving device over an encrypted WebRTC connection (DTLS), and the confirmation beams back to you: “Delivered — verified on their device.” Like a boomerang, it comes back. Most tools say “sent” the moment a file leaves your hands; Beamaroo waits until it's proven to arrive.
A verified pairing code, not a shareable link
A share link works for anyone who gets it. A Beamaroo verified pairing code cryptographically checks you're connected to the right device — and the channel burns after one wrong guess, so a leaked or mistyped code can't quietly reach the wrong person.
Questions
How do I send a file that's too big for Gmail?
Gmail caps attachments at 25 MB, so anything bigger needs to travel outside the message. Fastest route: open beamaroo.com on your device and the recipient's, share the one-time pairing code, and the file transfers directly — any size, encrypted, no Google Drive upload step and no stored copy.
What's the maximum file size I can email?
Gmail allows 25 MB per message, Outlook.com about 20 MB, iCloud Mail 20 MB, and corporate servers are often stricter (10 MB is common). Attachments also inflate ~33% in transit, so a '25 MB limit' fits roughly an 18 MB file. Past that, email wants you on a cloud link — or you can beam the file directly.
Is there a way to send big files by email without Google Drive or OneDrive?
Not through email itself — the limits are hard server rules. But you can skip the cloud entirely: a browser-to-browser transfer sends the file straight to the other device, so nothing is uploaded anywhere. Beamaroo does this free, with end-to-end encryption and no account.
Why did my email bounce hours after I sent it?
The recipient's mail server rejected the attachment — their limit applies too, and it can be lower than yours. That's the trap with 'it sent fine on my end'. A direct transfer avoids the guessing: the delivery receipt confirms the file is verifiably on their device.
Is beaming a file more private than a cloud link?
Yes, structurally. A cloud link means a copy of your file on a provider's servers, subject to their terms, retention and link-sharing settings. A beamed file is end-to-end encrypted between exactly two devices, verified by a pairing code — there is no third copy and no link to forward.
What if the other person isn't online right now?
Then a cloud link is genuinely the better tool — that's the one thing the upload model does that a live beam can't. Beamaroo needs both devices connected at the same time; in exchange, nothing is ever uploaded or stored. Pick by situation: recipient offline → cloud link; recipient reachable → beam.