Gmail caps attachments at 25MB. Outlook.com and most Microsoft 365 mailboxes cap them around 20MB. Those limits have barely moved in years, while the files people actually need to send have not stood still — a few minutes of 4K phone video, a folder of RAW photos from a mirrorless camera, or a design file with embedded assets will blow past either ceiling without much effort. Hit the limit and the message either bounces back undelivered or, on some providers, gets quietly converted to a cloud-drive link you didn’t ask for.
What actually blows past the limit
It doesn’t take an unusually large file to hit a 20-25MB ceiling. A single RAW photo from a modern mirrorless camera can run 30-45MB on its own — one photo, already over. A minute of 4K phone video is commonly in the 300-400MB range. A layered Photoshop or Illustrator file with embedded assets can pass a few hundred megabytes before you’ve added much to it. None of these are edge cases; a handful of vacation photos or a short screen recording is often enough on its own to bounce.
What the usual workarounds cost you
The standard fixes all trade the size limit for a different problem. A cloud-drive share link means the recipient may need an account with that provider, may hit a “request access” wall if your sharing settings aren’t quite right, and the link can quietly expire before they get to it. Splitting a file into a multi-part ZIP archive means every single part has to download successfully — one corrupted or missing piece and the whole archive won’t open, which is a bad way to discover a problem after the fact. Third-party upload sites solve the size problem but introduce a new one: your file now sits on a server run by a company you’ve never dealt with, under a retention policy you probably haven’t read.
Sending the file directly instead
FileTransferX skips the inbox entirely. Rather than uploading a file somewhere for someone else to download later, it pairs your device with the recipient’s and moves the file straight across that connection.
- Open Send Files and select the file, or files, you need to move.
- Share the QR code or short code with the receiving device.
- Watch a live progress bar with transfer speed and estimated time remaining.
- The file lands directly on the other device once the transfer completes.
There’s no attachment to format correctly, no compression step, and no inbox on either end that needs to have room for it.
Why a large file doesn’t choke the browser tab
Attaching a large file to an email loads the whole thing into memory before it can send, which is part of why browsers and mail clients bog down or crash on big attachments. FileTransferX reads and sends files in small chunks instead, so a multi-gigabyte video is handled the same way as a small document — the browser tab is never asked to hold the entire file in memory at once.
So how large is “large”
There’s no hard file-size ceiling built into FileTransferX. What you can comfortably send instead depends on two practical things: how much memory the sending device has free, and how stable the network connection stays for the whole transfer. A single 4K video export, a folder of several gigabytes of RAW photos, or a full project backup all move the same way — select the files, pair, and send — whether that adds up to 200MB or 20GB.
What you don’t lose along the way
Because the file itself travels rather than getting re-encoded, resized, or recompressed, what arrives is byte-identical to what you sent: same resolution, same bitrate, same file format. That’s worth calling out specifically because it’s not how every large-file workaround behaves — some cloud photo and video services automatically compress uploads above a certain size or resolution unless you dig into a setting to turn that off. Nothing here gets processed on a server in between, so there’s no compression setting to find in the first place.
If a network gets in the way
FileTransferX always tries to connect the two devices directly first. Some networks — strict corporate firewalls, certain mobile carriers — block that kind of direct connection outright, so it automatically falls back to a secure relay instead. The relay only ever forwards encrypted data it can’t read; more detail on exactly what it can and can’t see is on the security page. A relayed transfer can run a little slower than a direct one, but a large file will still complete over it, it just isn’t the fastest path available on that particular network.
What happens if something interrupts a large transfer
Because nothing is ever stored on a server in between, there’s no background copy of your file sitting somewhere waiting to be resumed. If either tab closes, loses its connection, or the device falls asleep partway through, the transfer stops there and has to be started again from scratch — which matters more the bigger the file is. For a large transfer, it’s worth keeping both devices awake and the browser tab in the foreground until the progress bar reaches the end, especially on a phone, where switching to another app can pause or interrupt an in-progress tab.
No workaround needed
None of this requires an account, a paid plan, or software to install — open the site on both devices, pair, and send. It works the same way between two phones, two computers, or a phone and a computer, so the same large-file problem that email can’t handle has one answer regardless of which devices are on either end.