The Email That Bounced: A Lesson in PDF File Size Limits

The Day a Client Slipped Through My Fingers

I remember exactly where I was when it happened. Sitting at my kitchen table with a cold cup of coffee and a proposal I'd spent three evenings building from scratch. The brief was perfect for me — a mid-sized furniture brand in Pune wanted a full brand identity refresh, and my portfolio had exactly the kind of work they were looking for. I'd put together 27 pages of strategy, moodboards, sample mockups, and a detailed pricing breakdown. It looked sharp. It felt like the pitch that would finally let me quit chasing small gigs.

I hit send. The little whoosh sound played. I closed my laptop and went to bed feeling, for the first time in months, genuinely optimistic.

The next morning I had a bounced email notification and a silence from the client that stretched into three days.

What Actually Happened

The bounce message was technical gibberish at first glance — something about a "552 5.3.4 Message size exceeds fixed maximum message size" error. I Googled it. My 38MB PDF attachment had hit Gmail's outgoing attachment cap of 25MB, and the client's corporate email server had an even stricter limit set at 20MB. The proposal never landed in their inbox. They didn't ghost me. They never received it.

By the time I figured this out and resent the file (badly compressed, still 26MB, bounced again), they'd already moved on to another freelancer who'd sent a cleaner proposal through a shareable link. I got a polite reply four days later: "Sorry, we've already gone in another direction."

That moment taught me more about working as a freelancer than any online course I'd ever paid for.

Why PDFs Get So Heavy in the First Place

Before I fixed my workflow, I needed to understand the problem. My proposal was bloated for entirely avoidable reasons:

• Unoptimized images: I'd exported mockups from Photoshop at 300 DPI — print resolution — and embedded them directly. A screen only needs 72–96 DPI to look crisp. The extra pixels were dead weight.
• Embedded fonts: I'd used three custom typefaces and embedded the full font files instead of subsets. Subsetting includes only the characters actually used in the document, which can cut font data by 80%.
• Layered design exports: My presentation software kept transparency layers and blending modes in a way that PDFs don't handle efficiently. Flattening them before export would have helped enormously.
• No compression on export: I'd literally clicked "Export as PDF" with default settings and called it done.

None of these were exotic technical problems. They were all things I could fix in under five minutes once I knew they existed.

Learning the Tools That Actually Work

After losing that pitch, I spent a weekend testing every compression method I could find. Some were useless; a few became permanent parts of my process.

The first thing I tried was Adobe Acrobat's built-in "Reduce File Size" option. It brought my 38MB proposal down to about 22MB — still too large for that client's server, and the image quality took a noticeable hit on the mockup pages. Useful in a pinch, but not the answer.

Next I tried Smallpdf and ILovePDF, the web tools everyone recommends. They worked, getting me down to 14MB, but I was nervous uploading confidential client proposals to a third-party server. Client confidentiality matters, and most of these tools' free tiers store your files temporarily. For personal documents, fine. For a business proposal with pricing and strategy? I wasn't comfortable with it.

The tool that actually changed my workflow was Ghostscript — a free, open-source command-line tool that runs entirely on your own machine. It sounds intimidating if you've never used a terminal, but the command you actually need is just one line:

gs -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -dPDFSETTINGS=/ebook -dNOPAUSE -dQUIET -dBATCH -sOutputFile=output.pdf input.pdf

The magic is in the -dPDFSETTINGS flag. You have four meaningful options:

1. /screen — Maximum compression, lowest quality. Good for drafts you're sending internally.
2. /ebook — The sweet spot for most proposals. Images downsampled to 150 DPI, readable on any screen, file size drops dramatically.
3. /printer — Targets 300 DPI print quality, moderate compression.
4. /prepress — Minimal compression, for files going to a professional print shop.

Running my 38MB proposal through Ghostscript with the /ebook setting produced a 7.2MB file. The mockup images were indistinguishable from the original on a laptop screen. I couldn't believe I'd been doing this wrong for years.

The Workflow I Use Now

I've rebuilt my proposal-sending process around a few simple habits that have eliminated bounce problems entirely:

Design at screen resolution from the start. If the deliverable is a PDF that someone will read on their computer, I export mockup images at 150 DPI maximum. This alone cuts file size before I've even touched a compression tool.

Compress before sending, always. I run every PDF through Ghostscript's /ebook preset as the final step, even if the file seems small enough. It takes 10 seconds and I've never had a file come out looking worse on a screen.

Know your client's email infrastructure before sending large files. If a client is at a large corporation, assume their IT department has tight attachment limits — often 10MB or less. When in doubt, I ask upfront: "What's the best way to send you a detailed proposal? Some clients prefer a link." This shows professionalism, not weakness.

Keep a WeTransfer or Google Drive folder as backup. For anything over 15MB, I send both the email with the compressed PDF and a "here's a higher-res version if you want it" Drive link in the same message. Belt and suspenders.

What I Wish Someone Had Told Me Earlier

The furniture brand wasn't the only deal I lost to this problem — it was just the first one I identified clearly. Looking back, I can think of at least two earlier "no replies" that might have had the same cause. Proposals that I thought people were simply ignoring, sitting in undeliverable limbo somewhere in a mail server.

There's something deeply frustrating about doing the creative work well and then losing a client to a file size limit. It feels arbitrary, mechanical, beneath the actual substance of what you're offering. But it's also completely fixable, which means there's no excuse for letting it happen twice.

The tools exist. Ghostscript is free. The command is one line. Adobe Acrobat has a built-in reducer. Even macOS Preview can compress PDFs through its Quartz filter (go to File → Export as PDF → Quartz Filter → Reduce File Size). You have options.

A Postscript on That Client

About eight months after the bounced email, I got a message from that same furniture brand. The freelancer they'd hired hadn't worked out. They'd found my portfolio again through a referral and asked if I was available.

I sent them a 6.4MB proposal. It landed in their inbox within seconds. We worked together for seven months.

I still think about how differently things might have gone if I'd just known to compress the file the first time. One small technical habit, and the whole timeline shifts. That's the thing about the boring, unglamorous parts of running a freelance business — they matter just as much as the quality of your work, sometimes more. The best proposal in the world doesn't close a deal if it never arrives.