The Proposal That Took Three Hours to Send

I was sitting in my home office, staring at Gmail's attachment progress bar. It had been stuck at 87% for what felt like forever. The proposal I was trying to send was 42MB, and the internet connection had decided today was the day it would test my patience. I watched that blue line creep forward, then stop, then creep forward again, and finally, after maybe five minutes of this torture, it failed. The attachment was too large. I knew it was. I knew it the moment I saved the file. But I was stubborn, and I thought maybe it would just work this time.

It did not work this time. It never works this time.

I had spent three hours on that proposal. It was detailed. It was beautiful. It also had high-resolution images of our team, product shots, and a few charts that I had exported as PNGs, which in hindsight was a terrible decision. The file was an absolute monster. I could not send it. I could not attach it. I could not share it the way I wanted to. And my client was expecting it in about twenty minutes.

That was the moment I realized I needed to learn how to reduce PDF file size properly, because my current approach of just hoping for the best was not working.

The first time I tried to compress a PDF

My first attempt at reducing the file size was not exactly elegant. I used an online tool that I found through a quick search, uploaded my massive proposal, and hit compress. The tool made the file smaller. I was thrilled. Then I opened the compressed version, and my heart sank. The images looked terrible. Not just a little compressed — pixelated, blurry, and completely unprofessional. The text was still readable, but the photos of our team looked like they had been taken with a flip phone from 2005. I could not send that to a client. It would have been embarrassing.

So I went back to the original file and tried a different tool. Same problem, different flavour. This time the colours were washed out and the text was still sharp, but the document just looked wrong. It felt like someone had drained the life out of it. I was starting to think that maybe I just could not compress this particular PDF without ruining it.

That was a frustrating lesson. I learned that not all compression is equal, and some tools just throw away too much quality to make the file smaller. What I really needed was a tool that knew how to prioritise. Text should stay sharp. Images can be reduced, but not demolished. And the overall document should still look like the original, just a bit smaller. That simple concept took me way too long to find.

The compromise nobody talks about

Here's the thing about compressing PDFs that I wish someone had told me earlier — there's always a compromise. You can't make a 50MB file into a 2MB file and expect it to look exactly the same. Something has to give. The key is knowing what you can sacrifice and what you absolutely cannot.

If you're dealing with a document that's mostly text, you can compress it a lot without anyone noticing. Text compresses really well. Images, on the other hand, are the heavy lifters. That's where most of the file size comes from. So if your document has a lot of images, you're going to have to make some choices. Do you need those images at full resolution? Probably not. Do you need them to look good on a screen? Yes. So you have to find the middle ground where the images are not pixelated but the file is small enough to send.

I learned that different types of documents need different levels of compression. A legal contract with mostly text can be compressed aggressively. A marketing brochure with full-page photos needs to be treated more gently. A scanned document is its own beast entirely. I used to apply the same approach to everything, and it never worked. Now I think about what the document actually needs before I compress it.

That sounds obvious when I type it out, but it took me a while to actually get it. I was just treating every PDF the same, and then wondering why some looked terrible and others were still too big.

What I still get wrong sometimes

Even now, I still make mistakes. Sometimes I compress a document and then realise later that I should have kept one of the images at a higher quality because it was actually important. Usually that happens when I'm in a rush and I just want the file to be small enough to send. I'll open it later on a big screen and think, oh, that could have been better.

There was one time I compressed a proposal with our team photo in it, and the photo ended up looking slightly blurry. I didn't notice at the time because I was on my laptop. Then the client opened it on a big monitor and made a comment about it. They were polite about it, but I felt awful. That photo was supposed to make us look professional. Instead, it looked like we had taken it from a distant security camera.

I also still sometimes forget to check the file size after compressing. I'll think the tool worked, I'll open the file quickly to make sure nothing is broken, and then I'll attach it and send it. Sometimes I find out later that I could have compressed it even more without losing quality, and I sent a file that was still bigger than it needed to be. That's not a disaster, but it is annoying.

And I still have that habit where I don't check the compressed file at all. I just trust the tool. I know that's stupid. I know I should check every time. But sometimes I'm in a hurry, and I just assume it worked. It usually does, but the one time it doesn't is always the worst possible time.

What I actually do now

These days I think about compression differently. I don't just think about making the file smaller. I think about making it smaller in the right way. For me, that means keeping the text sharp, keeping the images readable, and making sure the document still looks professional. If it doesn't look professional, there's no point sending it.

I've also learned to be more realistic about file sizes. Not every PDF needs to be tiny. If a document is 15MB and it's full of important images, that's fine. The problem is when a document is 50MB and it shouldn't be. I've gotten better at identifying those situations and handling them before they become a crisis.

One thing I do now is I actually check the images before I compress. If there's a photo that's way too high resolution for what it's doing, I'll reduce it first. Sometimes you can't reduce it in the PDF tool itself, so you do it beforehand. That's time-consuming, but it produces better results.

I also make sure to test the compressed file on different screens. What looks good on my laptop might look terrible on a client's large monitor. So I check it on a few different devices if I can. It adds a few minutes to the process, but it's saved me from sending embarrassing documents more than once.

When I need to reduce file size quickly without ruining the quality, I use PDFly's Compress PDF tool. It's not the flashiest tool out there, but it does one thing well — it makes the file smaller without making it look bad. It preserves the text, keeps the images reasonable, and tells me how much smaller the file actually is. That last part is surprisingly useful. I know exactly what I got, so I can decide if I need to do more or if I can just send it.

That proposal from earlier? The one that took three hours to send? I eventually got it down from 42MB to about 9MB. It took a few tries, and I had to make some decisions about which images to keep at full quality, but it worked. The client got the document, they didn't notice any quality issues, and I stopped trying to send giant files through Gmail like it was going to suddenly start working.

I still think about that moment sometimes, watching the upload fail, knowing I was going to have to redo the whole thing. It's not a fond memory. But it's a useful one, because it reminds me why I stopped hoping for the best and started actually learning how compression works.