The latest articles on DEV Community by junjie lin (@junjie_lin_42cfaed3aa0be3). https://dev.to/junjie_lin_42cfaed3aa0be3 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3965573%2Fb1ca490c-db7c-460f-86e1-5197eb95d3b8.png https://dev.to/junjie_lin_42cfaed3aa0be3 en junjie lin Thu, 04 Jun 2026 03:10:39 +0000 https://dev.to/junjie_lin_42cfaed3aa0be3/dealing-with-bloated-pdfs-without-ruining-diagram-clarity-3kla https://dev.to/junjie_lin_42cfaed3aa0be3/dealing-with-bloated-pdfs-without-ruining-diagram-clarity-3kla <p>Anyone else hit this exact wall?</p> <p>You have a 40MB PDF — technical spec, project doc, whatever — and you need to get it under 10MB for an upload. You Google a quick tool, drop the file in, wait... and then the download comes back with your architecture diagrams looking like this:</p> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fbz6bqxrkt7yleggo8fc6.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fbz6bqxrkt7yleggo8fc6.png" alt=" " width="800" height="615"></a></p> <p>The left side is what most "free" online compressors give you. The right side is what you actually need.</p> <h2> The two things that always go wrong </h2> <p><strong>1. Your vectors and text get rasterized</strong></p> <p>Any tool that just throws JPEG compression at the whole page will destroy your diagrams, code blocks, and sharp typography. What was a clean SVG-style flowchart becomes a blurry mess at 100% zoom.</p> <p><strong>2. The paywall shows up after you've already waited</strong></p> <p>You upload, you wait, you click download — and then: <em>"Upgrade to Pro to get your file."</em> Classic bait-and-switch. Infuriating every single time.</p> <h2> What we actually built (full transparency) </h2> <p>I'm part of the team that built <a href="https://compress.aurorapdf.com" rel="noopener noreferrer">compress.aurorapdf.com</a>. We ran into the same frustrations, so we built something to fix them.</p> <p>The core focus was <strong>separating what needs compression from what doesn't</strong>:</p> <ul> <li>Heavy background images → aggressively optimized</li> <li>Text layers, vector graphics, code blocks → left completely intact</li> <li>No watermarks, no account required, no paywall at the end</li> </ul> <p>You drop the file in. It shrinks. You download it. That's it.</p> <h2> Why diagram clarity matters for devs specifically </h2> <p>If you're sharing architecture docs, API specs, or anything with UML or flowcharts — blurry output isn't just ugly, it's <strong>actually unusable</strong>. A diagram where you can't read the labels is worse than no diagram.</p> <p>Most consumer PDF tools are built for résumés and forms. They don't care about vector sharpness. We do.</p> <h2> Try it on something complex </h2> <p>Honestly the best way to test it is to throw something at it that other tools mangle. A PDF with:</p> <ul> <li>Dense diagrams or flowcharts</li> <li>Small-font code snippets</li> <li>Mix of raster images and vector elements</li> </ul> <p>Drop it into <a href="https://compress.aurorapdf.com" rel="noopener noreferrer">compress.aurorapdf.com</a> and let me know what you get. Genuinely curious how it handles edge cases — and if it breaks on something, I want to know.</p> showdev productivity tools pdf