Image Metadata Remover
Remove metadata from your photos and batches in your browser. See what will be removed, keep copyright when you need it, and re-check every cleaned copy before downloading.
Choose images, or drop files or a folder.
- Runs in your browser
- No account
- Originals never overwritten
- ZIP for batches
JPG, PNG, WebP, GIF, HEIC or AVIF
HEIC and AVIF are converted only after you approve the output format and quality. Nothing is removed or converted before that confirmation.
Remove image metadata without uploading your photos
Photos can carry GPS coordinates, camera and lens details, capture dates, author names, copyright notices, edit history and app-added text chunks. This tool reads those fields in your browser and writes a cleaned copy when you confirm.
Inspection, cleaning and verification run on your device; image bytes are not sent to our servers. This page loads its own page assets and anonymous product statistics. It does not load session replay or advertising scripts, and the statistics never include file names, paths, GPS values, author names or metadata values. This is local processing, not an offline website.
Clean metadata from one image or a batch
Add one file, several files or a folder in the same place. The workspace adapts: a single image opens its detail view, while multiple files appear as a queue with per-file status. There is no separate single or batch mode to choose first.
Supported input and export matrix
| Input | Container metadata inspection | Keep format without re-encoding | Explicit conversion | Important distinction |
|---|---|---|---|---|
| JPG / JPEG | Supported recognized fields | JPEG | JPEG, PNG, WebP (re-encoded) | Native cleaning preserves encoded image data and necessary display information. |
| PNG / APNG | Supported recognized fields, including accepted bit depths and animation | PNG/APNG | JPEG, PNG, WebP (re-encoded; static images only) | Animation, transparency and frame timing have separate checks. |
| WebP | Supported recognized fields, including accepted animation | WebP | JPEG, PNG, WebP (re-encoded; static images only) | Alpha and animation must not be silently flattened. |
| GIF | Comment and recognized application metadata | GIF with frames and loop settings | Not offered in this release | The metadata route keeps frames and loop settings; GIF conversion is not offered. |
| HEIC / HEIF | Supported container fields; separate from pixel decoding | Not offered in this release | JPG, PNG or WebP after approval and decoder readiness | Input inspection is not original-HEIC export. |
| AVIF | Supported container fields; separate from pixel decoding | Not offered in this release | JPG, PNG or WebP after approval and decoder readiness | AVIF encoding output is not offered in this release; a converted copy is not the unchanged original container. |
Inspection, preview and conversion are separate. Container inspection and an accepted original-format route use the format parser. Pixel preview and conversion require a decoder. A missing decoder does not disable an independently available container route.
Batch conversion settings
When HEIC or AVIF files are added, each row shows a neutral status: Ready to convert · Will save as JPG. Nothing has failed.
Common opaque photos start at JPG quality 90; images with transparency start as PNG so the alpha channel is preserved. The JPG quality value is configured for this build and shown in the batch bar. Only JPG, PNG and WebP are offered as outputs.
The first time you choose Clean, one confirmation covers the whole batch: how many files will be converted, the output format and the quality change. The main button reads Convert and clean, followed by the number of files. There is no extra mandatory checkbox. You can adjust one file’s target inside Change. The confirmation is tied to this batch of files and these settings; adding a file or changing the settings asks you to confirm the unconfirmed part again. Cancelling creates no result and is not counted as a processing failure, and files that can be cleaned in their original format remain available.
Only a genuinely corrupt or failed file turns red and says Failed. Successfully cleaned items stay downloadable, and you can retry just the failed ones.
Limits
Limits are shown in one line in the workspace: up to 100 files per standard batch, 50 MB per file, and a pixel budget shown before processing. Larger batches are grouped by resource budget rather than silently dropping files.
Cleaning strategy
Every strategy writes a new file; the source is not modified. After cleaning, the copy is re-read and checked; failed items are listed and excluded from the ZIP.
Recommended clean (default)
Remove GPS, device identifiers and serials, capture and edit timestamps, author names, copyright notices, comments, XMP history and IPTC contact fields; keep display orientation (minimal rewrite), ICC, alpha and structure. The workspace shows Recommended clean · Change.
Keep copyright and credit
Remove location, device, date and comment fields; keep author/creator names, Copyright, Rights and Credit. Choose categories can retain them individually.
Choose categories
Select from detected field groups only; the review states each consequence. Unknown or unparsed structures are reported and are never claimed as removed.
Before and after — synthetic example
Synthetic example — not a test result.
| Field | Before | After (Recommended clean) |
|---|---|---|
| GPS latitude / longitude | 0.0000, 0.0000 | Removed |
| Make / Model / Serial | ExampleCam / Model X / 0000000 | Removed |
| Date taken / software | 2024:05:12 10:31:02 / Editor 9.1 | Removed |
| Artist / Copyright | A. Example / © A. Example | Removed by default; kept with Keep copyright |
| XMP history / creator tool | Two edit events | Removed |
| PNG text (Description, Comment) | Present | Removed |
| Orientation | 6 | Kept as a minimal tag |
| ICC profile | Display P3 | Kept unchanged |
| C2PA / JUMBF container | Present | Removed when supported; verification not run |
What is supported, removed and kept
| Item | Action | Detail |
|---|---|---|
| EXIF GPS, altitude, direction | Removed | Location and GPS time. |
| EXIF camera, lens, serial, owner | Removed | Private by default. |
| EXIF capture, edit and file dates | Removed | Offsets removed too. |
| EXIF Artist, Copyright, UserComment | Removed by default | Author and copyright kept together with Keep copyright. |
| XMP packets and edit history | Removed where supported | Unsupported structures reported. |
| IPTC contact, credit, caption | Removed by default | Copyright and credit optional. |
| JPEG comments, PNG text and time chunks | Removed | Per format contract. |
| Embedded EXIF thumbnail | Removed | May hold a second copy. |
| Orientation | Kept as a minimal tag | Upright display only. |
| ICC profile, alpha, color data | Kept | Color and transparency. |
| Pixel payload in original-format cleaning | Preserved without re-encoding | Conversion only with consent. |
| Animation, frame timing and loop count | Preserved on the original-format route | Conversion is for static images; animation is never silently flattened. |
| C2PA / JUMBF credentials | Detected; container removed when supported | No signature or trust check. |
| Visible watermark or logo | Not handled | Use the image watermark remover. |
| Invisible watermark or platform AI label | Not detected or removed | No claim about SynthID or AI origin. |
| Unknown or unparsed structures | Reported, not removed | Never shown as cleaned; Choose categories cannot select them. |
Copyright and creator values are treated as one group across EXIF, XMP and IPTC: removed by default and retained together with Keep copyright.
How to remove metadata from an image in 3 steps
Add the image or batch, review the detected fields and the conversion setting if HEIC/AVIF is present, then confirm once, clean, verify and download the new copies. The original files are not overwritten.
1
Add your image.
Drop a JPG, PNG, WebP, GIF, HEIC or AVIF file, or open a batch folder. The workspace shows the format and any applicable limit.
2
Review and confirm what to keep.
Check the field list and the strategy. If HEIC or AVIF files are included, review the batch conversion setting. One confirmation covers the batch; nothing is removed or converted before it.
3
Clean, verify and download.
The tool re-reads each copy, reports failed checks, and offers files individually or as a ZIP. Your originals stay untouched.
Metadata, AI metadata, watermarks and platform labels
Image metadata
EXIF, XMP, IPTC, JPEG comments and PNG text chunks sit beside the pixels and can contain GPS, device details, dates, authorship and edit history. Removing them changes the descriptive layer, not the picture.
AI metadata
AI image tools may write parameters into PNG text chunks, XMP properties or a C2PA container. This tool removes the supported structures it can inspect, but it cannot determine whether an image was AI-generated. A cleaned file is not proof of human authorship, and a missing field does not mean the image is not AI-generated.
Visible watermark
A logo, handle or text overlay rendered into the image. Metadata removal cannot erase it; use a purpose-built image watermark remover.
Invisible watermark
A signal embedded in the image data or added during generation or distribution. This tool does not detect or remove it and does not claim a cleaned image is free of it.
Platform AI label
A label applied by the platform hosting or displaying the image. It is not a field in your file, so editing metadata cannot remove it. Nor is metadata removal proof that an image was not AI-generated.
Formats, conversion and quality
JPG, PNG, WebP and GIF use an original-format route that removes recognized metadata without re-encoding image data. Necessary orientation, color, transparency and animation information is retained according to the format contract.
HEIC and AVIF use explicit conversion in this release. Choose an output — JPG, PNG or WebP — before conversion; an image is never silently converted because original-format cleaning is unavailable. Original-container HEIC/AVIF writing and AVIF encoding output are not offered here.
Conversion can change file size, color space, bit depth and quality. JPEG is lossy; PNG can preserve the decoded pixels but does not preserve every source-container or HDR property. Re-encoding to the same extension is still conversion. The workspace shows the chosen route and output settings before processing.
Pixel preview and conversion require an available decoder. Container metadata inspection does not. If a decoder is unavailable, the tool explains the affected actions and leaves any independently supported inspection or original-format cleaning available.
Privacy and performance
Files are processed in your browser; image bytes are not uploaded for inspection, cleaning or verification, and no account is required. This page is isolated from session replay, advertising and third-party analytics scripts. It loads its own page assets and anonymous product statistics that record only a fixed list of product events — page open, files selected, preflight result, conversion prompt and decision, clean start, clean finish, download click and related-tool click. Those events exclude file names, paths, hashes, GPS values, author names and metadata values. Statistical failure never blocks cleaning or downloading.
Container operations use limited concurrency to keep the page responsive. Pixel decoding and conversion run one at a time. The exact concurrency level is configured for this build. Large images or folders can still use significant memory and may be refused by the displayed limit. A download click is not proof of a saved file — the browser controls the final location.
Technical details
- A single local worker handles original-format work; heavy decoding runs separately and can be stopped.
- Batch ZIPs are written as grouped Blobs within a memory budget, so every successful file remains downloadable. Streaming disk write is not offered in this release.
- Offline use is limited to original-format cleaning in the current session after all required modules have loaded. Preview and conversion may still need network access to load a decoder. A closed page is not guaranteed to reopen offline; no service worker is provided.
- The tool reads container structures and writes a new copy. Verification re-reads that copy; it does not prove anonymity, authenticity or AI origin.
Frequently asked questions
Short answers about local processing, supported formats, what can be kept and what happens when a file fails.
Does this tool upload my images?
No. Inspection, cleaning and verification run in your browser; image bytes are not sent to our servers. Page assets and the anonymous product statistics described above may use the network, and those statistics contain no file content or metadata values.
Which image formats can I use?
JPG, PNG, WebP and GIF have original-format metadata cleaning. HEIC and AVIF can be inspected and explicitly converted to JPG, PNG or WebP after a decoder is ready; original-HEIC/AVIF cleaning and AVIF encoding output are not offered in this release. Input support never means that every export route is available.
What metadata can be removed?
Supported EXIF, XMP, IPTC, JPEG comment and PNG text/time fields: GPS, device details, dates, author, copyright, comments and edit history. Unsupported structures are reported, not hidden; Choose categories only offers detected groups.
Why keep orientation and the ICC profile?
Orientation keeps the photo upright without the rest of EXIF; ICC keeps colors consistent across viewers. Removing either can make a correctly cleaned copy look wrong.
Can I keep the copyright notice?
Yes. Keep copyright and credit removes location, device, date and comment fields while retaining author/creator names, Copyright, Rights and Credit. Choose categories can also retain them individually.
Can it remove Content Credentials (C2PA)?
When a supported C2PA/JUMBF container is detected, the cleaning step can remove it from the exported copy. Signatures, certificate trust and manifest claims are not verified — the report says “verification not run”. Removal does not make an image authentic or AI-free, and some platforms may expect provenance data.
Does removing metadata remove a visible watermark?
No. A visible watermark is part of the picture; metadata removal changes only the descriptive layer. Use the image watermark remover for marks in the pixels.
Does it remove invisible watermarks or AI labels?
No claim is made. Invisible watermarks and platform AI labels are outside supported behavior, and a cleaned file is not evidence that an image is human-made. AI-written parameters may be removed when they are in a supported structure, but the tool cannot determine how an image was created.
What if no metadata is found?
The file may already be clean, come from an app that strips metadata, or use a structure the tool cannot inspect. “No fields found” is not proof that an image is original, private or AI-free.
Does it work with batches, folders and HEIC files?
Yes. Add many files or a folder to the same workspace. For HEIC or AVIF, the batch bar shows the output format and quality; one confirmation converts and cleans the whole batch. Failed items are listed with a reason and excluded from the ZIP.
Does cleaning change image quality?
The original-format route keeps encoded image data and the display information listed for that format. Conversion re-encodes the image and can change color, bit depth, size or quality. The selected route, output format and quality setting are shown before you confirm; the JPG quality value is configured for this build and is not a guarantee of any particular file size.
What happens to corrupt, unsupported or oversized files?
The file is refused or skipped with a specific reason; it is never silently downscaled or replaced, and never reported as a successful clean. Switching output settings or adding files asks for a new confirmation only for the parts that changed.
How this tool is tested
Before release, every supported format is checked against fixed fixtures: baseline and progressive JPG, PNG across accepted bit depths and animation, WebP, GIF, HEIC and AVIF, a no-metadata file, a corrupt file, an oversized file and a C2PA sample. Each cleaned copy is compared for field presence, dimensions, display orientation, alpha, ICC, size and verification report. Independent reference tools check the same properties where they apply. Conversion quality is reviewed separately from original-format cleaning.
Repeat timing runs are limited to at most three named scenarios used before any future speed or memory claim. Results are published only with the browser versions, devices and dates actually tested, and are not a ranking until the comparison conditions match.