Private Preview
Join Waitlist →

PDF Redaction

Redact sensitive data from PDFs without uploading to the cloud

4 min readAuthor: Redactorr Support Team · [email protected]Last reviewed: March 2026

Outcome

Redact a text-layer PDF in the browser and export a reviewed copy.

Your progress

Mark each step as you complete it. This is saved only in this browser.

0 / 3 steps complete

Before you start

Use a PDF that has selectable text when possible.
Know whether the file is a digital PDF, scanned page, photo, or handwritten document.
Keep the original file local and review the redacted export before sharing it.

Visual frame

Review asset

PDF redaction storyboard

Synthetic PDF frame only. It separates text-based PDF review from scanned or photo-document boundaries.

SourceCheck PDF type
ReviewPage by page
ExportOpen final PDF

Synthetic frame

PDF source check

Text-based and scanned PDFs behave differently.

Selectable textUse PDF review
Scanned pageUse boundary guide
Photo documentVerify carefully
The source type determines the safest review path.

Instructional PDF review frame

A simplified PDF workflow frame. It shows the expected review areas without claiming to be a live screenshot.

File checkConfirm selectable text before relying on text-layer redaction.
Browser previewUse the preview to verify page and extraction state.
Export proofOpen the exported result before sending it onward.

Guided steps

Follow the task, then check the result.

Confirm the PDF type

Open the PDF and try selecting a line of text. Selectable text usually follows the standard PDF redaction path; scanned, photo, or handwriting cases need separate guidance.

PDF preview with a selectable text check.
Success check: You know whether the PDF has selectable text or needs scanned/photo guidance.

Upload the PDF and wait for the preview

Upload or drag in the file. Redaction processing for the file happens in the browser; support diagnostics should not receive raw document text by default.

Upload area followed by PDF preview.
Success check: A preview appears and the redaction review path becomes available.

Review every marked item before export

Move through the detected items, confirm expected marks, and ignore any item that should remain visible. Export only after the review state matches the document you need to send.

Detected items beside a PDF page preview.
Success check: The exported PDF has visible redaction where expected and no raw values in those spots.

Branch questions

Completion check

The PDF preview loaded and the relevant pages were reviewed.
Expected sensitive values are covered in the exported copy.
Scanned, photo, or handwriting cases are routed to the current support-status article.

Support boundary

Support can use by default

  • File type category and rough size band.
  • Upload, preview, review, or export step name.
  • Error category and browser metadata.
  • Intent ID
  • Article slug
  • App route
  • Browser and viewport

Requires your consent

  • User-written description
  • Email address
  • Explicit attachment
  • Redacted sample
  • Support bundle previewed to the user

Not collected by default

  • Raw original document text
  • Full local file paths
  • Pasted private content
  • Unmasked screenshots
  • Replay capture

Safe support summary

Copy a scrubbed handoff.

Redactorr KB support summary

Article: /knowledge-base/pdf-redaction
Selected issue: A supported PDF type fails to preview.
Playbook progress: 0/3 steps marked complete

Safe context to include:
- File type category and rough size band.
- Upload, preview, review, or export step name.
- Error category and browser metadata.
- Intent ID
- Article slug
- App route
- Browser and viewport

Requires explicit consent:
- User-written description
- Email address
- Explicit attachment
- Redacted sample
- Support bundle previewed to the user

Do not include by default:
- Raw original document text
- Full local file paths
- Pasted private content
- Unmasked screenshots
- Replay capture

User note:
- Describe the step and symptom without pasting raw document text, secrets, files, or restoration material.

Article details

Keeping Your PDFs Private

Imagine you need to share a contract with your solicitor, but it contains your client's Tax File Numbers. Or you have a medical report to send to a specialist, but it is full of personal information. This is where PDF redaction matters.

The Old Way (Risky)

In the past, you would have to:

  • Upload your PDF to a website
  • Trust that website with your sensitive data
  • Hope they deleted it after processing
  • Download the redacted version

Your private information would pass through someone else's servers — servers that could be compromised, logged, or misused.

The Redactorr Way (Safe)

With Redactorr, PDF detection and redaction run in your browser.

Upload Your PDF**

1 / 1

Click "Upload PDF" or drag and drop your file. The file stays in your browser — it is never sent anywhere.

Detection Runs**

1 / 1

Redactorr reads your PDF, extracts the text, and scans for sensitive information. Emails, phone numbers, Tax File Numbers, Medicare numbers, contract values — all flagged for your review. Everything happens in your browser.

Review and Download**

1 / 1

You will see everything detected, highlighted for your review. Confirm what to redact, then download your clean PDF ready to share safely.

What Gets Detected

Redactorr automatically finds:

  • Email addresses ([email protected] → [EMAIL_1])
  • Tax File Numbers (123 456 782 → [TFN_1])
  • Medicare numbers → [MEDICARE_1]
  • Credit card numbers (4532 1234 5678 9012 → [CARD_1])
  • Phone numbers (0412 345 678 → [PHONE_1])
  • API keys and credentials
  • Physical addresses
  • Custom patterns you define

Important Note

Redactorr works best with PDFs that contain selectable text — contracts, reports, letters, forms. Scanned-page, photo, and handwritten-form redaction are active product directions, but they are not broad production support claims until OCR, detection, visual redaction, export, and leakage gates pass.

Still stuck?

Copy a safe article handoff.

Start support with the article, the issue, and safe context. Raw document text, files, restoration material, and unredacted screenshots stay out unless you explicitly choose otherwise.

Support can start here
  • Article slug
  • Selected issue
  • Screen name
  • Action name
Redactorr support case

Source: Article playbook: pdf-redaction
Route: /knowledge-base/pdf-redaction
Selected issue: A supported PDF type fails to preview.

Safe context:
- File type category and rough size band.
- Upload, preview, review, or export step name.
- Error category and browser metadata.
- Article slug
- Selected issue
- Screen name or article section
- Action name
- Browser and viewport

Only include with explicit consent:
- User-written description
- Email address
- Explicit attachment
- Redacted sample
- Support bundle previewed to the user

Do not include by default:
- Raw original document text
- Full local file paths
- Pasted private content
- Unmasked screenshots
- Replay capture
- Hidden diagnostic uploads

User note:
- Describe what you tried and what happened. Do not paste raw document text, secrets, files, restoration material, or unredacted screenshots.

Support case builder

One case format, wherever you start.

This is the same support case shape used by diagnostics and article handoffs.

Safe to include
  • File type category and rough size band.
  • Upload, preview, review, or export step name.
  • Error category and browser metadata.
  • Article slug
  • Selected issue
  • Screen name or article section
Consent boundary

Private material belongs behind an explicit consent step, not in the initial case.

6 default exclusions

Before you copy0/4 ready
Open safe support guide