Every day, millions of people upload sensitive documents to online PDF converters — tax returns, contracts, identity documents. Those files pass through a server you do not control. dailytool takes a different approach: everything runs locally in your browser.
How browser-based PDF processing works
Modern browsers can parse and write PDF files entirely in JavaScript. We use proven open-source libraries such as PDF-lib and PDF.js. Your document is read from your device, processed in memory, and written back to your device. At no point in that flow is your file sent over the network.
The only network request a PDF tool makes is to load the library itself — and after that first load, the tool keeps working. Because the working copy lives only in memory, closing the tab deletes it.
What you can do without uploading
- Merge several PDFs into one, in any order.
- Split one PDF by page ranges into multiple files.
- Compress by re-encoding objects and images.
- Unlock or password-protect a file.
- Rotate pages, watermarks, and add page numbers.
- Convert HTML, images or Office files into PDF via the print engine.
Limits you should know about
Because your browser does the work, very large files are limited by device memory. Files under about 200 MB work well on a desktop browser. Scanned PDFs are images, so text extraction from them is not available — that is not something any of our tools can do, regardless of the approach.
Office-to-PDF and file-to-PDF conversions use the browser print pipeline, which is the same engine your browser uses for Print to PDF. Styling and fonts match what the browser renders.
Why it matters for privacy
If a file never leaves your device, it cannot be read, logged, sold or leaked. That is a meaningful guarantee that no cloud service can offer. It is also why these tools work without accounts: there is nothing to store.
Next time a document scans the QR code of an "online PDF tool", check whether the tool says it uploads. Ours do not, because they cannot — by design.