Should you put attachments in cold email? No. A first-touch cold email should carry no file at all, and this is the rare outbound question where the sources barely disagree: the vendors who tested it advise against it, and two sending platforms refuse to even build the feature. This article is the attachments verdict on its own terms: why a PDF in a first touch taxes your deliverability twice, what the circulating 100 KB finding actually says once you pin it to its source, and the one moment a file legitimately enters the thread. The neighboring decisions are ruled elsewhere: pictures in our verdict on images in cold email deliverability, URLs in our verdict on links in cold emails. This piece is about the paperclip.
The verdict comes from send volume, not theory. Our parent agency, Referral Program Pros, has run more than 4,000 outbound campaigns and booked over 7,000 meetings, and GTM Bud is that playbook turned into software, backed by a written guarantee: 5 percent positive replies on LinkedIn, 1.5 percent on email, or a full refund. Across those campaigns, no first touch shipped with an attachment. The deck, the one-pager, and the case study all waited for the reply, and the rest of this article is the reasoning behind that rule.
Should you send attachments in a cold email?
No. A first-touch cold email should carry no attachment at all, and every vendor that has published guidance on the question lands on the same side. Woodpecker’s article on attachments in cold email, written by its CEO, advises against them because mass spam historically arrived as a short message with a file, so filters treat the shape as suspicious. Mailshake’s help center goes further: the platform does not offer attachments at all, naming spam filtering and blocklist risk as the reason. Snov.io’s attachment guide says plainly never to send a file in the first email to a new recipient, and SmartReach tells senders to start the conversation first and share the file once the lead shows interest. The one partial dissent is Hunter, which argues an attachment is tolerable when its contents are clean, and even Hunter concedes a stranger is unlikely to open it. Send the file after the reply.
The reason the verdict is so lopsided is that an attachment fails through two separate channels at once. The machine channel: filters score the file before any human sees it. The human channel: even a delivered file asks the recipient to take a security risk for someone they have never met. The next two sections take those one at a time.
Why do spam filters treat attachments from strangers as a threat?
Because attachments are the delivery mechanism for malware, and a cold sender has no history to argue otherwise. Email filters route messages with files through heavier security scanning than plain text ever receives, and Gmail goes further than scanning: Google’s list of file types blocked in Gmail names dozens of extensions it refuses outright, including when they hide inside archives. A warmed domain with months of engagement history can absorb that extra scrutiny. A cold mailbox writing to a stranger cannot, because the filter has zero evidence your mail is wanted, and Google’s sender guidelines make the baseline explicit: send mail recipients expect, and do not hide or obscure what a message contains. A short pitch plus a file from an unknown sender is not a neutral shape. It is the specific pattern two decades of spam and phishing trained the filters on.
Then there is the weight. The most quoted number in this debate is a test described in Woodpecker’s attachments piece: messages up to 100 KB reached the inbox at every provider checked, while heavier messages landed in spam at Google Apps, Yahoo, and Outlook. Quote it with its caveats attached. No methodology was published, and the test names Google Apps, a product name Google retired years ago, so this is a dated vendor observation, not a standing threshold. The direction does have independent company: Pipedrive’s guide to email size limits, citing Email on Acid research, reports deliverability issues beginning around 110 KB of message weight and recommends staying well under it. A single PDF deck blows through both figures before the first slide. The honest summary is that nobody has published a current, controlled size threshold, and nobody needs to, because the safest first-touch attachment size is zero.
What does the vendor evidence actually say?
Almost everything quotable about attachments in cold email comes from companies that sell sending tools, so here is each source with its position and its bias in the same row.
| Source | Position on first-touch attachments | What to know before quoting it |
|---|---|---|
| Woodpecker blog | Never; the short-message-plus-file shape is what filters were trained on | CEO-authored vendor piece; its own platform also omits the feature |
| Woodpecker help center | No attachment option exists in the product, for deliverability reasons | Revealed preference, not just advice; users are told to link to a hosted file |
| Mailshake help docs | No attachments offered; spam filtering, blocklists, and unopened files cited | Same revealed preference from a second, competing vendor |
| Snov.io guide | Never in the first email to a new recipient | Vendor knowledge-base guidance, consistent but not data |
| SmartReach guide | Start the conversation first, share files after stated interest | Vendor guidance; recommends seed-list testing if you must send one |
| Mystrika deliverability piece | Attachments can significantly hurt deliverability; use alternatives | Vendor-published; no test data or mechanism released |
| Hunter analysis | Tolerable if the contents are clean; a PDF beats a .doc | The permissive outlier; leans on a quoted marketer’s opinion, not placement data |
The disagreement worth printing is Woodpecker and Mailshake versus Hunter. The first two treat the attachment itself as the risk: the shape of file-plus-pitch from an unknown sender gets scored regardless of what the file contains. Hunter treats the contents as the risk: in its guide to adding an email attachment to a cold email, an attachment without blacklisted text or images is fine, and the real constraints are provider size caps, 25 MB at Gmail and 12 MB at Zoho Mail per its breakdown, plus the choice of a PDF over a macro-capable .doc. Both can be partially right, because filters score shape and contents. But notice what Hunter concedes even while dissenting: a recipient who has never heard of you is unlikely to open the file. Which means the permissive case, even granted in full, buys you an attachment nobody opens.
The strongest evidence: the tools that refuse to build the feature
A vendor blog post costs nothing to publish. A missing feature costs sales, which is why the strongest evidence in this debate is not anyone’s advice but two product decisions. Mailshake’s help center answers “Can I add attachments to my emails?” with no, you cannot: attachments can trigger spam filters and other deliverability problems, recipients rarely open files from senders they do not know, and the suggested workaround is hosting the file on a service like Google Drive and linking to it. Woodpecker’s help center says the same thing about its own product: the option is deliberately left out because of the deliverability issues it may cause. These are companies that win deals on feature checklists, fielding a request users genuinely make, and turning it down because the feature would damage the customers who used it.
Weigh the bias honestly: declining to build attachments also spares both vendors infrastructure and abuse-handling work, so the decision is not pure altruism. But a feature refusal that two competitors independently arrive at, and publicly justify with placement risk, is a stronger signal than any ten advice posts, because it is a position someone paid for.
The trust tell: what a first-touch PDF says about you
Deliverability is only half the tax. Suppose the message lands: the recipient now sees a stranger asking them to open a file, which every security training they have ever sat through told them not to do. The attachment converts your email from a note into a security decision, and the default answer to a security decision from an unknown sender is no.
It also tells on your process. A deck attached to a first touch is a deck that existed before you knew anything about the prospect, which quietly announces that the same file went to everyone on the list. The first email’s only job is to earn a reply, and the discipline of building it around one question is covered in our guide to the cold email call to action. A message that needs a supporting document to make its case is a message that has not found its hook yet; an AI cold email writer that researches the prospect first solves that upstream, by giving the email something specific enough to say that no PDF is required. For teams running cold email for agencies across client domains, the rule is worth setting centrally: one client’s attached brochure can drag placement for mailboxes the agency spent weeks warming.
When does a file belong in the thread?
A file belongs in a cold email thread after the prospect replies, and not before. Once someone answers, the thread carries positive engagement signals, providers treat the exchange as a conversation rather than a broadcast, and the person on the other end has a reason to open what you send. That timing also fixes the trust problem: a PDF from a stranger is a security decision, while a PDF they asked for is a deliverable. The practical sequence is to write the first touch around one question, mention the material exists, and send it in your reply once they engage. SmartReach’s guidance matches this order, interest first and files second, and Emailchaser, the strictest source in our links verdict, states the same rule from the other side: after a response you can include links, attachments, or images as needed. The attachment is not banned from outbound. It is scheduled for the moment it stops being suspicious.
| Decision | First touch | After the reply |
|---|---|---|
| PDF deck or one-pager | Never attach; mention it exists and offer to send it | Send it in the same thread, compressed, as a PDF |
| Case study | Summarize the one checkable result in a sentence of text | Attach or link the full writeup on request |
| Contract or proposal | Far too early; this is a meeting outcome, not an opener | Send once terms are actually being discussed |
| Link to a hosted file | The lesser risk, but a question-only email is still better | Fine, though at this point the attachment is fine too |
| Calendar invite file | No; make the reply the call to action | Send after a time is agreed |
When the moment arrives, the format details from the permissive sources finally apply: prefer a PDF over a macro-capable Word file, per Hunter’s guide, keep it small, and stay far under provider caps, which exist to bounce oversized mail rather than to filter it. None of this spends first-touch risk, because by then the thread’s engagement history is working for you. The infrastructure that history sits on, authentication, warmup, and volume discipline, is its own project, covered in our cold email deliverability guide.
Frequently asked questions about attachments in cold email
Why do cold email tools like Mailshake and Woodpecker not support attachments?
Because the feature would hurt their customers more than its absence hurts sales. Mailshake’s help center says attachments can trigger spam filtering and blocklist placement, and that recipients are unlikely to open a file from a sender they do not know, so the platform offers no way to add one. Woodpecker’s help center leaves the option out for the same stated reason and tells users to link to a hosted file instead. When vendors who win deals on feature checklists decline to build something users ask for, the omission is stronger evidence than any blog post.
Is a PDF safer to send than a Word document in cold email?
Yes, once you have earned the right to send anything at all. Hunter’s guide to email attachments calls a PDF safer than a .doc file, and the reason is history: Word documents can carry macros, which made them a classic malware vehicle, so filters and trained recipients treat them with extra suspicion. The format question only matters after the reply, though. In a first touch the verdict does not change by extension: no attachment of any kind, PDF included.
Is there a safe attachment size for cold email?
No published threshold deserves to be treated as a rule. Woodpecker’s attachments piece describes a test in which messages up to 100 KB reached the inbox everywhere while heavier ones hit spam at Google Apps, Yahoo, and Outlook, but no methodology was released and the product naming dates the test. Pipedrive, citing Email on Acid research, reports deliverability issues beginning around 110 KB of message weight. Treat the direction as real, keep anything you send small, and remember that the safest first-touch size is zero.
Should you link to a file instead of attaching it in a cold email?
A link is the lesser risk of the two, and it is what Mailshake and Woodpecker both tell their users to do, but a first touch is better with neither. A URL still spends filter scrutiny, as our verdict on links in cold emails lays out, and a first email built around a question needs no file and no link at all. If the material genuinely matters, mention that it exists and deliver it after the prospect replies. A done-for-you outbound service enforces exactly that sequencing on every campaign.
Are attachments safe after a prospect replies?
Yes. After a response the thread carries positive engagement signals and providers treat it as a conversation rather than a broadcast, which is when files, links, and images all become routine. Keep the file small and relevant, prefer a PDF over formats that can carry macros, and send it in the same thread so the engagement history travels with it. The rules in this article protect the first unsolicited touch, not the conversation that follows it.
Earn the reply first, send the file second
The attachments verdict is the shortest one in the deliverability series: zero files in the first touch, no exceptions by format or size, and the full library available one reply later. The evidence stacks the same way at every level. The vendors who tested it advise against it, two competing platforms refused to build it, the one permissive source concedes the file goes unopened, and the circulating 100 KB figure, pinned to its source, is a dated observation that still points the same direction as everything else. A first touch is a request for thirty seconds of a stranger’s attention, and a paperclip raises the price of those seconds on both ends of the wire.
That restraint is what GTM Bud’s cold email automation tool runs by default: plain, short, question-led first touches with nothing to scan, and the deck held back until a human asks for it. It is the same playbook behind our agency’s 4,000+ campaigns and 7,000+ booked meetings, under the same written guarantee, 5 percent positive replies on LinkedIn, 1.5 percent on email, or a full refund. Keep the paperclip in your pocket until someone wants what it holds. The replies come faster without it.