creatorvalet
FilesConvert, compress and reshape files — without uploading them anywhere.MetadataSee what your files quietly carry, then strip exactly what you choose.Text & dataFormatters, converters, and the character-encoding fixes nobody else gets right.PublishingCheck how your pages read to crawlers, to people, and to language models.CodesBarcodes, QR and identifiers that keep working after you publish them.CharactersFind the character you can draw but cannot name — and the font you cannot place.

Is iLovePDF safe?

Yes, on the available evidence. iLovePDF promises deletion in two hours, with an exception. We read the policy to find where that promise stops.

Updated 2026-08-07

Yes. Nothing we found suggests otherwise, and we went looking with the documents open.

What makes iLovePDF worth a page of its own is not doubt about the company. It is that they make the boldest deletion promise of any converter we track — two hours — and that the promise, like every promise of its kind, comes with a written boundary around it. Finding that boundary is a five-minute job. Knowing it will still be there next quarter is not a job anyone outside the company can do at all.

Is iLovePDF safe? Yes, and here is what that answer rests on

Two different kinds of statement get folded together whenever this question is asked, and separating them is most of the work.

One kind you can establish yourself, from your own machine, in under a minute. The other kind reaches you as text somebody wrote about a system you cannot see. Both can be entirely true. Only one of them stays true independently of who is running the company next year. The pillar for this cluster walks through where your own evidence runs out, and that boundary is the same for every uploading service, iLovePDF included.

iLovePDF processes your PDF on its own hardware. That is not a shortcut or an oversight — it is what makes OCR, signature workflows and 300-page merges possible at all, none of which a browser tab handles gracefully. The consequence is simply that your document takes a trip, and everything about that trip you know secondhand.

Two hours, quoted from where it is actually written

On August 7, 2026 we sat down with iLovePDF’s privacy policy end to end. It carries a visible revision date — Thursday, February 19, 2026 — which is worth noting because three of the six services in this comparison show no such date at all. A dated document is a document you can tell has moved.

The retention sentence commits the company to deleting processed files “within TWO (2) HOURS of being processed”. It is a short window, offered voluntarily, and we have no reason to think it is not honored. It is not the shortest in this comparison — ezgif writes one hour — though the two are not really the same measurement, since ezgif’s hour restarts from a file’s last use rather than from the moment it was processed.

The four words that decide who the two hours apply to

Read the whole sentence, though, and the number arrives with a passenger. Before it states the two hours, the policy carves out an exception: “except for iLoveSign services”, whose storage period is instead governed by that product’s own separate terms.

So the accurate summary is not iLovePDF deletes everything within two hours. It is that the two-hour figure covers the PDF tools and explicitly hands the signing product off to a different document with a different retention period. If you converted a file, that is the number for you. If you signed a contract, you have been pointed somewhere else and need to go read it.

That distinction is easy to lose, and it does get lost. iLovePDF’s own security page states the same commitment with no carve-out at all — files are “automatically and permanently deleted within two hours”. That page also carries no visible revision date, unlike the policy. Neither statement is false. A security overview is a summary, and summaries shed qualifiers; that is what makes them summaries. But it means the answer you walk away with depends on which of the company’s two pages you happened to open.

None of this is a trap laid for anyone. It is what a promise made in prose looks like when you inspect it closely: it has edges, the edges live in a document, and the document is revisable by its author at any time without asking you. That is not unique to iLovePDF. It is the condition of every retention promise ever published, ours included — the difference being that we do not need one, because there is nothing on a server to retain.

Counting the outside hosts on the front page

Separately from any document, we measured ilovepdf.com on August 7, 2026. The result was one third-party host: www.googletagmanager.com, pulled in by a <script> tag.

Now the caveat, which matters more than the number. What our script parses is the raw document the server hands over, tallying only those hosts named statically inside it. Anything a script fetches after the page is running is invisible to it. So this measurement says “one statically referenced third-party host in the served HTML” — and it emphatically does not say the page loads one outside resource. A tag manager exists precisely to load further things at runtime, which is the category our method cannot see.

We can show you exactly how much that matters, because our own earlier working note put iLovePDF at thirteen. The most likely explanation for thirteen versus one is that the older figure came from a live browser, after scripts had run and injected what they inject, while this one comes from raw server output. Both numbers can be correct about different questions. Publishing either without its method attached would be the actual error, and it is why the method sits in this paragraph rather than in a footnote nobody reads. For the same run, CloudConvert returned zero, Smallpdf two, FreeConvert three, ezgif four and Convertio six.

The credential we do not have

One more thing belongs on the positive side of the ledger, and leaving it out would make this page a sales pitch. iLovePDF’s security page reports an “ISO/IEC 27001:2017 certification, recently renewed in November-March 2023”, and links to the certificate itself. Behind that label sits a genuine outside inspection of how the company manages information security, carried out by assessors who were let in the door. This site holds nothing comparable and will not imply that it does.

It is worth being precise about what a certification is, in both directions. It is a periodic examination of process by a qualified outsider — genuinely more than a promise. It is not a live account of what became of your particular file on a particular afternoon. Nobody’s certificate is.

Things iLovePDF does that a browser tab cannot

Being straight about this is the price of being trusted on everything above:

  • OCR. Recovering words from a scan means recognizing shapes as letters, and we ship no such recognizer. If your PDF is a photograph of paper, we cannot help and they can.
  • Signing. Electronic signatures with an audit trail, through iLoveSign. A contract that needs signing should be signed there, not here.
  • Editing existing PDF text. Changing words already inside a PDF, rather than producing a new one.
  • Core PDF surgery. Merge, split, compress and page-level reorganization are their headline tools and are simply absent from this site.
  • Reach and scale. Desktop and mobile apps, an account with history, batch runs, an API, and Zapier and Make integrations. We have none of that, and hundreds of files at once is not a job for a tab.

Where a browser tab wins instead

The trade turns when the document is sensitive, the machine in front of you is adequate, and the task is ordinary. A payslip, a signed lease, a medical letter, a passport scan: for those, the shortest possible route is the one with no round trip in it, and the appealing part is that you can watch the absence rather than be told about it.

That is the narrow thing this site does. PDF to JPG and PDF to PNG pull pages out as images, PDF to text lifts text that is already text, and JPG to PDF and PNG to PDF go the other way. Each is one address doing one conversion, with the work happening in the tab you already have open — no retention window to read, because no copy is ever made anywhere you cannot reach.