You search for "merge PDF", click the first result, drop in your files and get a merged document a few seconds later. It feels like a tool on your computer. It is not. In most cases your file travelled across the internet to a server, was processed there and came back. This guide explains what that means, which documents deserve more care, and what to do instead.
This is not a warning against any particular company. The established services publish how long they keep files and most are careful. The point is simpler: you cannot undo an upload, and you cannot see what happens to a copy once it has left your device.
What happens when you upload a file
- Your browser sends the file to the website's servers, normally over an encrypted HTTPS connection. Encryption protects the file in transit, not once it arrives.
- The server stores the file, at least temporarily, so a tool can read and change it.
- The result is created and stored, then offered for download.
- The service deletes the files later, according to its policy, or when you press a delete button if one exists.
Each step involves a copy. Even a service that does everything correctly has, for a while, a complete copy of your document on infrastructure you do not control.
Retention windows differ
Providers state how long they keep files, and the figures are short. As of October 2026, iLovePDF says uploaded documents are removed within two hours. Smallpdf says files from its free tools are deleted after one hour. PDF24's privacy policy says files and results are usually deleted one hour after upload or creation. Adobe says its online tools delete files shortly after use unless you sign in and save or share them, in which case they are stored in Document Cloud.
Those are reasonable promises and short windows. But they are still policies, not technical guarantees you can check. Account storage features, signature requests and some tools keep data longer: iLovePDF, for example, says signing data is stored for a month. If a tool asks you to create an account, ask what is stored there.
Things you do not see
- Logs. Servers often keep access logs such as your IP address, the time, the tool you used and sometimes the file name.
- Backups. A file on a server may be copied to a backup before it is deleted, depending on how the service is built.
- Third parties. Services use hosting providers, content delivery networks, analytics and payment processors. A policy usually lists categories of providers even if it does not list every system a file touches.
- Jurisdiction. The server may be in a different country from you, with different rules on access by authorities and different data protection law. Some providers name a region, such as the EU or Ireland. Others name none.
- Staff access. Any system that stores your file can in principle be reached by the people who run it. Good companies restrict this, but you are relying on that restriction.
Breaches and mistakes
No provider is immune to errors or attacks. Misconfigured storage, stolen credentials and software bugs have exposed files held by companies of all sizes across the technology industry. The shorter a file is kept, the smaller the window. A file that was never uploaded cannot be exposed in a server breach. That is the most honest argument for keeping files local.
Which documents deserve the most care
- Identity documents: passports, driving licences, national ID cards and scans of them.
- Tax returns, payslips, bank statements and anything with account numbers.
- Medical records, test results and insurance forms.
- Contracts, legal letters, settlement papers and business plans.
- Anything covered by a confidentiality agreement or your employer's data policy.
- Documents about children or other people who have not agreed to share them.
If you handle documents for work, your employer or clients may have rules about using third-party websites. Check them before using any free tool, however reputable.
Where an upload is fine
Not everything is private. A public flyer, a school newsletter or a recipe collection has no real downside if it is processed on a server. Using an online service for such files is a sensible, convenient choice. The aim is to match the tool to the file.
Safer options
Use tools that run on your device. Browser tools can do the processing locally with JavaScript and WebAssembly. DocPro works this way: merge, split, compress, convert, OCR, protect and more run in your browser without sending the file anywhere. Read how on-device tools work for the details and the limits.
Use desktop apps and built-in tools. Offline apps keep files on your machine. macOS Preview can combine pages, annotate, fill forms and sign. Windows can print to PDF, and Edge opens PDFs. LibreOffice exports PDFs with passwords and certificate signing. PDF24 Creator is a free Windows desktop app. Stirling-PDF can be self-hosted so files go only to a server you run.
Reduce what the file contains
Before sharing any document, remove what the recipient does not need. Clean the metadata such as author and software information, remove location data from photos, and add a password for files you send by email. A password does not make an upload to a third party private, but it limits who can open the file you share. See how to password protect a PDF.
Verify instead of trusting
Some sites claim that files stay in your browser. You can test that yourself in a few minutes without any technical background. Our guide on how to check whether a PDF website uploads your files walks through it.
A short test: if a file is private enough that you would not email it to a stranger, do not upload it to a website you cannot verify.
The honest summary
Uploading to a reputable PDF site is usually fine for ordinary files and the risk is low. For identity documents, financial records, medical files and contracts, the risk is small but permanent, and a local alternative costs you nothing. Choose the option where nobody else ever holds a copy.