Home/Answers/Signatures and stamps
REDACT LAB / Signatures and stamps

Signatures and stamps Requirements

Handling Signatures and stamps needs a supported browser/app, enough disk/memory and a valid input file.

Updated 2026-10-31About 3 minLocal test
Quick answer

Handling Signatures and stamps needs a supported browser/app, enough disk/memory and a valid input file. Black-box signatures/stamps; blur may leave recognizable strokes.

Why it matters

Missing any condition can turn an environment issue into a false file-corruption diagnosis.

Scanned contracts may have signatures on many pages.

Step by step

  1. Crop unrelated areas first, then redact what must remain.
  2. Use black boxes for IDs/addresses/QR codes, not just a center blur.
  3. Cover 2-4px beyond the edges to avoid readable strokes.
  4. Zoom to 200% after export to check edges/reflections/thumbnails.
  5. Confirm the original is not sent along.

Common mistakes

  • Blurring only the text center, leaving readable edges.
  • Using weak pixelation that can still be inferred.
  • Missing thumbnails/backgrounds/reflections.
  • Sending the original along.

Checklist

  • Unrelated areas cropped.
  • Sensitive areas covered with black boxes/strong blur.
  • Edges over-covered; checked at 200%.
  • Original not sent.
  • EXIF/GPS removed if needed.

Key facts

  • Scanned contracts may have signatures on many pages.
  • Cover stamp edges too.

FAQ

What do I need to handle Signatures and stamps?

Handling Signatures and stamps needs a supported browser/app, enough disk/memory and a valid input file. Black-box signatures/stamps; blur may leave recognizable strokes.

How long does it take?

Usually 1-3 minutes; for intermittent issues, run 30 seconds and retest elsewhere.

Is data uploaded?

Runs locally and does not upload video/audio; extensions may still read the page.

Source: FTC privacy