Image Metadata Stripper

Introduction:

A photo, screenshot, scan, or design export is more than the pixels a person can see. Image files can also carry metadata: camera settings, capture time, software names, comments, color information, thumbnails, captions, rights fields, editing history, and sometimes location clues. Those details are useful inside a controlled photo library or publishing workflow, but they can become unwanted baggage when an image is attached to a message, uploaded to a listing, shared in a support ticket, or included in a public report.

Metadata cleanup is not the same as image editing. Removing hidden fields can reduce accidental disclosure, yet it cannot blur a face, hide a document number, erase a reflection, or remove a recognizable landmark from the visible picture. A careful sharing workflow checks both parts of the file: hidden data around the pixels and private information inside the pixels themselves.

Fresh exports can also change image behavior. JPEG cannot preserve transparency, so transparent pixels need a background color. JPEG and WebP quality settings affect compression and visible artifacts. Some animated inputs become a single still image when decoded and exported through a browser canvas. Orientation tags can make a phone photo appear upright in normal viewers, so orientation handling should be checked before sharing the clean copy.

Metadata should be preserved when provenance matters. Legal evidence, journalistic originals, asset archives, and forensic handoffs may need the untouched file with its original timestamps, camera settings, captions, and editing history. Share a cleaned copy when privacy matters, but keep the original separately when authenticity or later investigation might matter.

How to Use This Tool:

Load one image, choose how the clean copy should be encoded, then review the clean preview and metadata findings before downloading.

1. Drop, paste, or choose Browse image for one file in Source image. JPEG, PNG, WebP, GIF, AVIF, BMP, and other image types your browser can decode are accepted.
2. If more than one file is selected, read the ignored-file notice. The page processes the first image only so all findings and receipts stay tied to one source.
3. Choose Clean output format. Auto (keep source) keeps JPEG, PNG, or WebP when possible and falls back to JPEG for other decoded images.
4. Set Quality for JPEG or WebP output. The slider is clamped from 45% to 100%; PNG output ignores it because the export is lossless from the decoded pixels.
5. For JPEG output, set Transparency background before judging edges or transparent areas. JPEG has no alpha channel, so transparent pixels are flattened onto that color.
6. Leave Apply source orientation enabled for most phone photos. Turn it off only when you intentionally want the encoded orientation rather than the viewer-corrected orientation.
7. Check Clean Image, Metadata Findings, Cleanup Receipt, and Size Cleanup Chart. If an error appears, use an image under 40 MB, reduce very large pixel dimensions, or choose a format your browser can decode.

Download the clean image only after the preview looks right and the findings show no remaining privacy-like markers in the clean output.

Interpreting Results:

Output privacy clean means the clean copy was scanned and no common privacy-bearing metadata markers were found. It is a practical browser-side check, not a promise that every metadata parser, forensic tool, or unusual file structure would report nothing.

• Sensitive metadata blocks covers common EXIF, XMP, IPTC, text, comment, and similar markers that can carry names, locations, captions, software history, or workflow notes.
• GPS hint is a text clue from marker labels and sampled metadata text. It can catch obvious GPS, latitude, longitude, geotag, or location wording, but it is not a full coordinate parser.
• Technical markers covers color profile, density, gamma, animation, and encoder structure data. These are separated because a clean export can legitimately contain display metadata.
• Container shows whether the source and output had a direct scan path. JPEG, PNG, WebP, and GIF receive direct scans; other decoded formats receive a limited signature scan.
• Size Cleanup Chart compares source size, clean output size, and privacy marker counts. A larger clean file usually reflects format and quality choices, not failed metadata removal.

For sensitive publishing, verify the downloaded copy with an independent metadata viewer and inspect the visible pixels separately. Hidden-data cleanup cannot remove information that is plainly visible in the image.

Technical Details:

Raster image formats store pixel data inside a container. The same container may hold metadata blocks before, after, or around the compressed image payload. A reliable cleanup copy avoids reusing the old container: it decodes the visible pixels, draws them into a canvas, then encodes a new JPEG, PNG, or WebP file from those pixels.

That fresh-export method is good for common sharing privacy because old EXIF, XMP, IPTC, text, and comment blocks are not copied forward. The tradeoff is that browser encoding can write new technical markers, choose a different compression shape, flatten transparency for JPEG, apply or ignore orientation depending on the setting, and reduce animated input to one decoded still frame.

Transformation Core:

source image bytes
  -> scan common metadata markers
  -> decode visible pixels
  -> apply source orientation when selected
  -> draw one still image
  -> encode a fresh JPEG, PNG, or WebP copy
  -> scan the clean output
  -> report findings, receipt details, warnings, chart values, and JSON

Formula Core:

The size change percentage compares clean output bytes with source bytes:

A 4.0 MB source that becomes a 3.2 MB clean copy reports -20.0%. A 4.0 MB source that becomes a 4.8 MB clean copy reports +20.0%, which usually points to re-encoding choices rather than remaining hidden metadata.

Privacy Notes:

The selected image is scanned, decoded, re-encoded, previewed, and exported in the current browser session without a server upload. That local workflow is useful for private photos, screenshots, scanned forms, and design drafts, but it is not a complete publishing review.

• Keep the original file when provenance, camera settings, capture time, or chain-of-custody information may be needed later.
• Redact visible private details separately. Metadata cleanup cannot hide faces, badges, documents, screens, reflections, street signs, or landmarks.
• For high-risk release work, compare the downloaded copy with a trusted desktop metadata parser before sharing outside your controlled workflow.

Advanced Tips:

• Use Auto (keep source) when you want a normal clean copy without changing JPEG, PNG, or WebP containers unnecessarily.
• Choose PNG when transparency matters. Choose JPEG only after setting Transparency background to a color that matches the destination.
• Keep Quality around 88-94 for JPEG or WebP sharing, then inspect the preview for artifacts around text, faces, and sharp edges.
• Read Technical markers separately from privacy findings. Fresh encoders may write density, profile, or format markers even after privacy blocks are removed.
• Use the Cleanup Receipt and JSON record when you need to document file size, output format, quality, orientation behavior, and warnings for a handoff.

Worked Examples:

FAQ:

Glossary:

EXIF

Camera and phone metadata that can include capture settings, timestamps, orientation, thumbnails, and GPS-related tags.

XMP

An extensible metadata format used for creator, rights, workflow, editing, annotation, and descriptive information.

IPTC

Photo metadata used in editorial, archive, and publishing workflows for captions, creator information, rights, keywords, and descriptions.

GPS hint

A clue that sampled metadata text includes GPS, latitude, longitude, geotag, or location wording.

Alpha channel

Transparency data in formats such as PNG or WebP. JPEG output cannot preserve it.

Technical marker

Format, color, density, animation, or display data tracked separately from privacy-bearing metadata.

References:

• About Exif 3.0, Camera & Imaging Products Association, December 2023.
• IPTC Photo Metadata Standard 2025.1, IPTC, 16 October 2025.
• XMP standards, Adobe.
• Portable Network Graphics (PNG) Specification (Third Edition), W3C, 24 June 2025.
• HTMLCanvasElement: toBlob() method, MDN Web Docs, 12 February 2026.
• Window: createImageBitmap() method, MDN Web Docs, 23 June 2025.