# What happens to your PDF when you upload it to a free website?

**Short answer.** In almost every free suite your file travels to a server, is
processed there and is deleted after a window the company itself declares:
iLovePDF says two hours, PDF24 says one. In the meantime a copy exists outside
your control, under the provider's jurisdiction. The only way to avoid it is a
tool that processes in the browser, and you can check it in thirty seconds: open
the network inspector or turn off WiFi and see whether the tool keeps working.

---

## The trip your file takes

When you compress a PDF on a typical website, this happens:

1. The browser uploads the whole file to a server.
2. The server writes it to disk or memory.
3. A process transforms it.
4. The result is stored and you get a download link.
5. After a window, both files are deleted.

Each step is reasonable on its own. The problem is the whole: for that window a
complete copy of your document lives on infrastructure you do not control, and
the download link is usually accessible to whoever holds it.

If the document is a brochure, fine. If it is a medical record, a contract under
a confidentiality clause or your team's payroll, you just transferred personal
data to a third party, and you are still the data controller.

## What the policies say, in their own words

Review of public policies in **September 2026**. Worth re-checking: they change.

| Service | Uploads the file? | Declared retention |
|---|---|---|
| iLovePDF | Yes, to their servers | Two hours: «within TWO (2) HOURS of being processed». Signed documents, up to five years |
| PDF24 | Yes, and says so explicitly | One hour. «During this hour we do not look at the files» |
| Adobe Acrobat online | Yes | No public window in the free tools; 24 hours in the API only |
| Smallpdf | Yes | We could not verify it: in our review, the privacy and security pages did not respond from their own domain |
| Stirling PDF | No if you self-host it; yes in their cloud version | Not applicable when self-hosted |
| Tools that process in the browser | No | Nothing to retain |

Two honest readings of that table.

First: **one or two hours is a short time**. These companies are not doing
anything shady; they publish the window, which is more than many do.

Second: **the window is irrelevant if the document should never have left**.
Professional privilege is not measured in hours. For a document under medical
confidentiality or attorney-client privilege, the question is not how long they
keep it but why it left at all.

## The risk that is not in the policies

There is a second problem, of a different nature: the websites that *are* shady.

In March 2025 the FBI's Denver field office publicly warned about free file
converter tools used to distribute malware and steal data from uploaded
documents. The pattern is simple: the tool works, returns the converted file,
and along the way keeps the content or hands you an executable.

The difficulty for a user is that **an honest site and a malicious one look the
same**. Both have an upload button, both return the file. The difference is what
happens to the copy, and that cannot be inspected from outside.

That is why the robust guarantee is not picking the right provider, but picking
an architecture where there is no copy to protect.

## Is it safe to upload documents to iLovePDF?

It is the most searched question, so we answer with what can be checked
(reviewed on 27 September 2026 at
[ilovepdf.com/help/security](https://www.ilovepdf.com/help/security)):

- iLovePDF holds **ISO/IEC 27001** certification: “iLovePDF proudly holds
  ISO/IEC 27001:2017 certification”. It is a security management system audited
  by a third party, which we do not have.
- It deletes what it processes: “All files processed within our platform are
  automatically and permanently deleted within two hours of being processed”.
- It keeps signed documents longer: “We retain signed documents for a maximum
  of 5 years”.

So the honest answer is: for most documents, iLovePDF has serious controls. But
**the file leaves your device** and sits on their servers for that time. If a
document must not leave your device (a medical record, a case file, a statement
with your account), no website that uploads files meets that condition, however
good its policy. In that case, use a tool that processes locally, ours or
another, and check it with the method in the next section.

## How to check it yourself, in thirty seconds

Two home tests that need no technical knowledge.

### Test 1: turn off the internet

1. Open the tool once while online.
2. Turn off WiFi and mobile data.
3. Drop a file and process it.

If it works, the job runs on your machine. If your file were uploaded to a
server, none of it could work offline.

### Test 2: watch the Network tab

1. Press F12, or right-click and «Inspect».
2. Open the **Network** tab and filter by **Fetch/XHR**.
3. Drop the file and process it.

If your document is uploaded you will see the request and its size: a 4 MB PDF
shows up as a 4 MB request. If nothing appears, nothing left.

### Test 3, for those who want to go further

Look at the site's response headers, in the same Network tab. A
`Content-Security-Policy` header including `connect-src 'self'` means the
**browser blocks** any transfer to an external server, even if the page's code
wanted to. That is the difference between a promise and a verifiable technical
property.

## What does leave, even with a local tool

For honesty, because «zero connections» is usually marketing exaggeration:

- **The page itself.** HTML, CSS, JavaScript and fonts are downloaded from the
  server, as on any website. That is not your file.
- **Your IP address** reaches the server that serves the page, same as visiting
  any site.
- **Ads and analytics, if any.** This is the fine print worth reading: a tool can
  process locally and still load third-party trackers on the same page.

What should never leave is the document's content, its name, its size or a
summary of it.

## What to do with this

If the document is public, use whatever is convenient. The real risk is low and
the big suites work well.

If the document holds third-party data — patients, clients, employees, minors —
the right question is not «do I trust this website?» but «does this file need to
leave my machine to do this?». For compressing, merging, splitting, rotating,
converting, extracting text or setting a password, today the answer is no.

You can check it right now with any of the tools on
[this page](/en/tools/): all of them process on your device, and the three tests
above work on all of them.
