Last reviewed: September 6, 2026
Automatic face detection can save time when a photo contains several people. It is still only a suggestion: a face can be small, turned away, partly hidden, near an image edge, or confused with a non-face object. A safe workflow always includes a human review before the image leaves your device.
PrivaCanvas finds likely face regions locally in your browser. It does not identify people, compare faces to a database, or scan the rest of the image for text, credentials, addresses, or other private details.
For a face in an ordinary group photo, Blur or Pixelate can preserve enough visual context while reducing recognition. For exact secrets such as a password, API key, account number, address, or ID number, use Blackout with some padding around the content.
The exported file is flattened into a new PNG, so the drawn masks are rendered into its pixels. This is still not a guarantee that an image is anonymous: review the result in the context where it will be posted or sent. For a detailed comparison, see blur, pixelate, and blackout.
Reviewing the image only on the editing canvas is not enough. The actual file you attach may be the original, a different version, or a screenshot of the editor. Reopening the downloaded PNG gives you one last chance to confirm that every mask is present and that you selected the correct file.
If you are sharing a screenshot, also use the screenshot redaction checklist. It covers browser tabs, notifications, file paths, API keys, and other details that automatic face detection cannot find.
No. It only suggests likely face regions for manual review. PrivaCanvas does not perform identity matching or age, emotion, or other trait inference.
No. Text and other private details need manual masks. Use blackout for exact secrets, and rotate a credential if it may already have been exposed.
No. Image decoding, face detection, editing, and export run in the browser. PrivaCanvas does not have an image-upload endpoint for this editor.