EXIF Metadata Checker: Find and Remove Photo Data

Use this EXIF metadata checker on the exact JPEG, PNG, or WebP file you plan to share. It runs inside your browser, flags common GPS, creator, camera, date, XMP, and text fields, and does not upload or alter the file. If it finds anything sensitive, make a separate cleaned copy and inspect that output again before it enters a post, message, shared folder, or collaboration handoff.

A clean result is a useful gate, not an anonymity promise. Private camera tags, unsupported file types, filenames, sidecar files, visible room details, faces, tattoos, reflections, and audio need separate checks. Keep the raw original private and move only a verified delivery copy into your approved publishing folder.

What does the browser metadata checker read?

Metadata is structured information stored alongside the pixels. The current CIPA Exif 3.1 standard listing documents the TIFF-based Exif format used for camera and capture data. JPEG commonly places that data in an APP1 segment, but metadata is not limited to JPEG or to fields labeled EXIF.

The W3C PNG specification defines an eXIf chunk plus text, international text, compressed text, time, and color-profile chunks. Google's current WebP container specification likewise allows EXIF, XMP, and ICC metadata chunks. That is why changing a photo from JPEG to PNG or WebP is not a reliable stripping method. The new container may still have room for the same identifying data.

This checker covers the fields that are most useful in a creator release review:

The tool reads up to 20 files at once, with a 50 MB limit per file. That is enough for a final-photo batch without encouraging you to drop a full raw archive into a browser tab. Inspect video separately because its container, streams, chapters, and audio create a different review problem.

How should you read the checker results?

The result groups metadata by what you should do next.

Identity or location means stop before sharing. GPS coordinates, a camera owner name, artist field, copyright owner, camera or lens serial number, image unique ID, or identity-like XMP text can connect a file to a person, place, or equipment history. Remove the field from a separate copy and inspect again.

Review before sharing covers timestamps, device make and model, editing software, descriptions, comments, XMP packets, and application metadata blocks. These fields are not equally dangerous in every threat model. A camera model by itself rarely identifies a person, but the same device and exact time across personal and creator accounts can strengthen a match. Descriptions or comments can contain a name or private project title.

Technical only includes orientation, pixel dimensions, exposure settings, and ICC color-profile presence. These fields usually help display the image correctly rather than identify the creator. Keep them if your cleanup method needs them for color or orientation, but confirm that your full local scan does not hide personal information inside a vendor-specific field with a technical-looking name.

No privacy-sensitive metadata detected means the browser parser found none of its supported high-priority or review fields. It may still report an ICC profile or other technical data. Do not translate that result into safe to publish until the filename, image content, destination, and unsupported metadata have also passed review.

The checker shows exact GPS coordinates when it can decode them. That is deliberate: you need to see whether the field points to a home, studio, hotel, or another sensitive location. The coordinates remain in your browser tab. Do not paste them into a shared tracker or support message just to document that the file failed.

Which metadata fields matter most to a creator?

Start with fields that create a direct bridge, then work outward to correlation clues.

The risk depends on the whole evidence chain. A common phone model is weak evidence. The same phone model, exact capture time, creator name, and location is a much stronger bridge. Your job is not to decide which single field would expose you. Your job is to avoid publishing unnecessary clues that can be combined later.

The creator doxxing guide maps metadata beside face matching, account linkage, voice, visible location details, and human disclosure. Use that wider model when a file passes the checker but still contains recognisable information.

Inspect the final export, not the camera original

Metadata can change at every stage. A camera original may contain GPS that an editor drops. A clean source may receive new software, author, copyright, description, date, or XMP fields during export. A batch rename can create a revealing filename after the binary metadata is already clean.

Run the gate in this order:

1. Export the final candidate from the editor.
2. Rename it with a neutral creator-safe identifier.
3. Inspect that exact file with the browser checker.
4. If the format is unsupported or the result needs action, inspect it with ExifTool.
5. Create a separate cleaned copy rather than overwriting the private source.
6. Reopen the cleaned copy and confirm the pixels, crop, color, and orientation still look correct.
7. Inspect the cleaned copy again.
8. Move only the verified copy into the approved or delivery folder.
9. Confirm that the post, message, or share picker is attached to that exact copy.

This sequence separates evidence from intention. A file called clean-final-v4.jpg is not clean because of its name. A tool reporting no supported sensitive fields is better evidence, and a second comprehensive scan is the right choice when the consequences of exposure are high.

