Review every suggested redaction
QR codes, faces, likely sensitive text, and other OCR lines receive separate switches. Keep only the boxes you want before export.
Visible secretsVisible privacy scan + verified JPG cleaning
Scan screenshots, messaging-app images, and photos for visible QR codes, faces, and sensitive text. Then use this image metadata remover to remove metadata from image JPG files and verify the downloaded copy.
Local pixel scanning · per-finding switches · post-clean verification
Choose a JPG, PNG, or WebP to scan visible pixels. Review a separate switch for every QR code, face, sensitive text line, and other OCR result; for JPG, supported embedded metadata is also removed and the export is read again before download.
Drop a JPG, PNG, or WebP here. Pixel scanning, redaction, and metadata inspection run in this browser.
Drag anywhere on the image to add a manual redaction box. Selected regions appear as solid dark boxes; unselected findings keep an amber outline.
The browser checks the actual pixels for QR codes, faces, and Chinese or English text. Suggested high-risk regions are selected automatically; review every box before export.
No automatic pixel findings yet
Upload an image to scan it. If the scan misses something, drag directly on the image to add a solid manual redaction box.
Automatic detection can miss rotated, tiny, stylized, low-contrast, or partially hidden content. A person must review the full image before sharing.
Each row says detected, not detected, or unreadable for the current format. Not detected does not mean completely anonymous.
The default action removes every supported privacy field. Open advanced settings only if author or copyright information should remain.
The page now checks both layers: information visible in the pixels and supported data attached to the file.
QR codes, faces, likely sensitive text, and other OCR lines receive separate switches. Keep only the boxes you want before export.
Visible secretsDrag on the preview to cover a missed address, plate, username, notification, or background detail with an opaque box.
Selected areaA screenshot may have no camera EXIF, yet visible usernames, notifications, paths, faces, and QR codes can still be detected for review.
Screen privacyUseful privacy cleaning checks both the rendered picture and the hidden fields attached to its file.
The local scan looks for QR codes, faces, and Chinese or English text in screenshots, messaging-app images, social downloads, and camera photos. High-risk findings are suggested, ordinary text stays optional, and manual boxes cover anything detection misses.
For JPG files with no selected visual boxes, the cleaner removes supported metadata segments while copying compressed image data byte-for-byte. If pixels are covered, it clearly reports that the image was re-encoded, then reads the new JPG again to verify supported fields.
This four-step workflow covers screenshots and social images as well as the remove EXIF data and remove GPS from photo use cases.
Upload a JPG, PNG, or WebP—or load the synthetic test image. The browser scans the visible picture while the remove metadata from image inspector reports supported file fields.
Suggested QR codes, faces, and high-risk text start selected. Turn off any item you want to keep, select ordinary OCR text if needed, and drag a manual opaque box over missed details.
The JPG cleaner removes recognized EXIF, GPS, XMP, IPTC, comments, and related supported containers. Author and copyright are removed by default but can be preserved from advanced settings.
Selected pixel regions are written into the export. For JPG, the tool parses the output again after it removes metadata from image bytes. Keep the generic filename option on if the original name identifies a person, client, or project.
Search-informed answers about image metadata remover tools, EXIF, GPS, image quality, filenames, and verification.
Choose a JPG, review the visible scan and metadata rows, leave author and copyright unchecked unless you need them, then select Apply selected privacy protection. This remove metadata from image tool reads the cleaned JPG again and enables download only after supported fields selected for removal are no longer detected.
GPS coordinates are commonly stored in the EXIF GPS directory, so removing the original EXIF block removes those values. This tool also strips supported XMP and IPTC containers because location or place names can appear outside EXIF. Always check the post-clean remaining list instead of assuming one EXIF operation covered every metadata format.
If you remove only metadata, this verified JPG path copies compressed image bytes unchanged, so there is no additional JPEG compression. If you select a visible QR code, face, text line, or manual box, pixels must change and the JPG is re-encoded at high quality; the result states that clearly.
No. The result only confirms that the supported fields selected for removal were not found when the exported JPG was re-read. Unknown application markers, proprietary structures, filesystem dates, cloud records, the filename, and visible content can still identify a person or place.
This page checks for capture time, camera make and model, device serial when readable, GPS coordinates or named place, author, copyright notice, description or title, and editing software. It reads common EXIF/TIFF, XMP, and IPTC representations, while reporting incomplete parsing instead of converting uncertainty into Not detected.
Yes. Open advanced settings before cleaning and select the rights fields to keep. The original metadata containers are removed, then the detected author or copyright value is written into a small XMP rights block. The export is re-read to confirm that the requested rights information survived.
Orientation can be the instruction that makes phone pixels display upright. ICC profiles, EXIF color-space values, and Adobe transform markers can affect color interpretation. The remove metadata from image workflow keeps only the technical information needed for consistent appearance while removing supported privacy fields.
PNG and WebP can use visible QR, face, text, and manual redaction now. Complete embedded-metadata reading and post-export verification are not promised for those formats yet because each needs separate tests for removal, orientation, color, transparency, animation, and previews. The result labels this limitation.
Yes. These everyday images often have little camera EXIF left, so the page also scans actual pixels for QR codes, faces, and Chinese or English text. Likely sensitive regions are selected for you, ordinary OCR text is optional, and you can draw a manual box over anything missed.
It can suggest a face and OCR lines that look like names, addresses, phone numbers, email addresses, or ID numbers, but it does not claim document or plate recognition. Review the entire image and drag a manual opaque box over any ID-card area, plate, barcode, document field, or low-confidence text it misses.
The recognized metadata segments are omitted from the new download rather than hidden inside them, but the original photo is untouched and may still exist in backups, cloud libraries, messages, or device storage. The verification applies only to the downloaded bytes and the fields this tool supports.
A filename such as a person's name, client name, address, case number, or project code can reveal information even when embedded metadata is gone. Keep the generic filename option enabled to download safe-image.jpg, then review the destination folder and sharing service separately.
Use a screenshot, social image, or camera JPG to review QR codes, faces, sensitive text, and manual regions in one place.
For JPG, remove supported EXIF and GPS data and let the tool read the export again before download.
No supported metadata detected does not mean completely anonymous.