Your PDF and Image Tools Are Uploading Your Files to Strangers Servers

#webdev #javascript #privacy #productivity

Your PDF and Image Tools Are Uploading Your Files to Strangers' Servers

Every time you merge a PDF or compress an image online, your files get uploaded to someone else's server. Think about that for a second.

That contract you're merging? Uploaded. Those personal photos you're resizing? Uploaded. That medical document you're converting? You guessed it — uploaded to a server you don't control, in a country you might not know, with a retention policy buried in a 12-page privacy policy you didn't read.

The dirty secret of "free" online tools

Most popular PDF and image tools work the same way:

You upload your file to their server
Their server processes it
They send back the result
Your file sits on their server for... how long? 🤷

iLovePDF says files are deleted after 2 hours. Smallpdf says 1 hour. But you're trusting a promise you can't verify. And during that window, your sensitive documents exist on infrastructure you don't own.

For a developer resizing a screenshot, maybe that's fine. But for a lawyer merging case documents? A doctor converting patient records? A business owner compressing financial statements? That's a real problem.

There's a better way: client-side processing

What if your files never left your device? What if all the processing happened right in your browser?

That's exactly what we built:

Parchment — Private PDF Tools

https://dannycranmer.github.io/parchment/

Merge PDFs — Combine multiple PDFs into one
Split PDFs — Extract specific pages
Compress PDFs — Reduce file size
Image to PDF — Convert images to PDF
PDF to Image — Convert PDF pages to images

Every operation runs entirely in your browser using JavaScript. Your files never leave your device. There's no upload, no server, no retention policy to worry about.

ImageToolkit — Private Image Tools

https://dannycranmer.github.io/imagetoolkit/

Compress Images — Reduce file size without losing quality
Resize Images — Change dimensions for any use case
Convert Formats — PNG, JPEG, WebP, and more
Crop Images — Precise cropping with visual preview
Watermark — Add text watermarks with full customization

Same principle: everything happens in your browser. Batch processing included. Download as ZIP.

How does client-side processing work?

Modern browsers are incredibly powerful. APIs like the Canvas API, File API, and libraries like pdf-lib and jsPDF let us do heavy file processing without touching a server.

When you upload a file to Parchment or ImageToolkit:

The file is read into your browser's memory
JavaScript processes it locally
The result is generated as a downloadable blob
Nothing ever hits the network

You can verify this yourself — open your browser's Network tab while using the tools. Zero outbound requests with your file data.

Why this matters

Privacy by architecture, not by policy. There's no server to breach.
Works offline. Once the page loads, you don't need internet.
No file size limits imposed by upload bandwidth.
Faster processing — no upload/download wait time.
No account needed. No signup. No email. Just tools.

The trade-offs

Client-side isn't perfect for everything. Very large files (100+ MB PDFs) might strain browser memory. Complex operations like OCR are harder without server-side power. But for 95% of everyday PDF and image tasks, client-side processing is not just adequate — it's superior.