iLovePDF Alternative for Redacting Without Uploading

What iLovePDF Is Actually For

iLovePDF started as a PDF merge-and-split utility and has grown into one of the most recognised general-purpose PDF toolkits online. As of August 2026 it bundles compression, conversion, e-signing, OCR and a Redact PDF tool into a single subscription, alongside a generous free tier for occasional use. Its customer base is broad by design: freelancers tidying up invoices, students converting lecture slides, small businesses that want one tool to handle everything rather than five specialist ones. Redaction is a feature bolted onto that toolkit, not the reason the product exists.

That matters for judging what the redaction tool is built to do. A general utility is optimised for coverage across dozens of tasks, not depth on one. It shows in how the Redact PDF tool is scoped: fast enough to sit alongside merge and split in the same menu, but not built to be the last line of defence before a sensitive file leaves an organisation.

How the Redaction Itself Behaves

Credit where it's due: iLovePDF's Redact PDF tool removes the underlying content from the page rather than drawing a box over it, which puts it ahead of a lot of free tools where the text is still selectable underneath the black rectangle. Content that's redacted is genuinely gone from the file structure, not just visually hidden.

The limitation sits upstream of that, in what gets flagged in the first place. Automatic detection covers three categories: credit card numbers, phone numbers and email addresses. Everything else, names, addresses, dates of birth, NHS numbers, National Insurance numbers, case references, employee IDs, has to be found by scrolling and highlighting manually. On a two-page invoice that's manageable. On a sixty-page disclosure bundle or a patient file, that's a manual search where one missed line becomes the whole incident.

On the trust side, iLovePDF's controls for the web tool are real and worth naming precisely: ISO 27001 certification, processing in the EEA or a nearby region, deletion within two hours, and a stated policy of not accessing or analysing your content. None of that is marketing fluff. It's also not the same question as whether the upload should have happened at all.

Where the Document Actually Goes

This is the part that matters most for a UK or EU compliance, legal or public-sector reader. The iLovePDF web tool is a server-side service: your file is uploaded, processed on their infrastructure, and deleted within two hours. The desktop app for Windows and macOS processes locally instead, which the vendor markets on exactly that privacy ground, but it sits behind a Premium subscription and a separate install, and its Redact tool is built on the same automatic detection as the web version, which covers three PII types.

For a lot of documents, a two-hour deletion window and EEA processing is a perfectly defensible position. For others it isn't a question of how good the controls are. Under UK GDPR, a data controller is expected to consider necessity and proportionality before any transfer to a processor, including a brief one for a low-risk task. Many law firms' client confidentiality policies, and many public-sector information-handling policies written around FOIA and SAR obligations, simply prohibit uploading a client file or a case record to a third-party server, full stop, regardless of retention period. In those environments the upload itself is the fact that needs explaining, not the two-hour clock that follows it.

How We Approach the Same Job Differently

When we tested the equivalent workflow in RedactProof, the document never left the browser tab, there was no upload step to wait on and no server-side processing to describe to a client if they asked where their file had been. Automatic detection runs against 60+ PII types rather than three, and it's presented as suggestions you review and approve before anything is touched, not an automatic action taken on your behalf.

Approval is where the actual redaction happens: confirmed matches get pixel-burned out of the export, which removes the underlying data rather than layering something over it, matching what iLovePDF's own Redact tool does correctly on the content it manages to catch. The difference is what happens next. Every RedactProof export carries an Ed25519-signed verification certificate with a QR code. A recipient, a regulator, a court, a counterparty, doesn't have to take your word for the file being what it claims to be. They scan the code or visit the verify page and see immediately whether the document matches what was signed. iLovePDF publishes no verification or signing mechanism for exported files, so once a redacted file leaves iLovePDF, there's no built-in way for anyone downstream to confirm nothing has changed.

That certificate is also the artefact that makes redaction defensible after the fact. If a redaction decision is ever questioned, whether internally or by a regulator, having a signed record of exactly what was removed and when is a materially different position than having only the exported PDF itself.

Who Should Still Use iLovePDF

If redaction is an occasional task on documents that carry no real confidentiality risk, an expired promotional flyer, a public tender document with a few contact details to strip, and you'd rather have one subscription covering merge, convert, compress and sign as well, iLovePDF's breadth and brand recognition are genuinely useful. Its free tier alone will cover plenty of low-stakes needs, and the desktop app closes some of the upload gap for anyone willing to pay for Premium and install it.

For anything that carries client confidentiality obligations, patient data, or a duty to disclose accurately and defend that disclosure later, the calculation changes: the question stops being how well the upload is handled and becomes whether the file leaves your machine at all.