# Gmail Attachment Size Limit: 25MB Threshold and Large File Sharing

The Gmail attachment size limit is a strict 25 MB cap on the total size of all attached files per outgoing email, which restricts binary attachments to roughly 18 MB to 20 MB due to MIME and Base64 encoding overhead. While Google automatically routes oversized attachments to Google Drive links, this introduces permission friction and quota consumption. Engineering teams and agentic workflows bypass email transfer ceilings by maintaining persistent, indexed workspaces accessible via MCP.

Source: https://fast.io/resources/gmail-attachment-size-limit/
Author: [Tom Langridge](https://fast.io/authors/tom-langridge/)
Last reviewed: 2026-09-28

## What Are the Documented Gmail Attachment and Message Size Limits?

The Gmail attachment size limit is a strict 25 MB cap on the total size of all attached files per outgoing email, which effectively restricts binary attachments to roughly 18 MB to 20 MB due to MIME and Base64 encoding overhead. For personal Gmail accounts, the limit is 25 MB.

When preparing an email in Gmail on desktop or mobile, the mail composer calculates the cumulative byte size of every attached document, spreadsheet, video clip, and inline image. If the aggregate payload exceeds Gmail's 25 MB attachment limit, the email client refuses to attach the files directly. Instead, Gmail displays a prompt alerting the sender that files larger than 25 MB must be shared through Google Drive.

Understanding how Google measures this threshold is critical for avoiding failed deliveries and unexpected bounces. The Gmail 25 MB attachment size limit does not apply individually to each file. If you attach two 13 MB PDF reports to a single Gmail email, their combined 26 MB weight crosses the attachment size limit, triggering the Google Drive link prompt. Similarly, attaching ten 2.5 MB images reaches the Gmail attachment size limit, even though every individual file appears modest in isolation.

### Single Email Attachment Caps and Google Workspace Tiers

The 25 MB outgoing attachment limit remains standard across both free consumer Gmail accounts and paid Google Workspace enterprise tiers. Whether an organization subscribes to Business Starter, Business Standard, or Enterprise editions, Google enforces the exact same 25 MB sending ceiling on direct message attachments.

This design reflects the underlying mechanics of email transfer protocols rather than arbitrary account tiering. Email systems rely on Simple Mail Transfer Protocol relays that process messages through distributed networks. Allowing massive multi-gigabyte files directly inside email envelopes would overwhelm intermediate mail transfer agents, degrade server responsiveness, and exhaust user mailboxes.

The table below outlines documented sending and receiving thresholds across standard Gmail, Google Workspace editions, and dedicated cloud workspaces:

| Interface or Service | Outgoing Attachment Limit | Incoming Message Limit | Over-the-Limit Handling | Verified Date |
|---|---|---|---|---|
| Gmail (Personal Accounts) | 25 MB total attachments | 50 MB total message | Prompts or converts to Google Drive link | September 2026 |
| Google Workspace (Standard) | 25 MB total attachments | 50 MB total message | Prompts or converts to Google Drive link | September 2026 |
| Google Workspace (Enterprise Plus) | 25 MB total attachments | 70 MB total message | Prompts or converts to Google Drive link | September 2026 |
| Microsoft Outlook and Exchange | 20 MB to 25 MB default | 25 MB (up to 150 MB configured) | Prompts for OneDrive or returns bounce code | September 2026 |
| Apple iCloud Mail | 20 MB default | 20 MB total message | Prompts to send via Mail Drop link | September 2026 |
| Fast.io Workspace via MCP | Plan storage capacity (1 TB to 50 TB) | Unlimited transfer volume | Persistent storage with hybrid semantic indexing | September 2026 |

When evaluating these limits, remember that the total size encompasses more than just the file on your local drive. Email message headers, MIME formatting boundaries, and the text body itself consume space within the envelope.

### The Difference Between Sending Limits and Receiving Envelopes

A frequent source of confusion among professional teams is the asymmetric relationship between Gmail sending limits and receiving limits. While you cannot dispatch an outgoing attachment larger than 25 MB from Gmail, your Gmail account can receive incoming messages up to 50 MB in size.

In Google Workspace, receiving limits allow incoming messages up to 50 MB (Enterprise Standard) or 70 MB (Enterprise Plus)*. This expanded receiving ceiling allows external senders on dedicated high-volume mail systems or custom mail transfer agents to transmit larger files directly into your inbox.

However, this incoming allowance offers little comfort when you must reply to the sender with updated revisions. If an external client emails you a 35 MB project document from their corporate server, your Gmail receiving limits allow the incoming file message. But if you attempt to reply and attach your edited files back to the email thread, Gmail enforces the 25 MB attachment size limit. You are forced to abandon direct email attachments and switch to an external sharing method.

## Why Does Message Encoding Inflate an 18MB File Past the Gmail Attachment Limit?

Many professionals encounter a confusing scenario: attempting to attach an 18 MB or 20 MB PDF to an email, only for Gmail to declare that the file exceeds the 25 MB limit. The sender verifies the file size in local storage, sees 18.2 MB, and wonders why the Gmail attachment limit rejects the email.

The failure occurs because computer operating systems measure raw binary files on disk, whereas email systems evaluate the message after data encoding. The Simple Mail Transfer Protocol, originally specified in RFC 821, was engineered strictly for 7-bit ASCII plain text. Mail transfer agents and intermediate relays were never designed to interpret raw 8-bit binary streams such as compiled code, compressed archives, digital photos, or video recordings.

To transport binary assets across text-only protocols without corruption, the Multipurpose Internet Mail Extensions standard mandates that binary files be converted into text characters using Base64 encoding.

### How SMTP 7-Bit ASCII Architecture Forces Base64 Conversion

Base64 encoding functions by taking 3 bytes of binary data (24 bits) and splitting them into 4 separate 6-bit units. Each 6-bit unit maps directly to one of 64 printable ASCII characters: uppercase letters A through Z, lowercase letters a through z, numbers 0 through 9, the plus sign, and the forward slash.

Because 3 input bytes always produce 4 output characters, Base64 conversion introduces an immediate mathematical expansion ratio. A raw binary file expands by one third of its original byte count the moment it enters the encoding stream.

Beyond the raw character transformation, MIME standards require email clients to insert line breaks at regular intervals. RFC 2045 specifies that encoded text lines must not exceed 76 characters, requiring the insertion of carriage return and line feed control sequences. When you combine the Base64 conversion, periodic line breaks, MIME boundary delimiters, and mandatory transport headers, the overall data expansion increases further.

Google Workspace message encoding adds about a 37% increase to the raw file size, inflating attachments during transit. This means an ordinary file experiences substantial byte inflation before it departs your outbox:

| Raw File Size on Disk | Expected MIME Payload After 37% Overhead | Outcome on Gmail 25MB Sending Ceiling |
|---|---|---|
| 10 MB | ~13.7 MB | Transmits successfully |
| 15 MB | ~20.6 MB | Transmits successfully |
| 18 MB | ~24.7 MB | Borderline; succeeds only with minimal email body |
| 20 MB | ~27.4 MB | Rejection; triggers Google Drive fallback |
| 22 MB | ~30.1 MB | Rejection; triggers Google Drive fallback |
| 25 MB | ~34.3 MB | Rejection; triggers Google Drive fallback |

Because mail servers inspect the complete stream during transmission, an 18.5 MB file combined with email text pushes the overall message payload beyond the 25 MB Gmail attachment limit.

### Line Breaks, Boundary Delimiters, and Header Overhead

Every email containing attachments is structured as a multipart MIME message. The message contains specific headers declaring content boundaries, such as Content-Type, Content-Disposition, and Content-Transfer-Encoding.

Each attachment requires boundary strings that separate the email body from the file data. For an email carrying multiple attachments, the client writes separate header blocks and boundary tokens for every individual asset.

If you attach three 6 MB files to a single Gmail email, their total raw weight approaches the attachment limit. Once each file is encoded and wrapped in MIME headers, the total message size surpasses Gmail's 25 MB attachment limit. Senders who want reliable delivery without triggering Google Drive redirects must treat 18 MB as the practical operational limit for raw binary attachments.

## Why Native Workarounds Like Google Drive and File Compression Fall Short

When a user attempts to attach a file exceeding the 25 MB threshold, Gmail offers an automated fallback: inserting a Google Drive link. While this mechanism appears straightforward, professional teams quickly encounter operational friction around permissions, quota depletion, and client presentation.

Similarly, traditional manual workarounds such as file compression and multi-part email splitting introduce unexpected failure modes that delay critical project deliveries.

### Google Drive Handoffs: Permission Requests and Storage Depletion

When you upload an oversized attachment through Gmail's built-in Google Drive prompt, Gmail uploads the asset to your personal or organizational Drive storage and generates a sharing link in the email body.

The most common operational issue is permission management. By default, files created in Google Drive inherit private or domain-restricted access controls. When an external client or agency partner clicks the link in your email, they are frequently greeted by an access barrier stating that permission is required. The recipient must submit an access request and wait for the sender to manually approve it. If the sender is traveling, attending meetings, or working in another time zone, delivery stalls for hours.

To avoid access requests, users often set link permissions to public access. While this allows the recipient to view the file immediately, it removes security controls. Anyone who forwards or accesses the link can view or download the file, creating compliance vulnerabilities for proprietary project assets and sensitive legal records.

Furthermore, every file uploaded through this mechanism consumes your personal Google storage quota. Free accounts share a 15 GB allocation across Gmail, Google Drive, and Google Photos. Teams sharing high-resolution design packages, software builds, or video deliverables rapidly exhaust their capacity, leading to bounced inbound emails and account disruptions across the entire Google Workspace domain.

### ZIP Compression Ineffectiveness on Modern Pre-Compressed Media

Another conventional workaround is compressing oversized files into ZIP archives before attaching them to Gmail. While compression can reduce the byte count of plain text files, source code repositories, and raw database exports, it offers negligible benefit for modern media assets.

Most contemporary production formats already incorporate sophisticated internal compression algorithms:

* **Video and Audio**: MP4, MOV, WebM, MP3, and AAC files use lossy compression designed to strip redundant data. Compressing a 30 MB MP4 file into a ZIP archive fails to shrink the payload below Gmail's 25 MB attachment size limit.
* **Modern Images**: JPEG, WebP, and optimized PNG graphics are already compressed. Placing them inside an archive yields almost no reduction.
* **Production Documents**: Complex PDF files, modern Office documents (.docx, .xlsx, .pptx), and packaged design files are already zipped XML containers. Secondary compression fails to alter their footprint.

Beyond the lack of compression savings, ZIP archives add friction for the recipient. The client must download the archive, extract the files using local desktop utilities, and navigate unpackaged folder trees. On mobile devices, opening compressed archives often requires third-party extraction tools, creating a poor user experience.

### Fragmentation Risks of Multi-Part Email Splitting

Some senders attempt to bypass the Gmail 25 MB attachment limit by dividing files across separate emails. For example, a team attempting to deliver an 80 MB package might send multiple Gmail emails with 20 MB of files each, hitting the attachment size limit on every message.

This practice introduces severe coordination hazards:

* **Thread Fragmentation**: Corporate email filters often deliver multi-part messages out of order. Recipients receive Part 3 before Part 1, creating confusion about missing deliverables.
* **Spam Filter Triggers**: Rapidly sending multiple sequential emails containing heavy attachments to the same recipient triggers automated rate limits and spam heuristics, causing messages to land in junk folders or be quarantined by security gateways.
* **Version Confusion**: When revisions occur, updating individual assets across fragmented email threads makes it nearly impossible to determine which attachments represent the latest approved versions.

## Security Restrictions, Prohibited Formats, and Attachment Delivery Errors

Exceeding the 25 MB size threshold is not the only reason Gmail rejects file transfers. Google operates an automated security scanning pipeline that inspects every attachment before allowing it into the mail stream. Understanding these security filters prevents sudden transfer rejections and delivery failures.

### Blocked Executable Extensions and Archive Inspection Rules

To protect users against malware, ransomware, and malicious scripts, Gmail strictly prohibits attaching executable files. If you attempt to attach a file with a restricted extension, Gmail terminates the upload and displays an error message stating that the file contains blocked code.

Gmail automatically blocks files with the following extensions, even if the file is intended for legitimate business use:

* Executable applications: `.exe`, `.msi`, `.bat`, `.cmd`, `.scr`, `.vbs`, `.com`, `.pif`
* System and shell scripts: `.sh`, `.bash`, `.ps1`, `.vbe`, `.jse`, `.reg`
* Programmatic scripts: `.js`, `.jar`, `.cpl`, `.ins`, `.isp`

Crucially, placing an executable file inside a compressed archive does not bypass Gmail's security filters. Google's inspection engine unpacks `.zip`, `.rar`, `.tar`, `.tgz`, and `.7z` archives in memory to inspect internal payloads. If an archive contains even a single blocked script, the entire container is rejected.

Furthermore, Gmail automatically blocks password-protected archives. Because encrypted archives prevent Google's automated scanners from verifying the internal files, Gmail treats password-protected ZIP and RAR containers as potential threats and blocks them from transmission.

### Storage Exhaustion Failures Across Sender and Recipient Mailboxes

Attachment failures frequently originate from mailbox capacity limits rather than individual file constraints. In Google Workspace and consumer Gmail accounts, storage pools across Gmail, Google Drive, and Google Photos.

When a sender's Google account reaches capacity:
* Outgoing drafts fail to save or upload new attachments.
* The web interface displays warnings that storage is full.
* Inbound emails bounce back to external senders with storage quota errors.

The recipient mailbox presents an identical vulnerability. If your recipient has filled their available storage allowance, your email will bounce even if your Gmail attachment size is well under 25 MB. The recipient mail server issues an SMTP 552 error code (mailbox allocation exceeded), leaving the sender uncertain whether the problem was caused by file size or account exhaustion.

### Network CDN Blocks and the Upload In Progress Error

In enterprise office environments, attachments occasionally fail to upload due to network infrastructure policies. Google hosts and delivers Gmail attachments through a dedicated content distribution network operating under the domain `mail-attachment.googleusercontent.com`.

If an enterprise firewall, content filter, or secure web proxy restricts traffic to this domain, users encounter persistent upload failures. The browser file picker opens, but the progress bar stalls indefinitely before displaying an error indicating that attachments are unavailable. Resolving this issue requires network administrators to add Google's attachment host to corporate network allowlists.

Another frequent desktop and mobile error occurs when senders click the send button while an asset is still uploading. If you attach a large file on a mobile device and immediately tap send, Gmail displays an alert warning that files are still being added. If the mobile app loses connectivity or the browser tab closes before the upload completes, the message remains stranded in your outbox, resulting in delayed delivery.

## Decoupling Large File Delivery from Email Using Intelligent Workspaces and MCP

Modern engineering organizations, creative agencies, and agentic teams avoid the limitations of email attachments by decoupling communication from file persistence. Instead of forcing heavy binary payloads through 40-year-old mail protocols, teams use dedicated cloud workspaces designed for collaborative asset storage, intelligent search, and autonomous agent access.

Fast.io provides intelligent workspaces where teams and AI agents organize, version, and share files, leaving email to handle concise notifications and contextual summaries.

### Replacing Heavy Attachments with Branded Workspace Delivery

In a decoupled architecture, email carries lightweight messages containing secure links, while heavy project assets reside in org-owned Fast.io workspaces:

* **Eliminating Size Boundaries**: Teams can upload large assets, including raw video footage, layered design containers, architectural CAD models, and extensive document libraries, using chunked uploads without email size restrictions.
* **Branded Client Shares**: Workspaces support purpose-built Send, Receive, and Exchange shares. Send shares deliver finished assets with custom expiration dates and download controls. Receive shares let clients upload assets directly into designated folders without email attachments. Exchange shares create two-way collaborative workspaces for ongoing projects.
* **Access Without Account Friction**: External clients and agency partners can access branded shares directly through a browser link without creating an account or consuming a licensed organization seat.
* **Per-File Version History**: When revisions occur, Fast.io retains complete version history for every file. Clients and collaborators always access the latest approved file while retaining the ability to review or restore earlier iterations.
* **Append-Only Audit Log**: Every file upload, download, view, and share creation is recorded in an immutable, append-only audit log, ensuring complete visibility into client deliveries.
* **Integrated E-Signature**: Teams can send agreements, release forms, and engagement letters directly from a workspace for signature using [Fast.io E-Signature](/product/e-signature/). The platform supports sequential or parallel signers, optional one-time passcodes, tamper-evident audit certificates, and automatically files the executed document back into the workspace.

### Built-In Workspace Intelligence and Hybrid Semantic Retrieval

Fast.io workspaces provide native intelligence that transforms static storage into an interactive knowledge engine. When Intelligence Mode is enabled on a workspace, incoming files are automatically indexed for hybrid search, combining exact keyword matching with semantic retrieval.

Instead of downloading multi-gigabyte document packets from email threads or manually browsing folder directories, team members and AI assistants can query workspace contents using natural language. Fast.io searches across text files, PDFs, spreadsheets, and presentations, returning precise answers with verified document citations.

For structured business records, [Metadata Views](/product/document-data-extraction/) convert unstructured documents into queryable tables. Users define fields in natural language, and AI extracts typed data, such as contract counterparties, policy numbers, expiration dates, and invoice line items, without manual templates or OCR configuration.

### Autonomous Agent Integration via Model Context Protocol

As organizations deploy AI agents built on Claude, Cursor, Codex, OpenClaw, or custom orchestration frameworks, email attachments become an acute operational bottleneck. Agents cannot reliably parse email threads cluttered with fragmented attachments, nor can they ingest massive binary files without exhausting model context windows.

Fast.io bridges the gap between autonomous agents and persistent storage through the Model Context Protocol (MCP). Fast.io exposes a consolidated MCP toolset over Streamable HTTP at `https://mcp.fast.io/mcp/tools`.

Using Fast.io MCP tools, AI agents can:
* Inspect workspace directories and read documents directly.
* Perform hybrid semantic search across thousands of indexed files.
* Retrieve specific data points and draft summary briefings with exact document citations.
* Save generated reports, analysis spreadsheets, and creative deliverables into shared team folders.
* Hand off completed workspaces to human teammates using ownership transfer, allowing agents to build workspaces and grant administrative control to clients.

Existing files stored in other repositories can be imported directly. Fast.io supports cloud import from Google Drive, Dropbox, OneDrive, and Box, as well as direct URL imports. For ongoing alignment, Cloud Sync provides scheduled or on-demand one-way and two-way synchronization for Google Drive, Dropbox, Box, and OneDrive.

Every organization starts with a 14-day free trial, which requires a credit card. Paid subscriptions are structured across Starter, Business, and Enterprise plans. Credits meter AI work. Storage and team seats come with each subscription plan. Explore workspace architecture at [Fast.io Workspaces](/product/workspaces/) and review agent storage patterns at [Fast.io Storage for Agents](/storage-for-agents/). For pricing and tier details, visit the [Fast.io Pricing page](/pricing/). Developer onboarding instructions are available at [Fast.io LLMs](/llms.txt).

## Frequently asked questions

### What is the maximum attachment size in Gmail?

The maximum attachment size in Gmail is 25 MB per outgoing email. For personal Gmail accounts, the limit is 25 MB. This ceiling applies to the cumulative total of all attached files and inline media in a single message, rather than a per-file allowance. If you attach two 13 MB files to an email, the total reaches 26 MB, exceeding the Gmail attachment limit.

### Why can't I send a 22MB file attachment exceeding the Gmail size limit?

You cannot send a 22MB file directly as an email attachment because transport protocols require converting binary files into text characters via Base64 encoding. Google Workspace message encoding adds about a 37% increase to the raw file size, inflating attachments during transit. As a result, a 22MB binary file expands past 30MB during message encoding, exceeding Gmail's 25MB attachment size limit.

### How do I send files larger than 25MB via Gmail?

To send files larger than 25MB through Gmail, you can link to an external cloud storage location instead of attaching raw binary data. While Gmail automatically prompts you to insert a Google Drive link, teams frequently encounter access permission delays. A more reliable approach is storing project assets in a dedicated workspace like Fast.io and inserting a branded share link with customizable access controls into your email.

### What is the difference between Gmail outgoing and incoming attachment limits?

Gmail enforces an outgoing attachment limit of 25 MB, while standard incoming mailboxes can receive message payloads reaching 50 MB (or 70 MB for Google Workspace Enterprise Plus accounts). This allows Gmail users to receive larger documents sent from specialized enterprise servers or other high-capacity mail transfer agents, even though they cannot send attachments of that size from Gmail itself.

### Does the 25MB limit apply to each file or the whole email?

The 25MB limit applies to the entire email envelope, including all attached files, inline images, headers, and the message body combined. Attaching five 5MB files yields a 25MB payload before message encoding, which exceeds Gmail's total email attachment limit once expanded. To ensure delivery without triggering Google Drive fallbacks, keep the aggregate raw size of all attachments under 18 MB.

### What file types does Gmail block from being attached?

Gmail strictly prohibits executable files and scripts to prevent malware transmission. Blocked extensions include .exe, .bat, .cmd, .scr, .vbs, .js, and .msi. Gmail also blocks compressed archives (such as .zip, .rar, .tar, or .7z) that contain executable files or password-protected archives containing suspicious code.

### How do automated AI agents and developer pipelines share large files without hitting Gmail attachment limits?

Automated AI agents and developer pipelines avoid email attachment limits by storing generated reports, datasets, and build artifacts in an intelligent Fast.io workspace. The agent uploads files directly via the consolidated Fast.io MCP server or API, then inserts a lightweight retrieval link into email notifications. Collaborators can view the files or query them using hybrid semantic search.

## Sources

- [Google: Gmail Help](https://support.google.com/mail/answer/6584?hl=en): Gmail enforces a 25MB attachment size limit on total files per email for personal accounts, automatically substituting Google Drive links for larger attachments.
- [Google Workspace Admin Help: Gmail sending and receiving limits](https://knowledge.workspace.google.com/admin/gmail/gmail-receiving-limits-in-google-workspace): Google Workspace receiving limits allow incoming messages up to 50MB or 70MB, noting message encoding adds about a 37% increase to the raw file size.

## About Fast.io

Fast.io provides shared workspaces where people and AI agents work on the same files, with built-in semantic search and citation-backed chat over what they hold. Agents reach it through a remote MCP server, a REST API at https://api.fast.io/current/, and a command line client published on npm as @vividengine/fastio-cli. MCP setup is at https://mcp.fast.io/docs: Claude and most MCP clients connect to https://mcp.fast.io/mcp/tools, ChatGPT to https://mcp.fast.io/mcp/operations, and coding agents to https://mcp.fast.io/mcp/code.