Create a clean copy of a JPG, PNG or WebP without common embedded metadata such as camera, software and location details.
No server upload No signup Up to 30 MB per file
Up to 50 files and 250 MiB in total (1 MiB = 1,048,576 bytes). The per-file limit also applies. Large dimensions or limited device memory can cause a smaller job to fail.
Drag files here
You can select multiple files at once.
Choose filesJPG, PNG, WEBP · Up to 30 MB per file
Local browser processing — Source files are not sent to our server for conversion.
JUUD FILE LAB
File choices, tested with real outputs
We made the source files, measured the exported bytes, and published the results so you can check them yourself.
Re-export selected images without carrying common ancillary fields into the new files.
Add one or more supported images.
Read any metadata-presence or colour-profile warning. This screen does not list GPS coordinates, camera models, capture times or individual metadata values.
Create cleaned copies and compare their appearance and file sizes.
Download the new files and verify sensitive results with a separate metadata inspector; keep the originals if you need their embedded records.
02
What metadata means
Image files can contain camera model, capture time, coordinates, editing software, comments and other non-pixel information.
JPG, PNG or WebP with metadata
JPG, PNG, WEBP
→
Re-encoded image with common metadata removed
JPG, PNG, WEBP
The tool removes source metadata by decoding pixels and producing a fresh file; it is not a metadata-only edit of the original bytes.
Original EXIF, XMP, comments and colour profiles are not carried over. The browser may add its own format information, and colour appearance can change.
03
When to clean a photo
Metadata cleanup is useful before distributing images beyond trusted recipients.
Publishing phone or camera photos on a public site.
Sending images where capture location should remain private.
Removing editor and device fields from shared deliverables.
04
Check both appearance and fields
Cleaning uses a fresh export, so compressed formats can change slightly.
Use high JPG quality for important originals.
Do not treat metadata removal as redaction of visible information inside the pixels.
Metadata inspection stays on-device
Files and detected metadata are processed in the current browser only.
No location, camera or file-name fields are sent to analytics.
For highly sensitive work, verify the downloaded file with a separate trusted inspector.
FAQ
Frequently asked questions
Does this remove GPS location?
The cleaned export omits common EXIF fields, including GPS when present in a supported source.
Does it blur visible addresses or faces?
No. It removes embedded data, not details visible in the image itself.
Does the screen show my GPS coordinates or camera model?
No. It can warn that common metadata or a colour profile exists, but it does not display individual values or provide a complete before-and-after metadata audit.
Does no warning mean my file has no metadata?
No. The advisory preflight checks at most the first 1 MiB for metadata markers. Records later in a file may not trigger it. An absent warning is not a privacy certificate; inspect the saved export separately.
Is every possible private field guaranteed to be removed?
No universal privacy guarantee is made. A fresh export omits common source metadata, but visible content, the downloaded filename and browser-generated format fields still need consideration. Verify sensitive files independently.