Inspect
See readable GPS, camera, date, creator, description, and software fields grouped in plain language.
Private image metadata cleaner
Inspect and remove GPS location, camera details, timestamps, author fields, and other readable metadata directly in your browser. Your image files never leave your device.
Private image metadata cleaner
Inspect what is readable, remove it by local re-encoding, and verify the result.
JPEG, PNG, WebP, HEIC, or HEIF · Up to 20 files
Metadata fields vary by device, editor, and image format. “No readable metadata found” is not a guarantee that no forensic information exists.
Only process images you own or are authorized to edit. Removing metadata does not change copyright ownership.
Common metadata tasks
Start with the task that matches the file you plan to share.
Check coordinates, clean the file locally, and verify the downloaded copy.
Understand the Exif specification, common fields, and broader image metadata.
Use a step-by-step metadata verification checklist on the actual download.
See how each format stores fields and what browser re-encoding can change.
Image tools
Redact, crop, convert, and compress with the same local-processing privacy principles as the metadata cleaner.
Cover faces, documents, screens, and other details with a solid block, pixelation, or blur.
Start redacting →Choose an area and aspect ratio, preview the result, and download it. HEIC and HEIF input is saved as JPEG.
Start cropping →Convert HEIC, HEIF, JPEG, PNG, and WebP while resizing, applying grayscale, or removing near-white backgrounds.
Start converting →Create JPEG, PNG, and supported WebP files at or below a selected maximum size when the target can be reached.
Start compressing →How it works
MetaRinse checks the original, creates a fresh image from decoded pixels on your device, then scans the result with the same metadata reader.
See readable GPS, camera, date, creator, description, and software fields grouped in plain language.
Your browser decodes the image, draws the pixels to a fresh canvas, and encodes a new file without copying the original metadata.
The output is scanned again. If readable private or descriptive metadata remains, MetaRinse does not offer that file for download.
Actual fields vary by image format, device, and editing history. MetaRinse groups differently named fields into useful categories.
Privacy architecture
Selected images are read with browser File APIs. Previews use temporary local object URLs, and cleaned files and ZIP archives are created in browser memory. MetaRinse does not send image bytes, filenames, metadata values, locations, or previews to a server.
Clear the cleaner or close the page to discard the in-memory working session. Ordinary page requests can still expose standard connection data such as an IP address and user agent to the hosting provider, but never contain your selected image content.
WebP is handled only when the browser can decode and re-encode it. HEIC and HEIF are decoded locally and cleaned to JPEG.
| Format | Inspect | Clean | Notes |
|---|---|---|---|
| JPEG/JPG | O | O | Re-encoded; compression and file size may change |
| PNG | O | O | Browser encoding and color-profile handling can change bytes or appearance |
| WebP | Browser-dependent | Browser-dependent | Feature-detected at runtime |
| HEIC/HEIF | O | O | Decoded locally and saved as JPEG |
| GIF | X | X | Rejected to avoid losing animation |
| RAW/PDF/video | X | X | Out of scope |
No. Selection, inspection, re-encoding, verification, download, and ZIP creation all happen in your browser. Filenames and metadata values are not sent to analytics or processing services.
Depending on the device and workflow, it can include GPS coordinates, camera and lens details, capture times, authorship, copyright, descriptions, keywords, and editing software. Not every image contains the same fields.
PNG is also regenerated through the browser, while JPEG and WebP are re-encoded with lossy compression. MetaRinse preserves displayed orientation, dimensions, and supported transparency, but color profiles, file size, and subtle pixel values can change.
No. It removes metadata that its scanner can read. It does not hide faces, addresses, reflections, documents, or other visible clues, and it does not promise the absence of every forensic trace.
No. Removing a copyright field does not change ownership or permission. Only process images that you own or are authorized to edit.
The browser encoder may use different compression, optimization, and color-profile handling from the original tool. File size alone does not prove cleaning success or image quality.
JPEG and PNG are supported. WebP is supported when the browser can re-encode it. HEIC and HEIF are decoded locally and saved as JPEG. GIF, AVIF, TIFF, RAW, PDF, and video are not supported.
Yes, in current mobile browsers. If several large photos exceed your device memory, process a smaller batch.
It confirms that no readable private or descriptive fields remain in the new file. If they are detected, MetaRinse does not label the result as verified or offer it for download.
MetaRinse reports that result honestly. You may still re-encode the image, but the file can change without providing a metadata privacy benefit.
Understand what metadata is, what it may reveal, and how to check a cleaned result without overestimating the tool.
Understand EXIF and broader image metadata through concrete field examples.
7 min · readInspect location fields, clean locally, and verify the output step by step.
6 min · readAssess location, device, time, and creator information without fearmongering.
8 min · readCompare format differences and the limits of browser re-encoding.
8 min · readLearn why the answer varies and how to test the actual screenshot file.
5 min · readCompare original and output files, then cross-check with another trusted inspector.
6 min · readOnly process images you own or are authorized to edit. Removing metadata does not change copyright ownership.