Private image metadata cleaner

Remove hidden metadata. Keep the photo.

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.

Choose images How it works →

Private image metadata cleaner

Clean image metadata

Inspect what is readable, remove it by local re-encoding, and verify the result.

Choose images

Drop images here

JPEG, PNG, or supported WebP · Up to 20 files

Processed locally in your browserYou can also paste an image from your clipboard.

Processed on your deviceNo account requiredBatch cleaning

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.

How it works

Inspect, rinse, verify.

MetaRinse checks the original, creates a fresh image from decoded pixels on your device, then scans the result with the same metadata reader.

Inspect

See readable GPS, camera, date, creator, description, and software fields grouped in plain language.

Rinse

Your browser decodes the image, draws the pixels to a fresh canvas, and encodes a new file without copying the original metadata.

Verify

The output is scanned again. If readable private or descriptive metadata remains, MetaRinse does not offer that file for download.

What may be detected and removed?

Actual fields vary by image format, device, and editing history. MetaRinse groups differently named fields into useful categories.

GPS location

Latitude, longitude, altitude, and direction

Camera and lens

Make, model, lens, and readable serial identifiers

Date and time

Capture, creation, modification, and timezone values

Creator and rights

Artist, author, copyright, and credit fields

Descriptions

Titles, captions, keywords, comments, and subjects

Editing software

Software, creator tool, and host computer details

Your files stay on your device.

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.

Methodology →Privacy policy →

Supported formats and honest limits

Unsupported formats are never converted silently. WebP is handled only when the current browser can both decode and re-encode it.

Format	Inspect	Clean	Notes
JPEG/JPG	Yes	Yes	Re-encoded; compression and file size may change
PNG	Yes	Yes	Browser encoding and color-profile handling can change bytes or appearance
WebP	Browser-dependent	Browser-dependent	Feature-detected at runtime
HEIC/HEIF	No	No	Not supported in the MVP
GIF	No	No	Rejected to avoid losing animation
RAW/PDF/video	No	No	Out of scope

Frequently asked questions

Does MetaRinse upload my images?

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.

What information can photo metadata contain?

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.

Does cleaning change image quality?

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.

Can MetaRinse guarantee that an image is anonymous?

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.

Does removing metadata change copyright?

No. Removing a copyright field does not change ownership or permission. Only process images that you own or are authorized to edit.

Why did my output file size change?

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.

Which formats are supported?

JPEG and PNG are supported. WebP is supported when the browser can re-encode it. HEIC, GIF, AVIF, TIFF, RAW, PDF, and video are not supported.

Can I use MetaRinse on a phone?

Yes, in current mobile browsers. If several large photos exceed your device memory, process a smaller batch.

Why does MetaRinse re-check the output?

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.

What happens when no metadata is found?

MetaRinse reports that result honestly. You may still re-encode the image, but the file can change without providing a metadata privacy benefit.

Learn to share photos more safely

Understand what metadata is, what it may reveal, and how to check a cleaned result without overestimating the tool.

Browse all guides →

Use it responsibly.