How to Send Large Files via Gmail in 2026 (Past the 25 MB Limit)

TL;DR: Gmail caps attachments at 25 MB sent / 50 MB received as of May 2026. To send anything larger via Gmail, you have three working options: (1) Google Drive auto-attachment for files up to 15 GB free / 2 TB on Google One — recipient needs Google permission, (2) a secure file-sharing service like Uploadex / WeTransfer / Smash where you paste a download link into the email body, or (3) split + zip the file into multiple sub-25 MB parts. For most professional use cases, option 2 with a password-protected link is the cleanest. This guide walks through all three, with the gotchas I've hit shipping files weekly through Gmail since 2018.

I get this question every couple of weeks. Usually it's a designer trying to email a 200 MB Photoshop file to a client, an accountant trying to send a 60 MB scanned tax bundle, or a colleague who just learned Gmail won't take their 80 MB video. Gmail bounces it with the cryptic message "Attachment exceeds the allowable limit" — and that's that.

Here's the honest version: Gmail has not raised its 25 MB attachment cap in over a decade. It's not going up. Google's bet is that you'll switch to Google Drive for anything bigger. That's fine when the recipient is also on Google, painful when they're not, and worth avoiding when the file is sensitive enough to keep out of the Drive permission tangle.

Let me walk through every actual method that works in May 2026 — what the workflow looks like, what breaks, and which one to pick for which kind of file.

What Are Gmail's Actual Attachment Limits in 2026?

There are two separate limits, and people regularly confuse them:

• Sending limit: 25 MB per email. Combined size of all attachments. If you try to attach more, Gmail offers to upload via Google Drive instead (more on that in a second).
• Receiving limit: 50 MB per email. You can receive larger inbound attachments from other mail servers than you can send. This trips people up — they receive a 40 MB attachment fine, then try to forward it and Gmail refuses.

Both limits are firm. There's no "increase attachment size in Gmail settings" toggle, no paid Workspace tier that raises them, no header trick. Files compressed in a .zip count toward the same 25 MB cap, post-compression.

Method 1: Use Google Drive Auto-Attachment (Built Into Gmail)

When you attach a file larger than 25 MB, Gmail offers to upload it to Google Drive and send a link instead. This is the path of least resistance if both you and the recipient are inside the Google ecosystem.

How to send a large file with Google Drive in Gmail

1. Compose a new Gmail message as normal.
2. Click the paperclip (attach) icon and pick a file over 25 MB.
3. Gmail prompts: "This file exceeds 25 MB. Use Google Drive instead?" Click Send using Google Drive.
4. The file uploads to your Drive, and Gmail inserts a link into the email body.
5. Before sending, check the link permissions — Gmail asks whether recipients should have view / edit access, or whether they need to request access.

File size limit: up to your Google Drive storage cap — 15 GB free, 100 GB on Google One Basic ($1.99/mo), 2 TB on Google One Premium ($9.99/mo), 5 TB on the AI Premium tier.

Where Google Drive in Gmail wins

• Zero extra tools or accounts for the recipient if they're already on Google
• Versioning — if you re-upload an updated file with the same name, the Drive link stays the same
• Works from mobile Gmail too

Where it doesn't

• Permission friction. If the recipient is outside your Workspace domain, you have to explicitly grant them access. "Anyone with the link" works but it removes the access control that the security-conscious actually want.
• No password protection on share links. Google Drive's share links can't be password-locked on free or personal Google One plans.
• No download cap, no link expiry on personal plans. Anyone who has the link, has it forever. Workspace Business+ adds expiration but consumer Gmail doesn't.
• Looks unprofessional in some industries. A Google Drive request-access loop is a productivity tax for clients who don't use Drive daily.

For meeting notes and casual files, Drive auto-attachment is fine. For client deliverables, regulated documents, or anything you wouldn't want forwarded — keep reading.

Method 2: Send a Secure Share Link (My Recommended Workflow)

This is what I do for 95% of "I need to email a big file" situations. Upload the file to a dedicated file-sharing service, get a share link with the security controls you want, and paste the link into the Gmail body. The email itself stays well under 25 MB because all you're sending is text plus a URL.

Step-by-step: send a large file via Gmail using a share link

1. Upload the file to a secure file-sharing service. I use Uploadex (disclosure: I write for them, and the free tier supports up to 2 GB per file). WeTransfer, Smash, and SwissTransfer all work too.
2. Set the security controls before generating the link: password (mandatory for anything sensitive), link expiration (24 hours to 30 days), download cap (1 if sending to a single recipient).
3. Copy the share link.
4. Open Gmail, compose your message normally, paste the link into the body. Mention what the file is and (separately, by SMS or a different email) the password.
5. Send.

Where this method wins

• File size: 2 GB free on Uploadex, unlimited on Smash, 5 GB on SwissTransfer — all far beyond Gmail's 25 MB and beyond what's practical to email even via Google Drive auto-attachment.
• Password-protected links — the single biggest security upgrade you can add. Gmail's transport encryption protects the message; the password protects the file even if the email is later forwarded or breached.
• Link expiration + download caps — kill the link after the legitimate download instead of leaving it open forever.
• Per-link download analytics — you can see whether the recipient actually downloaded, and from where.
• No Google account / Workspace permission tangle for the recipient.

Where it doesn't

• One extra step (the upload) vs Drive auto-attachment's one-click flow.
• The recipient has to click out of Gmail to download, which some non-technical recipients find clunky.

For a longer walkthrough on the security controls themselves, see my guide on how to send large files securely and the comparison of WeTransfer alternatives.

