About PDFDad

Thirty PDF tools that run on your device instead of ours — and a straight explanation of why that matters, how the site pays for itself, and what it cannot do.

What PDFDad is

PDFDad is a set of thirty PDF tools that run entirely inside your web browser. You open a page, add a file, press a button, and get a result — and at no point does your document travel across the internet. There is no upload, no queue, no temporary copy sitting on a server in a country you have never visited, and no retention policy you have to take on trust.

That is an unusual way to build this kind of site, and it is worth explaining why we did.

Why the files stay on your device

Almost every online PDF tool works the same way: you upload your document, a server processes it, and you download the result. It works well and it is easy to build. It also means that a file you considered private — a contract, a payslip, a medical letter, a scan of your passport, an unreleased set of accounts — has been copied onto hardware controlled by strangers, subject to whatever their security practices, retention schedule and jurisdiction happen to be.

Most of the time nothing goes wrong. But the risk is real and entirely avoidable, because browsers have been able to do this work locally for years. Modern JavaScript engines are fast, WebAssembly makes even optical character recognition practical on a phone, and the libraries needed to read and write PDFs are mature and open source. The only thing missing was somebody putting them together in a site that does not ask you to hand over your documents first.

So that is what PDFDad is. Every tool here — merging, splitting, compressing, converting, signing, redacting, encrypting — executes as code inside the tab you have open. You can verify this yourself in about ten seconds: open your browser's developer tools, switch to the network tab, and run any tool. You will see the page load, you will see the PDF library load once, and then you will see nothing at all while your file is processed. If you want to be thorough, load a tool page, disconnect from the internet entirely, and use it. It still works.

How the site pays for itself

Hosting a site that does no server-side processing is inexpensive, but it is not free, and neither is the time that goes into building and maintaining thirty tools. PDFDad is funded by the advertisements you see around the tools. That is the entire business model. We do not sell a premium tier, we do not sell data — we have none to sell, since your files never reach us — and we do not bundle software with the downloads.

We place ads above the tool and after the results, never inside the upload area and never beside the action or download buttons. Ads next to a Download button generate accidental clicks, which is bad for you, dishonest towards advertisers, and against Google's policies besides. If you run an ad blocker we would rather you kept using the tools than felt pushed away.

What we are honest about

Some things a browser genuinely cannot do as well as a dedicated desktop application, and we would rather say so on the page than have you discover it after sending a file to a client.

  • Converting a PDF back to Word or Excel is a reconstruction, not a recovery. A PDF stores positioned glyphs, not a document structure. Straightforward text documents convert well. Multi-column magazine layouts and complex tables do not.
  • Compression cannot shrink a file that is already small. It works by re-encoding images. A PDF that is mostly vector text has almost nothing to squeeze, and our tool tells you that rather than pretending it saved you something.
  • OCR accuracy depends on your scan. A clean 300 DPI page reads very well. A phone photo at an angle does not, and handwriting is not supported at all.
  • Permission flags are not a lock. An open password is real encryption. Restrictions on printing and copying are instructions that compliant readers obey and other software can ignore.
  • We will not crack passwords. Unlock PDF removes protection when you supply the correct password. It does not guess, and we are not going to build something that opens other people's documents.

Every tool that has a meaningful limitation carries a note about it on its own page, in plain language, above the fold rather than buried in small print.

Who builds it

PDFDad is a small independent project rather than a venture-funded company. It is built and maintained by a handful of developers who kept needing these tools, kept being uneasy about uploading documents to get them, and eventually decided to write the thing properly. There is no sales team and no investor deck. If you email us, a person who works on the code reads it.

Where it is going

The thirty tools here cover what most people need most of the time. The roadmap, in rough order:

  • Custom font embedding for Text to PDF, so that scripts outside Western European character sets — Chinese, Arabic, Devanagari, Cyrillic — typeset correctly rather than being replaced with question marks.
  • Batch mode, chaining several tools in one pass: split, compress and watermark a folder of documents without three round trips.
  • AES-256 support in Unlock PDF, which currently handles RC4 and AES-128.
  • Image extraction, pulling the original embedded images out of a PDF at their native resolution rather than re-rendering the page.
  • More OCR languages in the dropdown. Tesseract supports over a hundred; we list ten because those cover most requests, and we add others when people ask.
  • Interface translations, once the tooling for it is in place.

If something you need is missing, tell us. We prioritise by what people actually ask for, and bug reports always come before new features.

Getting in touch

The contact form reaches us directly, or you can email support@pdfdad.com. We read everything. We aim to reply within two working days, and we do reply — including to the messages that tell us something is broken.