Private Preview
Join Waitlist →

Scanned, Photo, and Handwriting Support

Current support status for scanned pages, document photos, and handwriting

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

Outcome

Recognise scanned, photographed, and handwritten inputs and choose the safest next step without assuming they behave like text-layer documents.

Your progress

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

0 / 3 steps complete

Before you start

Know whether the page is scanned, photographed, handwritten, or a digital document with selectable text.
Keep the original file local unless support explicitly asks for an opt-in attachment.
Use the current support boundary instead of guessing OCR behaviour.

Visual frame

Review asset

Scanned, photo, and handwriting boundary storyboard

Synthetic boundary frame only. It avoids real scans and keeps handwriting framed as a product direction, not a supported promise.

Best pathBorn-digital
PreviewScans/photos
BoundaryHandwriting

Synthetic frame

Document source

Choose the closest source before scanning.

PDF textSelectable
Scanned pagePreview path
HandwritingNot supported
The most reliable workflow starts from extractable text.

Scanned input decision frame

A decision frame for input types that may not contain readable text. It keeps expectations clear before upload.

SelectableUse the standard text-layer workflow.
Scanned/photoUse current support-boundary guidance.
HandwritingDo not assume automatic detection.

Guided steps

Follow the task, then check the result.

Check whether text is selectable

Open the document and try selecting a line of text. If text selection does not work, the file may be a scan or image rather than a text-layer document.

Selectable text check before upload.
Success check: You know whether the document has selectable text.

Choose the current support-boundary path

Treat scans, photos, and handwriting as separate from standard text-layer redaction. Use only the capabilities the product currently supports and do not assume handwritten text will be detected.

Decision split for scanned page, document photo, and handwriting.
Success check: You have routed the document by actual input type, not by filename alone.

Prepare a safe support description if needed

If the behaviour still does not match the guide, describe the input category and step where it failed. Do not attach raw documents unless a consent flow explicitly asks for an optional attachment.

Support description with input category and failed step only.
Success check: Support can understand the category without receiving raw document content by default.

Branch questions

Completion check

You know whether the input is text-layer, scanned, photographed, or handwritten.
You did not assume image or handwriting support behaves like a digital PDF.
Any support description avoids raw document content by default.

Support boundary

Support can use by default

  • Input category such as scanned page, photo, handwriting, or text-layer PDF.
  • Step name where the issue appeared.
  • Optional attachment only after explicit consent.
  • 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/scanned-photo-handwriting-support
Selected issue: A document category behaves differently from the current support-boundary guide.
Playbook progress: 0/3 steps marked complete

Safe context to include:
- Input category such as scanned page, photo, handwriting, or text-layer PDF.
- Step name where the issue appeared.
- Optional attachment only after explicit consent.
- 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

Scanned, Photo, and Handwriting Support

Redactorr is being built to handle more than clean digital files. The product direction includes scanned pages, photos of paper documents, and handwritten forms.

The important distinction is support level. We only call something supported after it has passed the right gates.

What Works Today

Redactorr's launch-safe path is born-digital files where text can be extracted directly:

  • Text-layer PDFs
  • Word documents
  • Spreadsheets
  • CSV and tabular text
  • Plain text and UTF-8 text-like files

For these files, detection and redaction run in your browser.

Scanned Pages and Document Photos

Scanned-page and photo redaction are active product directions.

The app has browser OCR paths for scanned PDFs and direct images, but broad production support is not claimed yet. A scanned document or phone photo can introduce rotation, blur, shadows, perspective distortion, low contrast, and missing text. Those cases need stronger proof before we tell users they can rely on it.

Before scanned pages or photos become fully supported, Redactorr needs to prove:

  • OCR can read the target text
  • Sensitive values are detected from that OCR text
  • Redaction boxes align with the original page or photo
  • Exported files do not leak the original values
  • The workflow performs reliably on real documents, not only synthetic examples

Handwritten Forms and Notes

Handwriting is a separate problem from printed OCR.

Printed OCR can often read typed text in a scan. Handwriting needs handwriting recognition, and messy handwriting can be ambiguous even for people. Redactorr should support handwritten notes and forms eventually, but we will not claim support until a separate handwriting gate exists and passes.

How To Think About It

Use this rule:

  • If your file has selectable text, it is in the launch-safe path.
  • If your file is a scan or photo of printed text, treat it as preview or roadmap until gates pass.
  • If your file is handwritten, treat it as a future capability, not current support.

This protects users from assuming a document is safe when the OCR, redaction overlay, or export proof is not complete yet.

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: scanned-photo-handwriting-support
Route: /knowledge-base/scanned-photo-handwriting-support
Selected issue: A document category behaves differently from the current support-boundary guide.

Safe context:
- Input category such as scanned page, photo, handwriting, or text-layer PDF.
- Step name where the issue appeared.
- Optional attachment only after explicit consent.
- 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
  • Input category such as scanned page, photo, handwriting, or text-layer PDF.
  • Step name where the issue appeared.
  • Optional attachment only after explicit consent.
  • 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