Search for a way to edit a PDF and you will find dozens of free "online" tools. Almost all of them share one design: you upload your file to their server, the server does the work, and you download the result. It is convenient — and it quietly puts your document on a computer you do not control.
Local-first tools take a different approach. The processing happens inside your own browser, so the file never travels across the network in the first place.
What "your file was uploaded" really means
When a document leaves your device, a few things become true that most people never think about:
- It exists, at least briefly, on someone else's disk.
- It may be logged, cached, backed up, or scanned by that service.
- Its safety now depends on that company's security, retention policy, and good faith.
For a holiday photo this is no big deal. For a contract, a bank statement, medical records, or a signed ID, it is a genuine exposure.
How local-first tools avoid all of that
A local-first tool loads its code once, then does everything on your machine:
- No upload: the bytes stay in the browser tab.
- Nothing to leak: a service that never receives your file cannot lose it.
- Works offline: once loaded, the tools keep working with no connection.
You do not have to take this on faith. Open your browser's developer tools, watch the Network tab, and run a conversion — you will see no request carrying your document.
Do everyday PDF tasks locally
Every OnsitePDF tool runs this way. A few common starting points:
- Merge PDF — combine several PDFs into one.
- Compress PDF — shrink a file for email.
- Protect PDF — encrypt a file with a password.
- JPG to PDF — turn images into a document.
Frequently asked questions
Is local-first really as capable as server-based tools? For the vast majority of PDF tasks, yes — modern browsers are powerful enough to merge, split, compress, and encrypt files directly.
How can I verify nothing is uploaded? Open developer tools, go to the Network tab, and perform an action. A local-first tool shows no request carrying your file.
Is there a catch? Very large files are limited by your device's memory rather than a server's, and the first page load downloads the tool code. After that, everything runs locally.