For batches, add the metadata result to the same approval state as the cover, caption, audio, and visual review. The batching and scheduling guide uses separate raw, working, review, approved, and release states so a deadline cannot pull an unverified file past the gate.

Remove location on iPhone, iPad, and Mac

As of August 2026, Apple's current location-metadata safety guidance provides three useful controls:

• On iPhone or iPad, open the photo, choose the More control, select Adjust Location, then No Location.
• In the iPhone or iPad share sheet, open Options and turn off Location for that share.
• To stop future Camera captures from recording location, go to Settings, Privacy & Security, Location Services, Camera, then choose Never.

On Mac, the same Apple guide describes reviewing location in Photos and using Image, Location, then Hide Location or Revert to Original Location. Treat these controls as location controls, not proof that every creator, device, date, software, XMP, or private camera field is gone.

After using a share or export control, save the exact output that will be delivered and run it through the checker. The source in your Photos library and the file produced for sharing can have different bytes. Checking one does not approve the other.

Turning off Camera location is a strong prevention step because new captures should not receive GPS coordinates from that permission. It does not clean old files or remove timestamps, device fields, owner values, software tags, filenames, or visible location clues.

Handle metadata on Android without relying on one gallery menu

Android camera menus vary by manufacturer. Google's current camera location settings guide lists names such as Save location, Location tags, Geotag photos, and Store location data. Turn the relevant option off on every camera app used for creator work, then make a harmless test image and verify the result instead of trusting the toggle label.

Do not assume Google Photos can remove every captured location. Current Google Photos location guidance distinguishes estimated or manually added locations from a location recorded automatically by the camera. It says camera-added location cannot be edited or removed inside Google Photos, and that downloading and sharing outside Google Photos can expose the original device-saved location despite edits made in Photos.

For an existing Android file with camera-written GPS, move a private copy to a desktop workflow or use a trusted local metadata utility that supports the exact format. Create a new delivery copy, inspect it, and keep the original out of the share picker. A gallery screen showing no map is not a complete EXIF scan.

If the camera saves HEIC, the browser checker will mark it unsupported. Do not convert solely to satisfy this tool and assume the conversion cleaned the file. Conversion software can copy metadata into the JPEG output. Convert in a controlled workflow, inspect the converted file with ExifTool, then check the final JPEG here as a second readable summary.

Use ExifTool for complete JPEG cleanup and verification

ExifTool is a local, cross-platform reader and writer for image, audio, video, and document metadata. Its current FAQ warns against deleting all metadata from proprietary RAW formats because some data may be needed to render the image. It also recommends preserving the ICC profile and color-space information when removing JPEG metadata so color rendering does not change unexpectedly.

Work on a copy. For one JPEG, this pattern creates a separate output and follows the current ExifTool metadata-removal guidance:

exiftool -all= --icc_profile:all -tagsfromfile @ -colorspacetags -o clean-photo.jpg source-photo.jpg

Inspect the output:

exiftool clean-photo.jpg

Then select clean-photo.jpg in the browser checker above. Technical color fields may remain by design. Identity, location, date, device, owner, description, comment, and XMP values should not.

For a folder of JPEG review copies, use a separate output directory so the raw files remain untouched:

exiftool -ext jpg -all= --icc_profile:all -tagsfromfile @ -colorspacetags -o clean/ review/

Read ExifTool's output and warnings. A command that skipped an unsupported file is not a successful cleanup for that file. Open several cleaned images to confirm color and orientation, then scan the full clean directory before it becomes publishable inventory.

Do not run destructive metadata commands against your only copy. Originals may be needed for editing, provenance, disputes, or a corrected export. Keep them in private raw storage that the publishing picker cannot reach, and give the cleaned derivative a neutral content ID rather than a real name or location.

What about PNG, WebP, screenshots, and edited exports?

PNG is not automatically clean. It can carry EXIF, author, copyright, description, comment, creation-time, XMP, modification-time, and private chunks. The browser tool shows readable standard text and flags compressed text that it does not expand. A compressed field is a reason to use ExifTool, not a reason to assume the content is harmless.

WebP is also a metadata-capable container. Its EXIF and XMP chunks can survive a conversion or export. Inspect the final WebP itself, not the JPEG that existed earlier in the editing chain.

A screenshot creates a new image rather than preserving the original file byte for byte, but the new image can have its own date, device, software, filename, and other metadata. Screenshots also change dimensions and may reduce quality. Use one only when that loss is acceptable, then inspect the screenshot as a new source. Do not call it clean without checking.

