Compare
Filecraft vs iLovePDF
iLovePDF is the tool most people reach for first. It works — but it works by sending your file to their servers. Filecraft is built differently.
Your file is sent to their servers. Here, it never leaves your browser.
How each approach works
This is not a feature difference. This is an architectural difference.
- 1Your file is sent to their server over the internet
- 2Their server processes your file on their infrastructure
- 3A copy of your file exists on systems you don't control
- 4You trust their promise to delete it afterward
- 1Your file stays in your browser — it is never sent anywhere
- 2JavaScript in your browser tab does all the processing
- 3No copy of your file exists outside your device
- 4There is nothing to delete because we never had it
Feature comparison
| Feature | iLovePDF | Filecraft |
|---|---|---|
| Where processing happens | iLovePDF servers | Your browser |
| File transmitted | Yes | No |
| Account required | No | No |
| Works offline | No | Yes |
| Privacy model | Upload + deletion promise | Local — no transmission |
What you're giving up
iLovePDF processes files on their servers. When you use any tool, your file is transmitted to their infrastructure over the network. This is how server-side processing works — it is not a policy choice, it is the architecture.
iLovePDF states that uploaded files are deleted after processing. Whether that happens in minutes or hours, the transmission has already occurred. Your file existed, briefly, on a third-party server.
For most everyday files this trade-off is acceptable. For contracts, financial documents, or anything containing personal data, the architecture is worth understanding before you upload.
How Filecraft is different
- ✓Processing happens in your browser using WebAssembly — not on a server.
- ✓Files are never transmitted to any server, including Filecraft's.
- ✓No server-side copy is created or stored at any point.
I understand — now try it yourself.
Process your file locally