Why no-upload redaction matters
Redaction is usually used on documents that are sensitive by definition: bank statements, contracts, IDs, legal records, financial reports and other material containing private information.
A local browser workflow avoids sending the normal PDF file to a document-processing server for the redaction operation. The file stays on the device while the supported local workflow runs.
Load the PDF locally
Open Redact PDF and choose the document from your device. The browser reads the file locally for the supported redaction workflow instead of first transferring it to a remote converter.
Once the app and required resources are already loaded, supported local workflows can continue without relying on a document-upload round trip.
Mark only the information that must be removed
Draw blackout regions over the confidential text, numbers or images. Zoom in when working with small account numbers, addresses, signatures or identifiers.
Do not assume one occurrence is the only occurrence. Check repeated headers, footers and later pages before applying the final redactions.
Create and verify the redacted copy
Generate the redacted PDF and reopen the downloaded copy. The selected areas should be burned into the resulting page output rather than left as removable shapes.
Search, select and visually inspect the finished file before sharing it. Keep the original PDF unchanged in case the redaction selection needs to be corrected.
Use sanitization when hidden data also matters
A visually redacted document can still contain metadata or other hidden structures that are unrelated to the blackout boxes. If those traces also need to be removed, use the separate Deep Sanitize workflow.
This distinction keeps the jobs clear: Redact removes selected visible information; Sanitize rebuilds the document to remove supported hidden data and interactive structures.