← Back to Blog

Attachment limits are not universal—Gmail allows roughly 25 MB per message, Outlook 365 tenants often cap 10–20 MB, government gateways sometimes 5 MB. Compressed photo PDFs blow limits faster than text reports because each page is a JPEG plate. Teams discover limits at worst moment: 11 p.m. filing deadline, client waiting on closing docs. Workarounds split along three axes: compress smarter, split files, or change transport—not blindly upload to random file-sharing sites that violate data policy.

Knowing Your Actual Limit Stack

Limit is the minimum across sender SMTP, recipient gateway, and mobile client offline storage. Internal 25 MB allowance means nothing if client firm caps 10 MB. Maintain client attachment matrix in CRM—update when IT changes policies.

Encoded email overhead inflates attachments ~33%—a 18 MB PDF may fail a 20 MB nominal cap. Target 70% of stated limit for safety margin on unknown recipients.

Compression Strategies That Preserve Utility

First pass: Compress PDF with text-preserving settings—recompress JPEG scans moderately, downsample oversized images to 150–200 dpi for email viewing. Second pass on still-large files: grayscale conversion for monochrome documents halves photo PDF weight.

Avoid multiple recompression rounds—each pass adds artifacts. Merge before compress when sending one package—Merge PDF then single compress beats compressing each scan separately then merging bloated JPEGs.

Splitting With Manifest Discipline

Split PDF by logical boundaries—exhibits 1–5 in Part A, 6–10 in Part B—not arbitrary page counts that split exhibit pairs. Email manifest listing page ranges and filenames. Include cover PDF as Part 0 index one page—recipients forward complete sets.

For symmetric limits, split into near-equal megabyte parts using size-aware tools rather than guessing page counts.

When Links Beat Attachments—Policy Permitting

Secure portals, SharePoint links with auth, and client VDRs transport large PDFs without SMTP limits. Policy may forbid public Dropbox links—use approved enterprise file services with access logs. Expiring links need calendar reminders before client access lapses.

Never replace regulated attachments with consumer links lacking BAAs for PHI. Local Compress PDF and split often satisfy HIPAA email when portals unavailable.

Print-Ready vs Email Derivatives

Press-ready PDFs with embedded fonts and CMYK exceed email limits by design. Maintain archive master; generate email derivative with Compress PDF and RGB downsample. Filename suffix _EMAIL versus _PRINT prevents accidental press submission of email copies.

Protect PDF large splits when content sensitive—three 8 MB parts leak same data as one 24 MB file if unencrypted.

Mobile Recipient Considerations

Clients on phones may decline downloading 20 MB "just to see page 3." Extract Pages relevant sections for mobile-first sends; provide full archive via portal. Watermark PDF preview snippets when only approval needed before full pack release.

Cellular data caps cause silent failures—recipients abandon downloads; confirm receipt explicitly.

Automation and Helpdesk Patterns

Helpdesk tickets spike after month-end when automated reports exceed limits. Pre-schedule compression in report generator or split rules in reporting server. If reports cannot shrink, switch delivery to SFTP with PDF Metadata Analyzer cleanup on automated exports.

Document standard workaround playbooks so tier-one support splits and resends without escalating to engineering nightly.

Measuring Limit Workaround Success

Track bounce rates, average compress passes per document type, client complaints about partial sets, and policy exceptions for cloud uploads. Goal: zero unauthorized file-sharing escalations caused by attachment limits—teams should have approved local compress/split paths that work at 11 p.m. without shadow IT.

Legal Hold and Large Attachment Exceptions

Legal hold notices may require preserving exact email with attachment—splitting for delivery still needs archived original merged PDF in hold repository. Merge PDF split parts back to verified whole before hold certification.

Some regulators accept DVD/USB for oversized productions—Protect PDF USB-delivered splits with password in cover letter, not sticker on USB.

SMTP Relay and Gateway Size Mismatches

Internal relay may allow 50 MB while external recipient caps 10 MB—compress for external path even when internal path tolerates large files. Split PDF at external limit minus encoding overhead.

Journalists and FOIA recipients on legacy government email need aggressive Compress PDF or physical media—confirm recipient IT before assuming portal or link acceptable.

MSP and IT Ticket Attachment Limits

MSP ticketing systems cap attachments below email limits—compress PDF support logs before ticket upload. Split PDF multi-part log export when ticket system counts each attachment separately toward quota.

Healthcare exchange PDFs between hospitals may cap 5 MB while sender hospital allows 25 MB—always compress for receiving minimum.

Archived PST exports re-send old giant PDFs—compress historical attachment before forward to avoid surprising new recipient with 2018 scan size.

Board packet part numbering in subject line Part3of5 prevents directors assuming Part 5 missing when only size limited send.

Some counsel prefer one PDF even if large—ask before splitting settlement PDF client worked hours to review as single scroll.

Version every exported PDF with date suffix before sharing so colleagues never confuse draft and approved copies.

Spot-check outputs on mobile viewers before bulk send—layout and font issues appear on phones before desktop review catches them.

Close browser tabs after local processing on shared workstations to clear document data from session memory promptly.

Record tool version and processing date in cover memos when auditors or clients request evidence of how PDFs were prepared.

Hash or checksum final PDFs when matter or project policy requires integrity verification across long retention periods.

Name split parts with explicit sequence labels so recipients know whether additional attachments are still forthcoming.

Test one compressed copy on the slowest device your audience uses before distributing large campaign or client packets.

Keep uncompressed masters in archive storage even when daily workflow relies on compressed derivatives for email and portals.

Document batch completion time and operator in a one-line log entry so repeat jobs benefit from realistic scheduling estimates.

Confirm page order at batch boundaries before declaring merge complete.

Align filename conventions with your records team before cross-department PDF handoffs.

Validate print preview when color or font complaints are historically common for this document type.

Store processing notes beside the PDF in your DMS for faster onboarding when teammates cover absences.

Re-run metadata review when reusing an old PDF template for a new client or matter cycle.

Teams that standardize local PDF preparation reduce rework cycles because every reviewer evaluates the same filename, version, and compression profile instead of reconciling ad hoc exports from mixed tools.

When stakeholders report display issues, compare the affected page in two viewers and on one mobile device before reprocessing the entire file—localized fixes save time on hundred-page packets.

Open QuickerPDF Tool →