Method 3: Split Into Parts (When You Have No Other Option)

If the recipient can only accept email attachments — corporate firewall blocking external file-share domains, regulated environment, weird compliance setup — you can split the file into sub-25 MB chunks and email them across multiple messages.

I dislike this method. It's slow, error-prone, and ugly. But it works and sometimes it's the only option.

How to split on Mac

split -b 24m bigfile.zip bigfile.zip.part-

This creates bigfile.zip.part-aa, bigfile.zip.part-ab, etc., each 24 MB. The recipient runs:

cat bigfile.zip.part-* > bigfile.zip

to reassemble.

How to split on Windows

7-Zip has a built-in option: right-click → 7-Zip → Add to archive → set "Split to volumes, bytes" to 24m. It produces bigfile.zip.001, bigfile.zip.002, etc. The recipient opens the .001 part in 7-Zip and it reassembles automatically.

What goes wrong

• Antivirus and spam filters. Multiple sequential emails with archive parts look very much like malware delivery — Gmail's outbound filter or the recipient's inbound filter often delays or quarantines them.
• Out-of-order delivery. If part 3 arrives before part 2, some recipients panic.
• Reassembly fails silently. If even one part gets corrupted in transit, the reassembled file is garbage and you don't know until the recipient tries to open it.

Use this only when the other two methods are genuinely blocked.

Quick Recommendation: Which Method for Which File?

A short cheat sheet you can keep open while writing the email:

What About the "Increase Gmail Attachment Limit" Tricks?

Every couple of weeks someone posts a "secret trick to increase Gmail attachment limit to 50 MB" or similar. None of them work in May 2026:

• No setting in Gmail or Google Workspace raises the 25 MB outbound cap.
• No browser extension can change a server-side limit.
• No paid plan raises it. Google Workspace Enterprise has the same 25 MB attachment cap as a free gmail.com account.
• Rename the file to a different extension? It doesn't matter — the file is rejected by size before Gmail looks at content.
• Compress with maximum compression? Helpful but rarely enough. A 100 MB video compressed via ZIP is still ~95 MB; ZIP doesn't reduce already-compressed media.

If you find a "trick" that promises otherwise, it's either out of date or wrong.

FAQ: Sending Large Files via Gmail

What is the maximum file size you can send through Gmail?

25 MB outbound, 50 MB inbound. This is the size of the entire email including all attachments combined. Files larger than 25 MB get rejected at the compose step; Gmail offers to upload them to Google Drive instead.

Can you send 100 MB files in Gmail?

Not as a direct attachment. For a 100 MB file, you have two practical options: (1) use Gmail's built-in Google Drive auto-attachment, which sends a Drive link instead of an attachment, or (2) upload the file to a secure file-sharing service like Uploadex or WeTransfer and paste the share link into your Gmail message body. Both keep the email itself under 25 MB.

How do I send a 1 GB file through Gmail?

Use a file-sharing service. Upload the 1 GB file to Uploadex (free tier supports up to 2 GB per file), Smash (no size limit on free), or SwissTransfer (50 GB free per transfer), then paste the share link into your Gmail message. Google Drive auto-attachment also works if you have enough Drive storage. Do not attempt to email the file directly — Gmail will reject anything over 25 MB.

How do I send large videos via Gmail for free?

Upload the video to a free file-sharing service (Uploadex's free tier handles up to 2 GB per file; Smash has no file-size cap on free), generate a share link, paste it into your Gmail message body. For videos under 200 MB and a Google-using recipient, Google Drive auto-attachment in Gmail also works.

Why does Gmail say "attachment exceeds the allowable limit"?

Your file is over Gmail's 25 MB outbound attachment cap. Compress the file (ZIP / 7z) if it's not already a compressed format like MP4 or JPEG, or switch to one of the methods in this guide — Google Drive auto-attachment for files under your Drive storage limit, or a secure share link for files where you want password protection and expiration.

Can I password-protect a file before emailing it through Gmail?

Yes — ZIP the file with a strong AES-256 password before attaching (or before uploading to a file-share). See my step-by-step guide on password-protecting a ZIP file. Then send the password to the recipient through a different channel — SMS, phone call, or separate email — not in the same message as the file or link.

Is it safe to send confidential documents through Gmail?

Gmail itself uses TLS encryption in transit, which protects messages between Gmail servers and the recipient's server if the recipient's server also supports TLS. That's most of the major providers in 2026, but not all. For confidential documents, the safer pattern is to use Method 2 from this guide: upload to a service with AES-256 at rest and password-protected share links, then send only the link (not the file) via Gmail. That way even if the email is later breached or forwarded, the file requires the password to access.

Summing Up!

Gmail's 25 MB cap isn't going up — every working solution for sending big files through Gmail in 2026 routes the file outside the message body and puts a link in it instead. Pick the method that matches your file size, recipient, and sensitivity:

• Casual files, Google-using recipient: Google Drive auto-attachment (Method 1)
• Anything bigger or sensitive: secure file-share + share link in the email body (Method 2) — this is what I default to
• Locked-down recipient firewalls: split into parts and email sequentially (Method 3)

For Method 2 — which is the one most professional workflows want — pair the share link with a password sent through a different channel, a short expiration, and a download cap of one. That combination keeps the file out of the "email forwarded to wrong person" failure mode that simple attachments fall into all the time.

If you want a fuller walkthrough on the security side (threat models, when to escalate to end-to-end encryption, what AES-256 actually protects against), my guide on sending large files securely and the AES-256 encryption explainer go deeper.

Sources: 
- Google: file sizes in Gmail 
- WeTransfer pricing 
- Smash file transfer