Use cases

Redact screenshots before they leave the browser

A drawn-on black box is not redaction: the pixels are still in the file underneath, and in a PDF the text layer often survives verbatim. If users are sending screenshots of billing pages or medical records, redaction that merely covers is a breach with extra steps.

Destroyed, not covered

The redaction tool removes the underlying pixels before the file is encoded. There is no layer to peel back, because the data was never written.

Before anything uploads

The whole edit happens client-side. What leaves the browser is the redacted file — the sensitive version never exists outside the user's machine.

Provable, not just promised

Because removal happens before encoding, the difference is checkable: extract the text layer of a delivered PDF and the redacted content simply isn't there — where a drawn-on box leaves it intact underneath. The home page shows that extraction side by side.

Questions people ask

Is the redacted text recoverable from the PDF?
No — redaction happens on the captured pixels before any file is encoded, so neither the raster nor any text layer contains what was removed. The landing page shows the extracted text of both approaches side by side.
Who controls what gets redacted?
The user, in the editor, before sending. If your compliance posture needs certain regions always removed, crop the capture target so they are never captured at all.