PDF tools that don't upload your file: are online PDF tools safe?
Upload-based and in-browser tools side by side
Both kinds of tool can merge, split, compress or sign a PDF. The difference is where the work happens, and that decides who else holds a copy of your file, even briefly.
| Aspect | Upload-based online service | In-browser processing (PDFont) |
|---|---|---|
| Where the file goes | It is sent to the provider's servers and processed there. | It stays on your device and is processed inside the browser tab. |
| Copies elsewhere | A copy exists on the provider's servers until it is deleted under their retention policy. | No copy is made on any server, so there is nothing to delete. |
| Account | Often optional for simple tasks; higher limits usually need an account or a paid plan. | No account and no sign-up. |
| Free limits | Free use is often capped by tasks per day, file size or pages. | No daily task limit; up to 500 MB per job on a computer and 100 MB on a phone. |
| Speed | Depends on your connection (upload and download) and the provider; works on slow devices. | No upload wait; depends on your device’s processor and memory. |
| Office conversion and OCR | Commonly offered. | Not available today. |
| How you verify it | You read the provider's privacy policy and trust that it is followed. | You can watch the Network tab and see that the file is never sent. |
What happens when a tool uploads your file
An upload-based service sends your file to its servers, typically over an encrypted (https) connection, runs the task there and gives you a download link. Many services publish how long they keep files; for example, one large service says on its security page that processed files are deleted automatically within two hours, with signed documents as an exception that is kept for up to five years to meet legal requirements [1].
That is usually fine for a menu or a flyer. For a passport scan, a contract, medical results or a payslip, it means a copy sits on someone else's computer for as long as their policy says, and you have to trust that the policy is followed.
How in-browser processing works
With in-browser processing, the site sends you the tool’s code and your browser runs it. When you add a file, it is read into the memory of that tab, processed there and saved straight to your device. There is no upload step, so there is no server copy to worry about.
PDFont works this way for every tool. The site still downloads its own code, fonts and WebAssembly files, and on the live site a cookie-free analytics script counts page visits; none of these requests carry your file.
What in-browser tools can't do today
Processing on your own device has real trade-offs, and it is better to know them before you start:
- Speed depends on your device. A recent laptop handles large files quickly; an older phone can take noticeably longer on heavy jobs such as compressing a long scan.
- Size is limited by memory. PDFont accepts up to 500 MB per job on a computer and 100 MB on a phone, and very large files can still fail on a device with little free memory.
- Converting Word, Excel or PowerPoint files to or from PDF is not available today.
- Text recognition (OCR) for scanned documents is not available today.
- Keep the tab open until you have downloaded the result: closing it discards both the file and the result.
When to use which
Choose an in-browser tool when the document is sensitive: ID cards, contracts, health or financial records, or anything with other people’s personal data. It is also the simple answer when your workplace does not allow uploading files to third-party services.
An upload-based service can make more sense when you need something that only runs on a server, such as OCR or Office conversion, or when your device is too slow for a very large file. In that case, read the provider's privacy and retention policy first, and remove anything you do not need to share.
How to check any PDF tool yourself
You do not have to take any site's word for it, including ours. Your browser can show every request a page makes:
- Open the tool page, then open the developer tools (F12 on Windows, Cmd+Option+I on a Mac).
- Go to the Network tab and clear the list.
- Add your file and run the task.
- Look at the outgoing requests. A POST, PUT or any other request that sends about as much data as your file means it was uploaded; if there is no such request, the file stayed on your device.
Detailed steps for Chrome, Edge, Firefox and Safari are on the page How it works.
Frequently asked questions
- Are online PDF tools safe?
- Many services publish how long they keep uploaded files, and you can check that the address uses https; for everyday documents that is often acceptable. The difference is that an upload-based tool holds a copy on its servers for a while, while an in-browser tool never receives the file at all. For sensitive documents, a tool that does not upload is the safer choice.
- How can I tell whether a PDF tool uploads my file?
- Open your browser's Network tab, run the tool and look for a request that sends a file-sized payload. A tool that works in the browser shows GET requests for its own code, fonts and WebAssembly files; these can be large, but they are downloads to your device, not an upload of your file.
- Is in-browser processing slower?
- Not necessarily. There is no upload or download wait, so small and medium files are often quicker. Very large files depend on your device's processor and memory, and an older phone can be slow on heavy tasks.
Sources
- iLovePDF, Security help page: processed files are automatically and permanently deleted within two hours of being processed; signed documents are an exception and are retained for a maximum of five years to comply with legal requirements. https://www.ilovepdf.com/help/security (checked )