How to check and remove photo metadata before a client handoff

1. Inspect what the original contains

Photo metadata can include information that is invisible when you simply look at the picture. Start with the source file’s information view and note the fields that matter to the client: location, capture date and device details.

On iPhone, Apple documents opening a photo or video and swiping up or tapping its Info button to view location information. This is a useful first check, but an app’s information panel does not necessarily expose every metadata format in a file.

Source: Apple: manage location metadata in Photos

2. Agree what should leave the team

A private location may be unnecessary for a social post, while capture dates may help a client organise an archive. Make that decision explicitly. Keep the untouched source in the client’s normal storage and make the delivery copy separately.

If the handoff requires a signed provenance record, do not treat metadata removal as a harmless default. Spoofzy’s Metadata Cleaner removes supported C2PA data. Keep the original and choose a different handoff process when that record must accompany the asset.

Choose the smallest change you need. If you only want to leave out a photo’s location, check your photo app’s sharing controls first. Choose Metadata Cleaner when you want a separately cleaned file and are comfortable removing supported C2PA records too.

Location: does the recipient need the capture coordinates?
Device: is the camera or phone information useful for this delivery?
Date: should the capture timestamp remain in the shared copy?
Provenance: does the client require Content Credentials with the asset?

3. Clean the delivery copy in Telegram

Open Spoofzy and choose Metadata Cleaner. Send a supported photo as a file, then choose which standard GPS, device and date fields to keep or remove. Supported C2PA provenance data is removed as part of the cleanup.

The workflow is designed to preserve the media’s appearance and orientation. It is not a SynthID remover or a visible-watermark editor, and it cannot promise support for every metadata field or file format. Check the current feature page and the bot’s file limits before a large handoff.

Source: Metadata Cleaner: supported files and cleanup options

4. Verify the result you will actually send

Download the returned file rather than judging its chat preview. Open it, compare orientation and appearance with the original, and inspect the metadata fields you intended to remove. If a field remains or a required field is missing, pause the handoff and resolve that specific mismatch.

When you share through another app, check its export options as well. Apple, for example, provides a Location toggle in the Photos share options. Avoid assuming that all apps keep or remove the same information.

Source: Apple: manage location metadata in Photos

How to batch remove metadata from photos

For a set of client photos, agree the same keep/remove choices before uploading. Open Metadata Cleaner and choose Clean a batch, then follow the bot’s prompts to send the supported files. The completed set arrives as one download. Keep the originals outside the delivery folder.

Download and inspect the files that will actually leave the team. Check the requested GPS, device and date fields as well as appearance and orientation. A successful batch download is a delivery result; it does not certify that every possible metadata field has been removed.

Source: Batch photo and video metadata cleanup

5. Leave a short handoff record

A reusable delivery note can be short enough to copy into your existing client record. It should explain what was checked without claiming that every possible trace has been removed.

Source: the filename or internal asset reference.
Delivery copy: the exact file approved for sharing.
Requested changes: GPS removed; device/date kept or removed as agreed.
Verification: relevant fields checked, orientation checked, reviewer and date recorded.
Context: intended destination and any required credit or AI disclosure.