I Compared iLovePDF to Free PDF Tools: Here's What Actually Happens to Your Files

Last month I needed to merge some bank statements. I opened iLovePDF like I always do, then stopped. These files had account numbers. Where exactly was I sending them?

I spent a week testing the most popular free PDF tools to see what actually happens to your files. Not the marketing claims, the real behavior.

What does iLovePDF do with uploaded files?

iLovePDF processes files on their servers. According to their privacy policy, they store files temporarily for processing, then delete them after two hours. They're GDPR compliant and use encryption during transfer.

The catch: your files leave your computer. They hit iLovePDF's servers in Spain. For most documents, this is fine. For tax returns or medical records, you're trusting their deletion schedule.

I tested this with a 2.3MB PDF. Upload took 4 seconds on my connection. The file sat on their server while I worked with it. When I closed the tab without downloading, it stayed there until the two hour window expired.

How Smallpdf handles your data

Smallpdf works the same way. Server-side processing, 14-day retention for free users (they keep files longer so you can access your history). Their servers are in Switzerland, which has strong privacy laws.

They're transparent about it. The free tier explicitly trades convenience for data retention. Pay for Pro and files delete after one hour.

I actually like Smallpdf's interface better than iLovePDF. The drag-and-drop feels smoother. But that 14-day retention bothered me enough to stop using it for anything sensitive.

What "browser-based" actually means

Some tools, including Merge PDF and Compress PDF on JustUse.me, process files entirely in your browser. No upload. The file never leaves your device.

Here's how I tested this: I opened Chrome DevTools, went to the Network tab, and processed a PDF. Zero network requests to external servers. The file processing happened locally using JavaScript libraries like PDF-lib.

The tradeoff is speed. Browser-based tools are slower for large files because they're using your device's processing power. A 50MB PDF that iLovePDF compresses in 8 seconds might take 25 seconds in your browser.

For a 5MB file? The difference is negligible. For a 100MB file? You'll notice.

File size limits tell you about infrastructure

iLovePDF free tier: 25MB per file, 200MB per day Smallpdf free tier: 5MB per file (seriously) Sejda: 50MB per file, 200 pages PDF24: No hard limit but slows down after 100MB

These limits exist because server processing costs money. When you upload a file, they're paying for bandwidth, storage, and compute time.

Browser-based tools like Split PDF don't have these limits because they're not paying for your processing. I've split 200MB files without issues. It just takes longer.

The feature gap nobody talks about

Server-based tools can do things browser tools can't. OCR (text recognition from scanned PDFs) requires heavy processing. iLovePDF's OCR is genuinely good. You can't replicate that in a browser without downloading gigabytes of language models.

Same with advanced compression. iLovePDF can reduce file sizes by 60-70% because they're running optimized server-side algorithms. Browser compression typically hits 30-40% because the algorithms need to be lightweight enough to run in JavaScript.

If you need OCR or maximum compression, you need server processing. There's no way around it.

What I actually do now

For sensitive files (anything financial, medical, or legal), I use browser-based tools. The speed hit doesn't matter when I'm processing 2-3 files.

For bulk work or files that need OCR, I use iLovePDF. I'm not worried about them seeing my ebook collection or work presentations.

For anything in between, I ask: would I email this file to a stranger? If no, it stays local.

The privacy policy thing everyone skips

I read the privacy policies. Here's what matters:

iLovePDF collects: IP address, browser info, usage data. They use Google Analytics. Files are deleted after 2 hours but metadata about your usage isn't.

Smallpdf collects: Same, plus they track which features you use to improve the product. More detailed analytics.

Browser-based tools: Can't collect file data because they never see it. They might still use analytics for page visits.

The real question isn't whether they collect data. It's whether you care that they know you processed 47 PDFs last month.

Speed benchmarks I ran

I tested the same 12MB PDF across tools:

• iLovePDF merge: 6 seconds
• Smallpdf merge: 7 seconds
• Browser-based merge: 18 seconds
• Adobe Acrobat online: 5 seconds (fastest, but requires sign-in)

For compression of a 45MB file:

• iLovePDF: 11 seconds, reduced to 8MB
• Smallpdf: 13 seconds, reduced to 9MB
• Browser-based: 52 seconds, reduced to 18MB

The quality difference was visible. Server-side compression is legitimately better.

When "free" isn't really free

iLovePDF free tier is generous. You hit limits with heavy use but casual users never notice.

Smallpdf's 5MB limit is aggressive. It pushes you toward the $9/month plan.

Browser-based tools are actually free because there's no server cost to monetize. The business model is usually ads or optional premium features, not forcing upgrades through artificial limits.

What about mobile?

This is where server-based tools win. iLovePDF's mobile app works great because all processing happens on their servers. Your phone just sends and receives files.

Browser-based tools struggle on mobile. Processing a large PDF on a phone browser can crash the tab. The technology isn't there yet.

If you work on mobile frequently, you need a server-based solution.

The honest answer is that both approaches have legitimate uses. I keep iLovePDF bookmarked for quick jobs and use browser-based tools when privacy matters. The "best" tool depends entirely on what you're processing.