You click “Attach,” browse to the right file, and click “Open.” For a second, it looks like nothing happened. No error popup. No attachment showing up in the message. You try again. Same result. Then you start doubting your memory, the file system, and finally your sanity.
If you need this as one file, our free compress pdf tool runs entirely in your browser — nothing is uploaded.
This “silent failure” is one of the most common (and most frustrating) problems with PDF attachments in Outlook, Gmail, and Thunderbird. The good news is that it is almost always fixable, and the causes are surprisingly consistent across all three clients. Below are the five most common reasons your email client will not attach a PDF, along with step-by-step troubleshooting for each.
---
PDF is the most heavily “co-owned” file format on your computer. Adobe Acrobat, Preview, Microsoft Edge, Google Chrome, and countless other programs register themselves as PDF handlers. When one of them has the file open, it holds an exclusive lock on the file (or a share lock that prevents modification). Most email clients either refuse to copy a locked file or silently fail when their background attachment service tries to read it.
Outlook is the worst offender here because it reads the file into memory in a separate process. If that process hits a lock, it simply gives up and the attachment never appears.
SearchIndexer.exe, MsMpEng.exe (Windows Defender), or OneDrive.exe that is still processing the file. Restart the machine if in doubt.report_copy.pdf), and attach that. The new file has no locks on it.qlmanage). Press Esc in Finder or run killall QuickLook in Terminal.---
Email clients do not use the Windows shell to resolve paths; they use their own internal file-handling layer. That layer often assumes the path is pure ASCII. If your PDF lives at:
C:\Users\Jürgen\Documents\Résumé_2025.pdfC:\Users\Jane\Downloads\report (1).pdfC:\My Documents\folder with space\file with "quotes".pdf…Outlook and Thunderbird will frequently drop the attachment request without warning. Gmail (web) is more forgiving because the browser handles the path, but if the *file name itself* contains characters that the browser’s file picker sanitizes oddly, you can still hit a dead end.
Ctrl+X) and paste it into your Desktop or C:\Temp.report.pdf, invoice_042.pdf.> Rule of thumb: if the file name or any folder in the path contains accented letters, CJK characters, emojis, parentheses, or more than 64 characters, assume it is the culprit until proven otherwise.
---
Windows has a legacy limit of 260 characters for the full path (including the file name). Many PDF workflows — especially those that auto-generate files into deeply nested project folders — silently blow past this. The file appears in Explorer, but when the email client’s internal resolver builds the string, it hits the limit and the attach command fails with no user-facing error.
Thunderbird has a separate, less-documented limit: if the file name alone is longer than 128 characters, the attachment dialog in older builds silently refuses to add it.
regedit, set LocalPolicy → Computer Configuration → Administrative Templates → System → Filesystems → *Enable Win32 long paths* to Enabled. A reboot is required.C:\Users\You\Desktop\inv.pdf will always work.---
Every email provider has a hard cap on attachment size:
| Client / Provider | Limit |
|---|---|
| Gmail (web & app) | 25 MB per message, 50 MB total per send |
| Outlook (web / M365) | 25 MB (admin can lower it) |
| Outlook (desktop) | Controlled by your IT policy; often 25 MB |
| Thunderbird | No built-in limit, but your provider enforces one |
Here is the subtle part: when you drag a 30 MB PDF into a Gmail web message, you get a clear “message too large” error. But when you use Outlook desktop or Thunderbird, and your provider’s limit is enforced server-side, the client sometimes *does not* show an error at all. The compose window just sits there, you hit Send, and the message “bounces” back minutes later with a server error — or, worse, the attach step itself silently drops the file because the client pre-checks the size and refuses to add it to the attachment list without telling you.
---
If you use OneDrive, Box, or iCloud Drive on Windows or macOS, files are stored as cloud placeholders. They show up in Explorer with a small cloud icon. Until you open them at least once, the local disk only has a tiny stub file (a few kilobytes) and a reference to the cloud copy.
When you drag that stub into Outlook, the client reads the stub, gets a file that is 0 bytes or a few KB of metadata, and the attachment either shows up as a corrupted 0-byte file or does not show up at all. Gmail’s web uploader sometimes manages to fetch the real file via the cloud SDK, but desktop Outlook and Thunderbird almost never do.
---
If you are in a meeting and need to send the PDF *now*, run this in order:
doc.pdf.In 90 % of cases, steps 1–4 solve the problem.
---
Q1: Why does Outlook attach the file as a 0-byte or corrupted PDF?
This is almost always the OneDrive/iCloud placeholder issue (cause #5). The email client read the stub file instead of the real content. Force a full download, then re-attach. If the file was a legitimate 0-byte file (the download failed on the source side), re-download it from the sender.
Q2: I renamed the file and moved it to the Desktop, but it still will not attach in Gmail web. What else is it?
In the browser, the issue is usually one of two things: (a) the file is still too large and the 25 MB cap is silently truncating the upload, or (b) your browser has a stale file-picker handle. Open a new tab, go straight to the compose window, and use the paperclip icon (do not drag-and-drop from Explorer, which can carry over a bad handle). Also check that no browser extension (ad-blockers, “file manager” helpers) is intercepting the file input.
Q3: My Thunderbird used to attach PDFs fine. Now it silently drops them. What changed?
Two likely causes. First, a Windows update may have changed how the file system exposes locks (cause #1), so a program that was not locking the file before now is. Second, if you recently installed a PDF viewer or enabled OneDrive on-demand, you may now be hitting cause #1 or #5. The fastest diagnostic: create a brand-new 1 KB text file on your Desktop, rename it to test.pdf, and try attaching that. If test.pdf works but your real PDF does not, the problem is specific to that file’s path / lock / size, not Thunderbird itself.
Q4: Is there a way to make Outlook warn me *before* I hit Send when an attachment is about to fail?
Not natively — Outlook desktop does not have a pre-send attachment validator. The closest you can get: (a) enable “Send test message” in your provider’s admin console (M365) so you catch size issues early, (b) use a VBA macro that checks each attachment’s size and file name pattern before Send, or (c) switch to Gmail web for large or oddly-named PDFs, where the 25 MB cap gives you an immediate, visible error. For a team, the most robust fix is to standardize on a naming convention (short, ASCII-only, under 100 characters total path) and a 20 MB internal size guideline, so the edge cases stop occurring.
---
*If you found this guide useful, share it with a colleague who is still “just trying again” in Outlook. And if your PDF is over 25 MB, skip the fight: a Drive link is the intended solution, not a workaround.*