BRAIN BEHIND THE CODE - SUDHAKAR

About DSPDF

DSPDF is a suite of PDF tools that run entirely in your browser. Nothing is uploaded. There are no accounts. There's no server processing your files.

Why we built this

We started DSPDF because we were tired of a specific problem: every time we needed to merge two PDFs, add a signature, or remove a page, we ended up on some website that wanted us to upload our file to a server we knew nothing about. Often the site was plastered with ads and buried under cookie banners. Sometimes it asked for an email address. Always, it was uploading our document to a random machine.

For a menu PDF, this doesn't matter. For a rental agreement, a tax return, or a medical record, it does. And it bothered us that the alternatives were (a) pay for a desktop app, (b) upload to a sketchy site, or (c) just not do the thing.

Modern browsers made option (d) possible: do the work in the browser, keep the file on the user's device, and don't have a server at all.

How DSPDF works

DSPDF is a static site. There's no backend. When you open a tool page:

• Your browser loads HTML, CSS, and JavaScript files (the same ones every visitor loads).
• You pick a file from your device. The browser reads it into memory using the FileReader API — no network activity.
• Processing happens using JavaScript libraries like pdf-lib and pdf.js, running on your CPU.
• The result is created as a Blob in memory and saved to your disk via the browser's download mechanism.

Throughout this sequence, no file content is sent over the network. This is provable: open your browser's DevTools, clear the Network tab, and use any tool. You'll see no outgoing requests carrying your file.

You can also test it differently: load a tool page, disconnect from the internet, and use the tool. It still works. That's the strongest possible proof that processing is local.

Our principles

1. Honest about limits

We won't claim a feature works unless it actually does. If a tool can't edit existing PDF text (which no browser tool can, reliably), we say so. If compression would degrade text quality, we warn you. If our encryption uses a weaker algorithm than you might expect, we tell you. Trust is more valuable to us than a slightly better-looking marketing page.

2. Client-side by default

If a task can be done in the browser, it should be. There are rare cases where servers are genuinely needed (massive-scale OCR, for example), but most PDF operations aren't one of them. We default to local processing and only move to a server when there's no alternative.

3. No tracking by default

Our site ships with analytics disabled. We don't use cookies unless you enable something that needs them. There are no third-party trackers. If you want to see how many people visit your site, you can turn analytics on in the config — but it's off out of the box.

4. No dark patterns

We don't put fake "Upload" buttons that lead to ad pages. We don't hide the download button behind a newsletter signup. We don't disable right-click. The tools work as advertised and the interface gets out of the way.

5. Open-source foundation

DSPDF is built on top of widely-used open-source libraries: pdf-lib, pdf.js, Tesseract.js, jsPDF, JSZip. These are maintained by communities and used by thousands of projects. If you want to audit what happens under the hood, everything is inspectable.

What we don't do

• We don't edit existing PDF text. No browser-based tool can do this reliably. Anyone claiming to is either misrepresenting the capability or producing text overlays that look edited but aren't.
• We don't crack passwords. Our Unlock tool removes passwords you already know. It's not a brute-forcer and won't be.
• We don't provide cryptographic signatures. Adding a visual signature to a PDF is not the same as signing it with a certificate. We don't pretend otherwise.
• We don't use "AI" for anything. No machine-learning models are running behind these tools. They're deterministic file operations.

Who's behind DSPDF

👉 OWNER: Replace this section with your own story. Consider mentioning:

• Your name or team
• Your background (developer, designer, teacher, etc.)
• Why you personally got interested in this problem
• Where you're based (country/region is fine)
• How to reach you (the Contact page has details)

A few honest sentences here are worth more than paragraphs of generic marketing copy. Visitors want to know there's a real person behind the site.

Roadmap

Things we're working on, or would like to:

• Page reordering tool. Drag-and-drop reordering of pages within a PDF, without needing to extract-and-merge.
• Custom TTF font embedding in the PDF editor and text tools. Currently only standard PDF fonts (Helvetica, Times, Courier) are supported.
• True invisible text rendering in OCR output. Currently we use a very-low-opacity overlay, which works but isn't ideal.
• Per-page cropping. Currently crop applies the same margins to every page.
• Better Hindi OCR. Tesseract's Hindi model works but is limited. We're watching for improvements.

Feedback and support

If you find a bug, have a feature request, or want to say hello, see the Contact page. We read everything, though we can't promise a fast reply.