In a world without privacy, we create it.

Veldrinby CounterCustody
Download on the App StoreDownload on the App Store
Scan to download VELDRIN on the App Store.
TL;DRWant the short version? Click here.
The problem
Private files sit in a camera roll anyone can scroll, an album anyone can open, or a cloud you don't control.
The fix
Veldrin keeps them in a pattern-locked vault on your iPhone. No account, no vault list, and a red emergency button for when you're pressed to open it.
In short
Choose a metadata cleaner for EXIF, GPS and C2PA.

Why you need this

A picture can reveal more than the scene you intend to share. Before sending it, check both its visible details and its embedded labels. Testing a cleaner on a harmless copy helps you see what changes, what remains and whether image quality suffers.

Guide · 7 min read

Metadata cleaner apps and C2PA: what removal changes and what it doesn't

A metadata cleaner can remove embedded labels such as GPS coordinates, camera details and a Content Credentials (C2PA) manifest when it supports the file and those fields. Check what the exported copy contains. Removing labels does not make an image untraceable or establish that its subject is genuine.

What a metadata cleaner actually removes

An image file has two parts: the pixels that make the picture, and a wrapper of labels around them. The labels are the metadata. EXIF holds the date, the camera or phone model, exposure settings and often GPS coordinates. XMP and IPTC hold captions, credits, rights notes and the name of the software that touched the file. Many files also carry an embedded thumbnail, which is a small second copy of the picture. A file can also hold a C2PA manifest, the signed provenance record branded as Content Credentials.

A metadata cleaner produces a copy of the file with some or all of those labels left out. That's useful and often exactly what you need before you post a photo taken at home. It's also narrower than the word "clean" suggests, because every label is separate from the picture itself.

Removal at a glance: what changes and what stays

Thing you might want goneDoes a metadata cleaner remove it?Why
GPS location, date, device model, serial numbersYes, when the tool supports those fields and that formatThey are labels in the file wrapper
An embedded C2PA manifestYes, when the tool supports removing that embedded manifestIt is stored in the wrapper, next to the other labels
A credential stored in a manifest repositoryNoIt lives on a server, outside the file you edited
An invisible watermarkNot reliably; a pixel watermark can remainIt is part of the pixels
A visible logo, a face, a street signNoIt is what the picture shows
Permission to reuse the imageNo new permission is grantedFollow the rights holder’s permission and license terms
An embedded provenance recordThat record can be removed from this copyOther records may remain; provenance alone does not prove the scene is true

Two ways cleaners work, and why the difference matters

Some cleaners rewrite the container. They copy the compressed picture data across untouched and leave out the metadata segments, so the pixels stay identical to the original. Other cleaners rebuild the file from pixels: they decode the image, draw it, and encode a fresh file. That route drops every label the tool didn't deliberately copy, but lossy re-encoding, such as lossy JPEG or WebP output, can change the pixels, and color profiles or HDR data can be lost. WebP also supports lossless encoding; the selected format and settings matter.

Metadata removal is not redaction of the scene. A container-only edit can preserve the encoded image data; rebuilding can change pixels, color and quality. Neither is a reliable way to remove an embedded watermark: survival depends on the watermark and the transformation. The photo metadata tool on this site rebuilds the image and scans the result again. Its displayed fields help inspect the copy; they do not prove the absence of every possible metadata type.

How C2PA ties a credential to an image

A C2PA manifest is a signed record of claims about an asset: which tool made or edited it, what actions were taken, and sometimes which ingredients were combined. The specification links the record to the asset in two ways. A hard binding hashes defined protected asset data, with specified exclusions such as the manifest store. Changing covered data invalidates that binding; a change outside the covered data need not do so. A soft binding is an identifier that survives some changes: either a fingerprint computed from the content, or an invisible watermark embedded in it. The Content Credentials explainer covers the manifest itself in more detail.

Durable Content Credentials can reconnect a stripped image

