How we compare
| Feature | itspdftools | iLovePDF | SmallPDF |
|---|---|---|---|
| File upload to server | No | Yes | Yes |
| Server-side storage | No | Yes (temp) | Yes (temp) |
| Account required | No | After 2 uses | After 1 use |
| Processing location | Your browser | Their servers | Their servers |
itspdftools
- File upload to serverNo
- Server-side storageNo
- Account requiredNo
- Processing locationYour browser
iLovePDF
- File upload to serverYes
- Server-side storageYes (temp)
- Account requiredAfter 2 uses
- Processing locationTheir servers
SmallPDF
- File upload to serverYes
- Server-side storageYes (temp)
- Account requiredAfter 1 use
- Processing locationTheir servers
How it works
01
You drop a PDF file
It stays in your browser's memory. Nothing is sent over the network.
02
JavaScript / WebAssembly processes it locally
The same technology that powers in-browser games handles your PDF — entirely on your device.
03
You download the result
The processed file is generated locally and saved to your machine. Nothing was ever sent anywhere.
What we don't do
- xWe don't upload your files to any server
- xWe don't store your files anywhere
- xWe don't require an account or login
- xWe don't track what's inside your documents
- xWe don't use your files to train AI models
Frequently asked questions
Is itspdftools HIPAA compliant?
Because files never leave your device, there's no server-side handling of PHI. This means no BAA is needed — the simplest path to compliance.
Can I verify this?
Open your browser's network tab while using any tool. You'll see zero file upload requests.
What about the service worker?
Our service worker caches app assets (HTML, CSS, JS) for offline use. It explicitly excludes all PDF files and user data.
Ready to try it?
Pick any of our 38 tools. Your files stay on your device, always.
Browse all tools