Photo privacy walkthrough
Share Photos Without Exposing Private Details
A practical review workflow for the pixels and metadata that a photo can reveal before you share a copy.
Open Photo Privacy ProcessorReview the whole frame before choosing an effect
Inspect a photo at full size before it leaves your device. Names, addresses, email, phone numbers, QR codes, badges, account balances, document numbers, reflections, map labels, notifications, browser tabs and screens in the background can matter as much as a face or a plate.
The self-authored practice photo has several categories at once: an account notification and apparent location in the upper card, an address and QR-like pattern on the parcel, a face, a plate and a house number. Context can also identify someone when combined with information already public.
Choose the treatment from the disclosure risk
Use an opaque solid cover for text, codes, identifiers and other content that must not remain readable. It replaces those pixels in the export. Blur and mosaic are visual effects; they can be useful for lower-risk context, but do not treat either as a guarantee that information cannot be inferred.
Draw a region wider than the sensitive subject. Include nearby edges and leave a margin so an imperfect selection, crop, rotation or later compression does not reveal a fragment.
| What is shown | Recommended treatment | Reason to check |
|---|---|---|
| Address, email, code or account detail | Opaque solid cover | The original pixels must be replaced, including the surrounding margin. |
| Face | Solid cover for high risk; blur only when appropriate | A face can remain recognizable after a weak or small blur. |
| Plate or low-risk context | Mosaic only after visual review | Pixelation can still leave a pattern or partial characters. |
| EXIF, GPS or capture time | Export a new copy | These are not visible pixels and need a separate check. |
Load a copy and inventory what must not leave
Open Photo Privacy Processor and choose the source copy. The tool accepts one JPG, PNG or WebP at a time. Its decode, editing and export happen locally in the browser, so this workflow does not upload the image to MV Tools.
Before drawing, list each visible detail and any metadata you need to remove. The example source intentionally contains test EXIF software, capture-time and GPS tags, alongside the visible delivery card.
Keep the original outside the sharing path.
Use a copied file as the editor input. The original may be needed later for legitimate editing or record keeping.
Scan from corners to background.
Look for small labels, notification text, reflections and map-like context before focusing on the obvious face or plate.
Write down every region to protect.
A checklist prevents one detail being missed after the first obvious mark is applied.
Commit marks and make the high-risk areas opaque
The real run shown here commits four marks: blur over the illustrated face, mosaic over the plate, an opaque cover over the parcel label, and an opaque cover over the delivery notification. The number in the tool rises only after a region has been released and committed.
For a real address, code, account detail or medical information, choose opaque cover and inspect the outer edge. Blur and mosaic in this example demonstrate available tools; their suitability depends on the sensitivity and your disclosure risk.
Export a new file to remove the source metadata
Pixel redaction and metadata removal solve different problems. The source used here contains four kinds of test metadata evidence: an EXIF container, software identifier, capture time and GPS tag entries. After the local PNG export, all four checks are absent from the downloaded output.
The protected PNG is 325 KB, compared with the 143 KB JPG source. Its larger size is expected for this graphical sample and does not make it less private. Choose the output format for the receiving workflow after confirming the pixels and metadata.
Open the exported file and inspect it as a separate artifact
Do not rely only on the on-screen selection outlines. Download or open the output, view it at normal size and zoom in around every marked edge. Check it on the actual sharing destination when practical, because a platform may create another copy or recompress it.
The comparison below uses the same 1400 × 900 image before and after the four committed marks. Verify that covered regions contain no readable fragments, the visible result is acceptable for the intended audience, and the file selected for sharing is the exported copy.
Use the tool within its real limits
Photo Privacy Processor handles one JPG, PNG or WebP image up to 30 MB and 40 megapixels. It supports mosaic, blur, solid cover, rotation, undo and redo, then exports PNG, JPG or WebP. Browser capability can still affect whether a particular image can be decoded.
The tool helps prepare a shareable copy. If disclosure could cause material harm, reduce the information you share, use opaque redaction for sensitive material and have a trusted reviewer inspect the final exported file.
Frequently asked questions
Does blur always hide text or a face safely?
No. For information that must not remain recoverable, use an opaque solid cover with a margin and inspect the exported file at high zoom.
Does removing EXIF also hide what is visible in the image?
No. Metadata and pixels are separate disclosure paths. Remove metadata through a new export and redact visible details separately.
Are my photos uploaded to MV Tools?
No. This tool decodes, edits and exports the selected photo locally in your browser.