The C2PA specification defines a Durable Content Credential as one with at least one soft binding that lets it be found in a manifest repository. In practice, a publisher can store the manifest on a server as well as in the file, and embed a watermark whose identifier works as a lookup key. If someone strips the manifest out of the file, a reader that detects the watermark can ask the repository for the record again. C2PA also describes a Soft Binding Resolution API so those lookups work the same way across repositories.

Fingerprints can help find a record when there is no usable watermark or embedded manifest, if the reader and repository support that lookup. Because fingerprint algorithms match near-identical images rather than exact bytes, the C2PA guidance recommends presenting any credential found that way with a qualification. For you, the point is simple: deleting the manifest from your copy deletes your copy's label. It doesn't delete a record that someone else stored, and a watermark in the pixels can lead back to it.

Four things metadata removal doesn't do

  • It doesn't hide the scene. Re-encoding can change pixels, but a picture of your street still shows your street. Faces, reflections, house numbers and school logos need separate attention.
  • It doesn't make an image forensically invisible. The picture can still be matched by reverse image search, recognized from a watermark, or compared with a copy that kept its labels. Compression traces and image content remain for anyone who looks.
  • It doesn't grant reuse permission. Removing a credit or rights label is not permission to use someone else's image. Follow the rights holder's permission and license terms.
  • It doesn't authenticate or disprove anything. A file with no credential isn't proven fake, and a file with one isn't proven true. Removing a manifest from an AI image doesn't turn it into a photograph.

When stripping your own metadata makes sense

The ordinary reasons are privacy reasons. A living-room listing photo may carry home coordinates, and a credential may include identifying assertions. Device identifiers, when present, can link images. Decide which details a recipient needs before sharing. Removing embedded metadata removes that copy's labels, not other copies, repository records or visible clues. Keep the original separately when its provenance matters.

How to check a metadata cleaner with a harmless photo

  1. Choose a harmless test photo, such as a mug, whose metadata you can inspect. If testing GPS removal, confirm that the original actually contains coordinates.
  2. Read its metadata in a viewer first and note the location, date and device rows.
  3. Run the photo through the cleaner and save the copy separately. Keep the original.
  4. Open the copy in a different reader and check the specific fields you intend to remove. A missing row means that reader did not report it, not that every possible metadata field is absent.
  5. Compare the two pictures side by side for color shifts, lost transparency or heavy compression.
  6. If the cleaner is a website, decide whether you're comfortable with the file leaving your device before you try a real photo. A browser tab can process a file locally or upload it, and the page should say which.

On an iPhone you can also leave labels out when you share. The share sheet's Options control can turn off Location for that copy, and some versions offer a switch for all photo data. EXIF data on iPhone photos walks through it, and removing location metadata covers other routes.

Questions people ask

Does a metadata cleaner remove C2PA Content Credentials?

A cleaner that supports the file format and C2PA removal can remove an embedded manifest from its output. It does not remove repository copies or guarantee removal of watermarks that may reconnect the image to a record. Inspect the exported file.

What is a C2PA soft binding?

It's a link between a credential and an image that survives some changes to the file: a fingerprint computed from the content, or an invisible watermark embedded in it. A hard binding hashes specified protected data with defined exclusions; changing the covered data invalidates the binding.

Does removing metadata change the photo?

A container-only edit can preserve encoded image data. Rebuilding re-encodes the picture: lossy settings can change pixels, while WebP also supports lossless encoding. Color profiles or HDR data may be lost, so compare the output with the original.

Can a stripped image still be traced?

Yes, in several ways. Reverse image search, an embedded watermark, a fingerprint match against a repository, or the visible content itself can all connect it to its source. Metadata removal only takes away the labels.

Does removing a rights label let me reuse the image?

No. Removing a label does not grant permission to use another person's work. Follow the rights holder's permission and license terms.

How do I know a cleaner really worked?

Inspect a harmless original, clean a copy, then examine the output in another reader. Check the fields you intended to remove and compare image quality. A reader reporting no fields is useful evidence, but not proof that every metadata format is absent.

Sources

VELDRIN

Keep the photos you never send out of the share sheet

See Veldrin on the App Store