When Signatures and stamps fails, troubleshoot in order: file/format, permission/lock, output settings, another tool. Black-box signatures/stamps; blur may leave recognizable strokes.
Why it matters
Start with the most common and cheapest causes to narrow it down fast.
Scanned contracts may have signatures on many pages.
Step by step
- Crop unrelated areas first, then redact what must remain.
- Use black boxes for IDs/addresses/QR codes, not just a center blur.
- Cover 2-4px beyond the edges to avoid readable strokes.
- Zoom to 200% after export to check edges/reflections/thumbnails.
- 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
How do I troubleshoot a failed Signatures and stamps task?
When Signatures and stamps fails, troubleshoot in order: file/format, permission/lock, output settings, another tool. 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