A photo can reveal more than its visible pixels. Depending on the file and the device that created it, hidden metadata may include GPS location, capture time, camera or phone model, editing software, comments, copyright fields, and an embedded preview. Removing those details before sharing an original file is a practical privacy step, especially for photos taken at home, at work, or around children.
This guide explains how to inspect and clean JPG, PNG, and static WebP images with Purgebg's browser-local metadata tool. It also explains the limits: removing metadata does not blur a visible address, erase a face, remove a watermark, or make an unsafe photo safe to publish. You still need to inspect what is visible in the image.
What image metadata can reveal
EXIF is the best-known metadata format in photographs. A phone or camera may use it to store technical details such as exposure, focal length, orientation, capture time, device make and model, and sometimes GPS coordinates. A coordinate can identify a home, school, workplace, or travel location much more precisely than the visible scene suggests.
EXIF is not the only source. XMP and IPTC fields can contain descriptions, creator details, keywords, workflow notes, and editing history. JPEG comments and embedded thumbnails can preserve information that is not obvious in the main image. PNG files may contain textual chunks, while WebP files can carry EXIF and XMP blocks. Changing the filename does not remove any of these structures.
Not every image contains private data, and not every platform handles uploads the same way. Some social services re-encode photos and discard many fields; email, cloud storage, messaging attachments, portfolio downloads, and shared original files may preserve more. The safest workflow is to clean the copy you intend to share rather than assume a recipient or platform will do it for you.
How to remove EXIF and GPS metadata locally
- Open the Purgebg Image Metadata Remover. The tool accepts one JPG, PNG, or static WebP image up to 25 MB.
- Choose a copy of the image. Purgebg reads it inside the browser; the selected image and its metadata are not uploaded to a Purgebg image processing server.
- Review the categories found. The interface reports privacy-relevant categories without displaying exact GPS coordinates or other sensitive values on screen.
- Select the cleaning action, wait for verification, and download the cleaned copy. Keep the original separately in case you later need its capture information.
- Reopen the downloaded copy in the tool or another metadata inspector. Confirm that the privacy-bearing categories are gone and that the visible orientation, dimensions, transparency, and color still meet your needs.
The tool does not require a Purgebg account or consume a credit. That is different from the Fast and Fine background-removal workflows: metadata cleaning is a separate local privacy utility and does not alter the visible subject or background.
What Purgebg removes from JPG, PNG, and WebP
| Format | Privacy data checked | Important behavior |
|---|---|---|
| JPG / JPEG | EXIF, GPS, XMP, IPTC, comments, thumbnails | Encoded pixels normally remain unchanged |
| PNG | Privacy-bearing text and metadata chunks | Transparency and required image data remain |
| Static WebP | EXIF and XMP metadata | Animated WebP is outside the current scope |
This table describes the current Purgebg implementation, checked on September 17, 2026. It is not a promise that every possible proprietary block will be removed. Unknown application data is preserved unless it is explicitly recognized as safe to discard. That conservative approach reduces the risk of corrupting an image or removing unsupported provenance information.
Will metadata removal reduce image quality?
In most supported files, Purgebg can remove metadata without decoding and recompressing the main image pixels. In that normal path, visual quality and dimensions remain unchanged even though the file size may shift slightly because metadata blocks have been removed.
EXIF Orientation is the important exception. Some cameras store the pixels sideways and rely on an orientation tag to tell software how to display them. Simply deleting that tag would make the cleaned photo look rotated. When correction is required, the tool re-encodes the image in its visible orientation. Re-encoding can slightly change compression, file size, or pixel-level values, so compare the downloaded copy with the original before deleting anything.
A rotated file containing unsupported provenance credentials is not cleaned by this version. Correcting its orientation could invalidate or discard those credentials, and silently doing so would be misleading. The tool prefers an explicit limitation over producing a file whose provenance state is unclear.
What the tool deliberately does not remove
Visible content is not metadata. A house number, license plate, computer screen, reflection, badge, signature, face, or location landmark remains in the pixels. Crop or blur those details with an appropriate editor before sharing. The metadata remover also does not remove visible logos or watermarks and should not be used to bypass ownership information.
Purgebg does not remove C2PA manifests or other unsupported content credentials. C2PA is designed to carry provenance and editing assertions, and treating it like an ordinary comment block could break the trust chain. If a downstream service has a specific content-credentials policy, review that policy and use software that explicitly supports the required provenance workflow.
Cleaning metadata also cannot revoke a copy already sent, remove data held by a platform, or prevent someone from inferring a location from the scene. It reduces information attached to the new file; it does not erase every privacy risk surrounding the original photograph.
A practical before-and-after verification
Use a non-sensitive test file before relying on any cleaner. For JPEG, choose a phone photo that contains capture details and, if safe, location metadata. For PNG, use a file exported by an editor with a description or software field. For static WebP, use a converted copy that retains EXIF or XMP. Never publish the sensitive original merely to demonstrate that it contains private information.
Record categories rather than the sensitive values themselves. A useful test sheet has four columns: format, category detected before cleaning, category detected after cleaning, and visual/output checks. The expected result is that supported privacy categories disappear while the image still opens with the correct orientation, dimensions, transparency, and appearance. If a category remains, do not claim the file is clean.
Run the cleaned download through a second inspector when the risk is meaningful. Independent verification protects against parser differences and unusual files. Keep both tools current and remember that a scanner can report harmless technical structure alongside privacy-bearing data; the goal is to understand what remains, not merely obtain a green badge.
Photo privacy checklist before sharing
- Work from a copy and preserve the original privately.
- Remove supported EXIF, GPS, XMP, IPTC, comments, and thumbnails.
- Confirm that the downloaded file opens in the correct orientation.
- Inspect visible addresses, plates, faces, screens, and reflections.
- Check the background for documents, badges, maps, or location clues.
- Verify the cleaned file with a second inspector when necessary.
- Share only with the audience and permissions you intend.
- Keep provenance credentials when your workflow requires them.
Metadata cleaning is most useful as one step in this checklist. It is fast, repeatable, and reduces accidental disclosure, but the final decision still belongs to the person who can see the image and understand its context.
Clean a copy before you share it
Open the free Image Metadata Remover to inspect and clean one JPG, PNG, or static WebP file locally. If the privacy problem is visible in the pixels rather than hidden in metadata, use an appropriate editor first. If you also need to isolate the subject, the background remover can create a transparent or solid-color result in a separate workflow.
Product behavior was verified against the Purgebg metadata-removal implementation on September 17, 2026. Retest after supported formats, provenance handling, or browser processing changes.