u/Cute_Ad2883

Built a PDF toolkit recently where everything runs locally in the browser instead of uploading files to a server.

Main idea was:

• no accounts
• no watermarks
• no uploads
• works without Docker/self-hosting nonsense

I honestly can’t tell if I built something useful or just massively overengineered a personal annoyance 😭

Things I’m unsure about:

• does the “privacy/no uploads” angle matter to normal users?
• is “Mini Tool” a terrible name?
• are workflow builders/batch processing features something people actually care about in PDF tools?
• would anyone ever pay/tip for a tool like this?

Current status:

• launched recently
• some Reddit traffic
• zero paying users so far

Would genuinely appreciate brutal feedback on:

• the concept
• UX
• messaging
• whether browser-side PDF processing is even a meaningful differentiator anymore

I’ll drop the link if anyone wants to test it.

Genuine question for people running self-hosted PDF stacks:

If a PDF tool processes everything locally in the browser with no backend/upload endpoint at all, would you consider that more private than a traditional self-hosted setup where files still hit your server?

I was testing browser-side PDF processing recently and modern browsers/Web Workers handled way more than I expected.

Every time I needed to process a PDF I had two options:

1. Upload it to some random website and hope they don't store it forever
2. Self-host something like Stirling-PDF which requires Docker, a server, ongoing maintenance, and still processes files server-side

Neither felt right for sensitive documents. So a third option.

Mini Tool- A PDF toolkit that runs 100% in your browser. No server. No Docker. No setup.

No maintenance. Just open the URL and it works.

What it does:

- Compress, Merge, Split, Rotate PDFs

- Protect and Unlock PDFs (AES-256 encryption)

- Sign and Watermark PDFs

- Organize pages (drag and drop reorder)

- Batch process multiple files at once

- Workflow Builder (chain operations together)

- Images to PDF

- Smart Print Mode + Booklet Optimizer

The privacy angle that matters:

Every operation runs locally using pdf-lib and PDF.js in Web Workers. I opened DevTools and

confirmed zero outgoing file requests during processing. Your files genuinely never leave

your device.

For the self-hosted crowd specifically:

I know this community values owning your stack. The irony here is that "self-hosted" still means your files hit YOUR server. With browser-based processing the files never hit any server at all - not even one you control.

It's the most private PDF processing possible short of running offline desktop software.

What I'd love feedback on:

- Are there PDF operations missing that you regularly need a self-hosted solution for?

- Any edge cases with complex PDFs you'd want to test?

- Would an offline PWA version be useful to this community?

Checkout Comment

Built this because I was tired of "free" PDF tools that quietly upload your documents to their servers. Everything runs locally — compress, merge, split, rotate, protect, sign, watermark, batch process and more. Verified with DevTools — your files never leave your device.

The privacy angle was the whole point. Every major free PDF tool processes files server-side. Built Mini Tool to run everything locally in the browser using pdf-lib and PDF.js in Web Workers. 14+ tools. Zero uploads. Zero account. Zero cost. Would love honest feedback especially on mobile experience. [link in comments]