Guide
What photo metadata can reveal.
Metadata can make a file easier to organize, display, edit, and verify. The same context can reveal more than you intended when the file leaves your device.
Remove private clues, preserve the picture.
Standard cleanup removes supported EXIF/GPS, non-appearance XMP, IPTC, comments, and safe text or time data. Encoded pixels and frames are not re-encoded.
Opens the free tool. Your selected files stay in this browser.
Beyond the pixels
What photo metadata can reveal.
Location, capture time, device details, author fields, captions, and editing history can add context you did not intend to share.
-
01
What a photo can reveal
Location, capture time, device details, author fields, captions, and editing history can add context you did not intend to share.
GPS coordinates and place names · Camera, phone, lens, and software details · Dates, creator fields, captions, and comments
-
02
What the file says about its origin
XMP fields and identified C2PA containers can carry editing or provenance assertions. They are useful clues, not a verdict about authenticity.
Recognized C2PA or Content Credentials containers · AI- or editing-related labels present in supported metadata · Software and workflow history recorded by the file
-
03
What should usually stay
Orientation, color profiles, animation controls, secondary images, HDR data, and unfamiliar rendering structures can affect appearance or compatibility.
Dimensions, encoding, and animation · ICC color and minimal orientation data · Unknown or appearance-critical structures preserved conservatively
Real-life uses
Practical ways to use Remove Photo Metadata & AI Content Credentials
These examples show where the tool can help and what still needs a deliberate human check before the result is used or shared.
Posting photos from home
Remove GPS coordinates, capture time, and device details before a photo of a pet, room, garden, or delivery is posted publicly.
Sending images to buyers or clients
Inspect product, property, and project photos for author fields, captions, editing history, and location data before delivery.
Sharing AI-edited images
Review identified provenance data separately so you can make an intentional choice about privacy without assuming that removing metadata proves how an image was made.
Worked example
Sharing a photo taken at home
The picture itself is safe to share, but its file metadata may contain precise coordinates, the capture time, and the phone model.
Before
The original file carries extra context
- The visible image is the content the recipient needs
- GPS, device, date, author, or editing fields may reveal private context
After
The shared copy keeps the picture
- Inspect the findings and choose the supported metadata to remove
- Save a new verified copy and keep the untouched original private
What you receive: a locally created copy whose selected recognized metadata has been removed and rescanned, plus a receipt describing what was changed or preserved.
Four local steps
How to inspect and clean a photo.
- 01
Choose photos
Select one supported photo, choose a folder for batch cleanup, or open the built-in demonstration. Every selected file is read on this device.
- 02
Review the findings
For one photo, review the detailed privacy and provenance findings. For a folder, review aggregate counts, skipped files, and inspection failures before cleaning.
- 03
Choose what to clean
Review the supported privacy metadata selected for standard cleanup. Content Credentials and other identified C2PA data are a separate choice because provenance can be valuable.
- 04
Save verified copies
The cleaner rescans every output without re-encoding image data. Save one result, write batch copies under NullKit Output, or use individual download links when direct folder writing is unavailable.
Final check
Check the result before you use it
Verification belongs in the workflow. Review the downloaded result itself rather than relying only on the preview inside the tool.
- Open the cleaned copy and confirm the image still looks correct.
- Run the cleaned copy through the inspector again and review the receipt.
- Confirm that you are sharing the cleaned filename rather than the original.
Supported files
A conservative format policy.
“Clean” means the selected, recognized metadata was removed and the output passed a local rescan. It never means that every unknown byte or every possible clue has disappeared.
- Only supported selected metadata is removed. Preserved and unsupported data is listed.
- No AI label does not prove human authorship. Pixel-level or invisible watermarks such as SynthID are not detected or removed.
- Content Credentials may help a recipient understand a file's history. Remove identified C2PA data only when that privacy tradeoff is intentional.