🚦 Upload Limit Checker

Every few days, someone sends a "why didn't you get my email?" message, and the answer is almost always the same: the attachment was too big and bounced silently. The sender has no idea. The recipient has no idea. The file just disappeared into a rejection queue somewhere between SMTP servers, and no one got a sensible error.

File size limits are one of those invisible infrastructure constraints that affect almost every person who uses the internet, yet almost no one can recite them from memory. What's the WhatsApp limit? Twenty-five MB? A hundred? Is that for videos or documents? Does Discord treat free accounts differently from Nitro subscribers? Most people learn these limits the hard way, at the worst possible moment — right before a deadline, or after a client swears they "never received" the proposal you sent.

Why Platforms Have Different Limits (And Why They're All Over the Place)

There's no global standard for upload limits. Each platform sets its own based on storage costs, abuse prevention, and the engineering choices made years ago that are now baked into legacy systems. Gmail's 25 MB attachment cap, for instance, dates back to an era when 25 MB felt generous. Google didn't raise it when storage got cheaper partly because they'd rather route you through Google Drive, where your file becomes a revenue-generating storage customer.

WhatsApp allows 100 MB for most media, but that number changes depending on whether you're on Android or iOS, and whether you're in a group or individual chat. Web forms are arguably the worst offenders for unpredictability: a server running default PHP configuration typically caps uploads at 8 MB, but the form might show no visible limit at all. You only discover it when your carefully prepared resume PDF quietly fails to submit.

Discord's free tier sits at just 10 MB — surprisingly low for a platform built around sharing game clips. Slack, meanwhile, allows up to 1 GB per file. Telegram's 2 GB limit makes it one of the most file-friendly platforms in everyday use, though most people never send anything close to that size and don't know to use it when email fails.

The Hidden Cost of Guessing Wrong

When you send an email with a 27 MB attachment through Gmail, a few things might happen: Gmail blocks it outright and shows you an error, your recipient's mail server rejects it and you get a bounce-back (sometimes hours later), or — most frustratingly — some mail servers accept it into a queue and silently drop it after a delay. The bounce notification, if it comes, often contains just enough technical jargon to be confusing and not enough plain language to be useful.

The same problem plays out differently on web forms. A large PDF upload fails after a slow progress bar reaches 99%, giving no indication of whether the issue was the file size, the network, or a server timeout. The user refreshes, tries again, maybe submits a smaller file — and wonders for days whether the original went through.

For professionals sending design files, medical records, legal documents, or video content, these limits aren't occasional minor inconveniences. They're workflow blockers that consume real time. Knowing in advance which platforms will reject your file lets you pick the right channel before you waste effort.

Understanding the Numbers: MB, GB, and Why Binary Units Matter

A quick but important note: when platforms say "25 MB," they typically mean 25 megabytes in the decimal sense (25,000,000 bytes), while operating systems and storage tools often display file sizes in mebibytes (MiB), where 1 MiB = 1,048,576 bytes. A 24.9 MB file might display as slightly more or slightly less depending on which convention your system uses. In practice this difference is small — around 5% — but it can matter when you're right at a platform boundary. If your file reads as 24.8 MB on your Mac, it should be fine for Gmail's 25 MB cap. If it reads as 24.8 MiB, the actual byte count is closer to 26 MB, and it could be rejected.

This calculator works in standard binary units (1 KB = 1024 bytes, 1 MB = 1024 KB) to match how most file systems report sizes, so the comparisons stay honest.

What to Actually Do When Your File Is Too Large

The right fix depends on the file type and the destination platform.

For videos, HandBrake (free, cross-platform) can reduce file sizes dramatically without visible quality loss. A 200 MB MP4 can often be trimmed to under 50 MB using H.265 encoding at a sensible quality preset. WhatsApp auto-compresses videos on iOS and Android, but it does this after you select the file, not before — and it may drop quality more than you'd like for anything important.

For images, lossless PNG files can often be converted to JPEG at 85% quality with no perceptible difference and a 70% size reduction. Tools like Squoosh (browser-based, no upload required) or ImageOptim on Mac handle this well.

For PDFs, the story is trickier because PDF size is usually driven by embedded images. Adobe Acrobat's "Reduce File Size" option works, but so does exporting a Google Slides or Word document as PDF with compression settings enabled from the start. Printing to PDF from a browser often produces smaller files than exporting directly from design tools.

For everything else, cloud sharing is the cleanest workaround. Google Drive, Dropbox, and WeTransfer all let you share files of several gigabytes via link. Gmail now auto-suggests converting large attachments to Drive links, which is genuinely useful — the recipient gets a link that works, and you don't have to manually upload anything first.

Platform-Specific Tricks Worth Knowing

Outlook and iCloud Mail both have smart auto-conversion built into their native apps (not webmail). Outlook will offer to upload your attachment to OneDrive and send a sharing link instead when you try to attach something over 20 MB. Apple Mail does the same with iCloud Drive for recipients who also use Apple Mail. These flows only work if you're using the dedicated app, not the browser version.

Telegram deserves a mention for anyone regularly sharing large files. Its 2 GB limit combined with fast CDN delivery makes it surprisingly useful as a file transfer tool between people who both have it installed. For one-sided transfers (you → someone who doesn't use Telegram), WeTransfer's free tier allows 2 GB with no account required, which covers most real-world use cases.

Discord Nitro is worth the mention specifically for communities where file sharing is frequent. The jump from 10 MB to 500 MB is significant, and for game dev or design communities sharing assets regularly, it pays for itself in reduced friction.

Checking Before You Send

The underlying habit that saves the most headaches is simply checking before committing to a delivery method. Right-click the file, get info, note the size in MB, then match it against the platform you're using. Or use the tool above: enter the size (or drop the file to auto-detect it), and get an instant read on every major platform at once. No account needed, no data sent anywhere — the calculation runs entirely in the browser.

It sounds almost too simple, but building a ten-second pre-send check into your workflow eliminates an entire category of "did you get it?" follow-ups. That's not nothing.