Location
GPS fields can expose precise coordinates, altitude, and direction. A photo taken at home, work, or while traveling may reveal more than the visible scene.
GPSLatitude / GPSLongitude / GPSAltitude / GPSImgDirection
AI workflow / EXIF / GPS / PDF XMP
Free AI metadata remover
Choose a supported image or PDF. We detect the file type locally, open the matching metadata workflow, and verify what changed without uploading the original.
Local file detection
Ready to detectFree · no signupChoose a file. We’ll open the right metadata workflow.
The browser checks the file signature first. Supported images stay in the AI metadata cleaner; PDFs open the document-property cleaner.
Drop a file here
We check its contents locally instead of trusting the extension.
You can also paste a file
JPEG, PNG, static WebP, PDFChoose one file first · images can add up to 5
Try a safe sample
On-device file detectionNo file uploadSignature-based routing
18 image + 4 PDF fixtures · cross-browser tested
View test evidenceInspect AI metadata first. Remove second. Verify every result.
AI metadata removal should be observable, not a black box. The workbench shows each finding and decision while keeping the original file unchanged.
Inspect
Read supported prompts, generation settings, EXIF, GPS, and provenance markers before changing anything.
Explain
Separate file-level AI workflow data from location, identity, device, rights, display, and provenance fields.
Clean
Re-encode the visible image locally and discard metadata that is not needed for display.
Re-scan & report
Inspect the new file again, list what was removed, and mark anything the scanner cannot verify.
What AI and photo metadata can reveal
A finished image can still carry prompts, model and workflow settings, provenance records, location, device, author, and editing history.
Identity and device
Author names, camera models, device identifiers, and serial numbers can connect an image to a person or a specific piece of equipment.
Artist / Creator / Make / Model / SerialNumber
Timeline
Capture, digitized, and modification dates can show when an image was created or moved through an editing workflow.
DateTimeOriginal / CreateDate / ModifyDate
AI workflow metadata and provenance
AI-generated and edited images may store prompts, seeds, samplers, model references, XMP records, and provenance markers. Their presence is workflow evidence, not proof of AI origin.
Prompt / Negative prompt / Seed / Sampler / Steps / Checkpoint / LoRA / ComfyUI / AUTOMATIC1111 / C2PA
Remove supported metadata—with proof.
Images are re-encoded locally; PDFs are structurally rewritten for supported document properties. Each output is scanned again, and unsupported formats are rejected before processing.
Supported in V1
Images: up to 5 files. PDF: one file. 25 MB each.
JPEGPNGWEBPPDF
Designed to remove
- GPS coordinates and related location tags detected by the scanner.
- Author, artist, owner, creator, and contact fields embedded in supported metadata.
- Capture, digitized, modified, and other embedded timestamps.
- Camera, phone, lens, software, and workflow-identifying fields.
- Prompt, negative prompt, seed, sampler, steps, checkpoint, model name or hash, and supported ComfyUI, AUTOMATIC1111, InvokeAI, XMP, or PNG-text workflow fields.
- PDF Info dictionary fields and catalog XMP covered by the PDF scanner.
Designed to preserve
- The intended visible image, subject to browser decoding and re-encoding.
- Pixel width and height for supported static images.
- Common sRGB appearance; embedded color profiles may be removed.
- Your original file, which is never overwritten or modified.
- PDF page count; document contents remain outside the metadata-cleaning scope.
Important limits
- Animated PNG and animated WebP are rejected in V1 instead of being silently flattened.
- C2PA or Content Credentials removal requires explicit consent; detection is not cryptographic validation yet.
- Unknown or unsupported metadata may be reported as unverified, never silently claimed as removed.
- HEIC, RAW, video, audio, and Office files are reported as unsupported at the homepage. They are not uploaded or cleaned.
Remove AI metadata before an image leaves your hands
Inspect hidden generation, provenance, and privacy data before you post, list, deliver, or send an image.
Review metadata before social publishing
Check stored fields that may contribute to an AI label, then clean supported file-level metadata without claiming control over a platform’s classifiers.
Prepare AI artwork and listing images
Remove supported prompts, model and workflow references, GPS, and editor fields before publishing product, print-on-demand, or marketplace images.
Deliver cleaner creative assets
Review prompt, model, author, copyright, software, and provenance fields before previews or final exports leave your team.
Protect private photos and source context
Remove supported location, device, identity, and workflow metadata before an image moves beyond a trusted circle.
Verify the privacy claim yourself
Privacy should not depend on a promise. The browser network record and the output re-scan provide two separate checks.
0 file uploads
Analytics may send pageview requests, but file processing sends no file or metadata payload.
0 processing API
The cleaner calls no file-processing API.
0 file data sent
Only the disclosed page analytics contact external providers; file bytes stay local.
AI metadata removal, without vague promises
Clear answers about prompts, EXIF, image quality, provenance, AI labels, and the limits of file-level metadata cleaning.