Editing is not a cleanup promise. Photo tools often preserve metadata because ordinary users want dates, locations, copyright, and color information to survive. Export presets may behave differently by file type. Test each preset with a harmless file, document the result, and repeat the check after major editor updates.

Inspect video metadata with a container-aware tool

The browser checker intentionally stops at still-image containers. A video can carry metadata at the global file, video stream, audio stream, chapter, and device levels. It can also contain location, creation time, encoder, title, artist, comment, and camera information.

Use ExifTool to inspect the exact final video:

exiftool final-video.mp4

If your workflow uses FFmpeg to create a metadata-clean delivery copy, consult the current FFmpeg metadata mapping documentation for the container and streams you are handling. A negative metadata input can disable automatic copying, but global, stream, and chapter metadata are separate scopes. Do not copy a one-line command without checking which scopes it covers.

After remuxing or exporting, play the complete output with sound enabled. Confirm duration, first and last frames, orientation, cover frame, audio, captions, and seek behavior. Then run ExifTool again. A file can be metadata-clean and still reveal a voice, real name spoken off camera, transit announcement, notification sound, room, reflection, or face.

Metadata is only one part of the final-file review

Binary tags are easy to scan because they are structured. The surrounding clues are less tidy and often more revealing.

Filename and folders. Rename the delivery copy before sharing. Remove real names, addresses, neighborhood labels, camera-roll sequences tied to personal posts, client names, and private event titles. Open the actual share screen because a cloud folder or archive name may be visible even when the file name is neutral.

Sidecars and archives. Editing tools may store metadata in .xmp, project, catalog, JSON, or database files. Send the approved image or video, not the working folder. Inspect ZIP contents and archive names before delivery.

Visible clues. GPS removal does nothing to a street sign, window view, shipping label, certificate, school logo, family photo, badge, distinctive room, or reflection. Review the complete frame at full size.

Biometric clues. Metadata stripping does not anonymize a face, voice, tattoo, scar, hands, or movement. The mask, crop, blur, and face-anonymization comparison helps route the visible-face layer separately.

When a face-forward photo or prerecorded video fits the concept but your real facial identity must stay out of the approved file, the current NeoFace face anonymization walkthrough shows the upload, face detection, anonymized-output review, and download flow. Run the metadata check after processing because the downloaded result is a new file with its own approval state.

Face anonymization changes the visible face in the reviewed result. It does not remove metadata, backgrounds, body identifiers, audio, filenames, or account links. Keep those checks independent so one successful result cannot approve the rest by association.

A metadata-safe release checklist

Use the one-time items to reduce future work, then run the release items on every final package.

One-time setup

• Turn off camera location for every device and camera app used for creator content.
• Clear real owner, artist, copyright, and template fields in cameras and editing software.
• Install ExifTool from its official source on the local machine used for final review.
• Create separate raw, working, review, clean, and approved folders.
• Keep raw folders outside the albums, synced locations, and pickers used for publishing.
• Test each photo and video export preset with a harmless file.
• Write a neutral filename pattern based on content ID and version.

Every final file

• Export a new delivery candidate rather than sharing the editing source.
• Rename the file without a real name, private location, or personal project label.
• Run the browser checker on JPEG, PNG, or WebP files.
• Use ExifTool when the format is unsupported, compressed text is present, a warning appears, or the consequences justify a complete scan.
• Remove unnecessary metadata from a separate copy while preserving required color information.
• Open the cleaned copy and confirm its appearance, orientation, and playback.
• Inspect the cleaned copy again and resolve every identity or location result.
• Review the pixels, audio, filename, folder, sidecars, caption, cover, and destination account separately.
• Move only the verified copy into the approved publishing or delivery folder.
• Confirm the actual post, message, or share screen points to that exact file.

The interactive OnlyFans privacy checklist places this file gate inside identity separation, account discovery, promotion, monitoring, and incident response. The ongoing anonymity playbook helps repeat those controls after launch rather than treating cleanup as a one-time event.

What to do with a clean result

Record a clean result as one completed control: metadata checked on final export. Do not record anonymous, safe, or cannot be traced. Those claims are wider than the evidence.

If the same export is later cropped, recompressed, watermarked, captioned into a container, converted to another format, or downloaded from a collaboration tool, it becomes a new file. Inspect it again. The approved state belongs to exact bytes and packaging, not to the concept or source shoot.

Keep the routine mechanical. Select the final copy, inspect, clean when needed, verify again, review visible and audio clues, and move only the approved result into the release folder. That sequence closes a preventable exposure path without pretending metadata is the whole privacy problem.