Some online PDF tools upload your document; others never send it anywhere. How to tell which one you are using, what the major tools' own terms say about deletion, and the checks worth running.
The question usually arrives after the fact: someone has merged a contract, or compressed a scan of an ID, and then wondered what is sitting on someone else's server. It is a fair question to ask before the next upload, and it has a concrete answer rather than a reassuring one.
Online PDF tools are not one category. Some read your file over the network; others run their code on your machine and never send it. Which one you used is a property you can check, not something you have to take on trust.
Two different kinds of tool
An upload-based tool transfers your document to a server, processes it there, and hands back a result. The file exists somewhere you do not control, for a period its terms define. A browser-based tool downloads its code once and runs it locally: the file stays on your device, and the only network traffic is the page itself.
The interface is almost identical in both cases - a drop zone, a button, a download link. The difference is invisible unless you look for it.
How to check in one minute
- Open the tool page and load your file, then open the browser's developer tools (F12) on the Network tab.
- Watch what happens when you press the action button. A POST request carrying your document means it was uploaded.
- Read the tool's privacy or terms page for how long files are kept, and when the clock starts.
- For anything genuinely sensitive - legal, medical, financial, identity documents - prefer a tool that transmits nothing, so the question is settled by design.
What the major tools' own terms say
Policies change, so read them yourself before relying on a summary. These are direct quotations from each provider's published policy, checked on 1 October 2026:
| Tool | What its policy says about your files |
|---|---|
| iLovePDF | "ILOVEPDF will delete the files of your Content ... within TWO (2) HOURS of being processed on ILOVEPDF's servers." |
| PDF24 | "All files uploaded by the user and the results created are usually deleted one hour after uploading or creating the results." |
| Sejda | "All user-uploaded files as well as the processed output files will be permanently deleted after upload or processing respectively." |
| Smallpdf | "We will generally aim to delete User Files within a reasonable period of time after the last time they were opened" - and the policy notes that "this retention period is extended every time you reopen the respective User File." |
Retention statements quoted from each provider's own policy (checked 1 October 2026)
What the answers mean in practice
Two hours and one hour are ordinary, well-documented practices - the file exists on a server for a defined window and then is deleted. The Smallpdf wording is the one worth reading twice: the clock starts when you last opened the file, and reopening it resets the period. Neither is a scandal; it is simply a different risk model from a tool that never receives the file at all.
Deletion promises also cover the copy you uploaded, not necessarily metadata about the upload - timestamps, file names, IP addresses - which policies usually retain longer for abuse prevention.
Where browser-based tools are genuinely better
- Confidential or client documents: no third party ever holds the file, so there is no retention period to evaluate.
- Managed machines at work or school: nothing is transmitted, so there is nothing for a network filter to log.
- Files you would not upload anyway: passports, contracts, medical records, unreleased material.
- Offline work: a tool that runs locally keeps working when the network does not.
Where they are genuinely worse
Honesty cuts both ways. Local processing is bounded by your device: a browser will struggle with a multi-gigabyte scan that a server would swallow. It also cannot do work that requires a service - and any tool that quietly does should say so on its page.
GainUtility's own position, stated plainly: PDF merging, splitting, compression, conversion, OCR, and metadata removal run in your browser with the file never uploaded. The PDF Translator is the exception - it keeps the PDF local but sends the extracted text to a third-party translation service, and its page says so. Check any tool's disclosure the same way you would check anyone else's.
A short checklist for any tool
- Does the page state where processing happens? Silence is a reason to check the network tab.
- If it uploads, what does the policy say about deletion - and does the clock start at upload or at last access?
- Is there a free tier with a daily task limit? Limits are not a safety problem, but they tell you the business model.
- Does the tool ask for an account before you can try it? More data collected than the task needs is a signal.